"Hi Mike, Just a note that iPhone firmware 1.1.4 wonked by previously fault-less iPhone. No hacks or 3rd party stuff on it. Just went puff and into restore mode.

By the way, Restore works great, just have to wait for the data sync to finish and it's as if it never happened. This is how it should be for restoring computers that go wonk too! Thanks and all the best to you,
-Jim"

The iPhone 1.1.4 update window had a link to Apple's security updates page but nothing there yet on the iPhone 1.1.4 update as of 8PM eastern time Tuesday (nor at Apple's iPhone pages yet) but may be by the time you read this.

"Subject: Powerpoint 2008 Font Issues -- Microsoft "Don't use 3rd party fonts"
I have some news for you relating to Microsoft Office 2008 for the Mac, particularly Powerpoint.
The 2008 version of Powerpoint does not correctly support several of our 3rd-party fonts, including Agfa's "Sacker" font, all of which worked just fine in Powerpoint 2004 for the Mac. When selected in the font menu Powerpoint 2008 displays them with a substitute/generic font that looks nothing like the selected font. This occurs without any warning or dialog box that a substitution has occurred.

Upon calling Redmond for help, Microsoft's Mac Tech Support laughably told me after emailing them a bunch of sample files and enduring several long periods on hold that "the engineers writing the program decided no 3rd-party fonts were being supported in Office 2008 and that I could only use Microsoft fonts." I find this hard to believe and wonder if this was just something he said to placate me. I hope that the issue is resolved in a forthcoming bug fix release so that we will not have to continue to keep Powerpoint 2004 around indefinitely.
(he later wrote)
Now working to try and sort out the issue with the support people at FontHaus (fonthaus.com), which is where we bought the font. They seem to think it may that we are using the Mac Postscript version of the font and are sending us the TrueType version to try, and if that doesn't work the OpenType version. I will report back with what we come up with.
Thanks, Tolga M.

"Introducing new MacBook and MacBook Pro models Apple today introduced new models of the MacBook and MacBook Pro. MacBook Pro models feature the latest (Penryn) Intel Core 2 Duo processors (running at up to 2.6GHz with 6MB of shared L2 cache), larger hard drives (up to 300GB), and 2GB of memory standard in most models. They also include the latest NVIDIA graphics processors (8600M GT) -with up to 512MB of video memory and an innovative Multi-Touch trackpad, first introduced in MacBook Air.

The three new models of the MacBook feature faster processors and hard drives: sleek white 2.1 GHz and 2.4 GHz models with 120GB or 160GB 5400 rpm hard drives and a stunning black 2.4 GHz model with a massive 250GB 5400 rpm hard drive. The 2.4 GHz MacBook ships with 2GB of memory standard, expandable up to 4GB across the line.

Available immediately, the new MacBook and MacBook Pro models start at just $1,099 and $1,999, respectively. "

They also have a separate press release on the new models. The Apple store was down earlier this morning for changes - it's back online now.

"Subject: Powerbook G4 Disabled Lower Memory Slot Fix
Hi Guys, Here is my solution for the disabled lower memory slot that has plagued many Powerbook users. Unfortunately it is not currently a permanent fix, but I submit this to you in the hope someone will be able to come up with a proper solution. Little testing has been done on this fix, but I have trialed it on my Powerbook with 100% success.
Kind Regards, Jonathan T.

here is a solution to the problem, sort of.
i confirmed my lower slot is not fried by starting up with a single dimm in the lower slot. however it still will not recognize the lower dimm if there is memory in both the upper and lower. this may be different to what others are experiencing so your mileage may vary.
####NOTE THIS INVOLVES THE USAGE OF OPEN FIRMWARE, YOU COULD PERMANENTLY DAMAGE YOUR MACHINE FOLLOWING THIS PRODECURE SO PERFORM AT YOUR OWN RISK, I WILL NOT BE HELD LIABLE####
anyway as i said, my powerbook was physically detecting the ram in open firmware, simply not mapping it to any address space.

logic dictates that if the ram isn't properly mapped to an address, it will not be visible in mac os x. thus the ability to artifically reduce the size of your system ram in open firmware by changing these mappings.

1) first of all a note about module sizes. sizes appear to be in hex.
- 10000000 = 256mb
- 20000000 = 512mb
- 40000000 = 1gb
- and so forth...
you need to use the sizes above to map your ram to relavent address space.

2) next boot into open firmware. do this by holding cmd+opt+o+f just after the boot chime of your macintosh.

3). this will bring you to the white open firmware prompt "0>". from here you need to navigate to the memory device tree by typing:

0> dev /memory

4) to display the details about the current memory mappings type:

0> ..properties

5). this is an example of how i mapped my powerbooks memory modules to address space.

0> 0 encode-int 10000000 encode-int encode+
2> 10000000 encode-int 40000000 encode-int encode+
4> encode+
2> " reg" delete-property
2> " reg" property
0> mac-boot

the first line loads onto the OF stack the location of my first memory module. in this case it starts at address space 0 and is 10000000 (256mb) in size.
the second loads my second memory module onto the stack starting at address 10000000 (directly after the first module) and is 40000000 (1gb) in size. the third line encodes the two lines above together on the stack. the fourth line deletes the current address space mappings (the contents of the " reg" property). the fifth pops my new memory mappings off the stack and onto the " reg" property. finally the last line starts the boot process for your mac. check system profiler and both dimms should be registering now.

6) There are two problems I can see with the use of this method. First of all it is not persistant, when you reboot your machine these mappings will be lost and you will be back to square one. Second, and this is the biggie, why is open firmware not doing its job and mapping both modules properly! is there a problem with it gauging the size of the memory in the lower slot when two modules are installed (i.e. faulty module)? or is this just a firmware bug?
Anybody have any answers? Anybody at all?
-Jonathan T."

When this first came up years ago, I thought it may have been memory module related (years ago a powermac G4 firmware update would not recognized PC100/PC133 dimms that did not have CL3 timing in the SPD for instance - I linked to a 'dimm first aid' util for that here) - but swapping modules IIRC did not help. After the usual voodoo didn't help (reset nvram, PMU, reseat sodimms, etc. there may be an issue with one of the contacts (either in socket or socket contact to logic board). BTW - replacement logic boards are still not cheap - PB G4/1GHz logic board was appx $400, 1.25GHz was appx $450 when I checked today, plus install costs if you can't do it yourself.

• MacBook (Early 2008) and MacBook Pro (Early 2008): Selections in 'Optional Installs' may not show as selected (Apple)
• CD Stack 1.1.2 (advanced CD ripping and encoding app w/iTunes integration, using the LAME Encoder)
• Jade 1.0.5 (image enhancement tool)
• LightZone 3.4 (Digital photo editing and workflow software)
• Ricochet Lost Worlds 1.0 (breakout game - apple staff pick)
• Lux Delux 5.71 ("Risk" style game w/network play)
• MacPool 9.0
• SuperTuxKart (Intel) SVN 1567 (free)
• Xslimmer 1.5.1 (trim univ. binary apps)
• aLunch 3.1.0
• Best Buy Drops Xbox HD DVD Player Price To $50 (informationweek)
• Network Solutions named in class action suit