well…. so far so good…. but I have no idea how stable this will be because it was reported earlier (unless my memory is messed up) that the retail disc + 10.5.5 would seemingly work on the newer machines, though it was assumed that something would eventually show up as broken and die.
As such, YMMV, but I have built a retail + 10.5.6 image that seems to work, has all the ‘updated’ pref-panes….. Oddly none of my MCX record changes took, so I need to redo those or figure out why they did not work…..
plus I have found permissions issues for the default user folders that I do not get when applying this image to an older macbook or MBP…. no clue how that works but…. i nee to do some more work on the image.

I have an OEM +10.5.6 image built from the MacBookPro5,1 discs booting both a MacBookPro5,1 and MacBookPro4,1. Everything seems to be working out. I’m running into a weird error with my default VMware guest OS however, where it spits out kernel errors at random intervals. Trying to track down whether it’s a problem with my Fusion pkg or perhaps the ordering of pkgs in the build train.

–joe

[QUOTE][u]Quote by: mattzago[/u][p]I have been putting together a build for Late- 2008 Aluminum Macbooks. Using the Leopard 10.5 Retail DVD image with 10.5.6 and all the other updates after that (Front Row etc), My build works well, but I noticed two quirks. First the machine is booting in verbose-mode by default. Someone else on the MacEnterprise forums saw the same thing. If you select the HD as the startup disk using systemsetup from the CLI (or the Startup Disk system preference pane) this issue goes away. The second issue I noticed is that mach_kernel is not hidden in /. I’m thinking the 10.5.6 combo update failed to mark the file as hidden (I am using chflags hidden in a startup script to do this for me).

A much less important detail is that my build does not have the new Energy Saver icon (I just have a package that changes this).

MZ[/p][/QUOTE]
—————————————-

Are you building your image on a Late-08 MacBook Pro? The retail disc will likely not know what to do with the newer hardware and sys prefs. A rule of thumb I follow is to only build an image using install media that is compatible with the hardware used in the build.

If you want to use the retail installer (10.5.4), you might have better luck building the image on an earlier model MacBook Pro and updating to 10.5.6. I would think that image would be compatible with all the latest hardware and going back.

–joe