[chilcote]

I’ve had similar errors if I already have a volume on the machine with the same name as the output name that Instadmg uses. I make it a habit to change the name of my test volume (firewire drive) to fw before starting anew.

–joe

[chilcote]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]Your build equipment and InstaDMG setup are otherwise unchanged except for the replacement of your post-DVD packages with the 10.5.6 Combo updater?

You downloaded the 668MB combo update from Apple (didn’t grab a different machine or architecture-specific version)?

What OS build did the MacBook Pro ship with? Possibly there was a silent hardware revision that requires a later version of 10.5.6?

– Patrick[/p][/QUOTE]

Hi Patrick, thanks for the response. The answers to your questions in order are Yes, Absolutely, and 10.5.5 build 9F2088. I’m not aware of any hardware that ships with a special build of 10.5.6 and there is no mention of that on http://support.apple.com/kb/HT1159

I went ahead and built a simple 10.5.6 image using the 9F2088 build installer and 10.5.6 combo update. I’m not seeing the single-user mode issue nor any of the other issues that I encountered (including MacBook Airs booting into verbose mode after the second restart). I then built my entire image including custom packages with the 9F2088 disc and have not had any issues so far.

I think maybe the stock advise to always use A) retail installers and B ) the latest possible hardware, falls apart in this scenario.

I’d be curious to know if anyone else has experienced this issue, or even if you have time and access to a late-08 MacBook Pro, try out the retail 10.5.4 installer in an InstaDMG build and provide feedback.

–joe

[chilcote]

[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

[chilcote]

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

[chilcote]

Hi Blake.

Check /System/Library/CoreServices/Dock.app/Contents/Resources/English.lproj/default.plist.

–joe

[chilcote]

Better yet I just let InstaDMG mount the second disk image and added a one liner after the initial system installer code and before the part where it saves off a cached version:

[code]installer -pkg “/Volumes/Applications Install Disc/Install Bundled Software.mpkg” -target “$CURRENT_IMAGE_MOUNT” -verbose[/code]

Incidentally, I ran this build on a MacBookPro4,1 (Early 2008), using the installer disk images from the Late 2008 MacBook Pro, and so far don’t have any problems.

–joe

[chilcote]

[QUOTE][u]Quote by: knowmad[/u]WAY way back in the early days of instadmg (about a year, maybe a wee bit more than that) I (and others) found that if you had a two disk install set you could get instadmg to use/find the second disk by simply mounting it before you started.
I am trying this in the next fifteen minutes.
knowmad[/p][/QUOTE]

Sorry, I mistyped. InstaDMG did not skip the dmg, it mounted it but didn’t use the installers inside. For instance, if I run the install from DVD disc 1 it no longer prompts to insert disc 2.

I imagine it will be a matter of yanking all the pkg installers out of the Applications Install Disc disk image and putting them in BaseUpdates before the SU updates appear.

Time permitting, I’ll try it again today.

–joe

[chilcote]

[QUOTE][u]Quote by: ewhite[/u][p]I have an external drive that I use as a “booter” for imaging and troubleshooting. The drive uses Apple Partition Map to make it “Universal” and has Mac OS X 10.5.5 installed (using this technique: http://support.apple.com/kb/HT2595).[/QUOTE]

Your 10.5.5 disk likely does not have the required drivers for the updated hardware included with the new MacBook Pros. First thing I tried was to NetBoot the MacBook Pro off our existing Netboot server, to no avail. Had to create a new NetInstall-NetRestore set on the new machine.

I did not have luck using InstaDMG with the new install disk images. The second install disc is now called Applications Install Disc, and contains an installer distribution package for the optional installs. InstaDMG just skipped that disk image. I tried putting it in my BaseUpdates in place of a numbered folder, but no go. Haven’t mucked around with it since that first try.

Creating a modular disk image manually worked like a charm, and the asr image seems to work just fine with older MacBook Pros. The new fluorescent icon is there for the Energy Saver prefs, and the Trackpad and Keyboard prefs are broken out individually. The Trackpad options that are not relevant on the older hardware are just grayed out. Haven’t tried it on a Mac Pro yet.

However, while it seems to work I’m going to use two images until 10.5.6 comes out. Both restorable images are identical besides the hardware-specific files included with the later build, so there’s no real need to have one image to rule them all for this short time.

–joe

[chilcote]

[QUOTE][i]

LanRev InstallEase helped me make a nice little package that pushes those three files out to the local user directory, but of course, that would not work in InstaDMG. I did try to build a package that just had the three files and then made an mpkg with duplicate copies directed at each local home directory, but permissions seem to be a problem. Any thoughts on how to do this effectively would be welcomed.[/i][/QUOTE]

So as not to duplicate effort I like to use the same packages created by InstallEase for both InstaDMG and ad hoc deployment. Then I include in InstaDMG a StartupItem which copies the files at /Users/Shared/LANrevInstallEase_FilesForHomeDirectory to the User Template. This way the script traps for any changes that have been added to the various packages rather than requiring a manual repackaging of everything into the User Template.

[chilcote]

Hrm. A bit surprising that no one else is deploying VMware out there so I’ll just leave a quick note that I fixed it with a simple ditto to /Users/Shared/Virtual Machines during the InstaDMG build process. Probably more ideal anyway since packaging up such a large bundle may be prone to error.

best,

–joe

[Author]

Posts