[thegooch49]

[QUOTE][u]Quote by: hotwired34[/u][p]
First and most importantly, it seems like the computer is stuck in verbose boot mode. I have tried running the [i]nvram boot-args=””[/i] command and that seems to do nothing. I have recreated the image about 5 different times with different versions of InstaDMG and on different hardware…all with no success in getting the computer to boot right.

Thanks.[/p][/QUOTE]

Hi hotwired, to fix the verbose boot, just go to the startup disk in System Preferences, and select your disk. Reboot, and it will be gone. Some of the newer computers set verbose startup mode when the startup disk set in EFI is not available.

[thegooch49]

I got mine working properly with a 10.5 base and a 10.5.8 combo updater. I had to switch to InstaDMG 1.5rc1. This made my image good with all the correct version. But, I cannot get the xcode tools to install with 1.5. Has anyone had luck with this, or be able to lend a hand?

[thegooch49]

I just used my 1.4b3 script and my custom packages and InstaDMG worked fine. I didn’t put in any updates in it. I did modify my instauser package, as noted in previous posts. But this seemed to work fine. I got some strange output in my terminal window, but overall it looks fine.

[thegooch49]

Yeah, thanks for the replies. My previous images were built with a 10.5.0 disk, upgraded to 10.5.7. This last one, I used an OEM 10.6, upgraded to 10.5.7. That seems to be the difference in what I did in creating these images. Odd.

[thegooch49]

Hello, building a 10.5.8 image I have a bad mail.app and console.app. Mail is at v3, console at 1.5.0. I used a 10.5.0 retail base, and 10.5.8 combo updater. My code is old instadmg1.4

[thegooch49]

Thanks Chris, I didn’t know that something like that existed. I just downloaded it. The GUI app won’t launch. I looked at the shell script that is included (which I’m guessing does the work for the GUI applescript app) and it just removes the volume check, and deletes a binary called ‘find_office’. It looks like it won’t modify the update package like needed. Thanks though!

-Jeff

[thegooch49]

Thanks for the reply. In my instauser script, I first set a bogus password in script. I do this, because I use the password once, when I enable root. To enable root, I need to put the password in the script as plain text. So instauser first sets the password as ‘fakepass’. It then enables root, using this fake password:

/usr/sbin/dsenableroot -u localadmin -p fakepass -r anotherfakepass

Later in the instadmg script, I move the temp hash files that I put in place, to match the UUID’s for root and localadmin. Perhaps this issue would all be cleared up, if I could find a way to enable root with the instauser script, without having to enter in this dummy password (or put my actual password into a plain text file). Has that been figured out on this forum already? I’ll search.

-Jeff

[thegooch49]

The way I dealt with this, is to have the new host email me some info about the system. It emails a mailing list group, so that the other admins know that a new machine was added to the network. The emails are a reminder to me to add them to the ARD configuration next time I’m on. The email has the hostname, and the first few relevant lines from system_profiler. It also sets the computer hostname (which comes from our DHCP server).

I have this script run as a post flight on another package that I run after the system is image. I just piggybacked this script as a postflight, since I have to run the package anyway (it sets some configurations for cfengine). Maybe this will help.

#Set the computername
systemsetup -setcomputername $(/bin/hostname)

#Phone home
SUBJECT=”New Host Added: ”
TO=”[email protected]”

/usr/bin/mail -s “$SUBJECT $(/bin/hostname)” “$TO” <

[thegooch49]

[QUOTE][u]Quote by: Theilgaard[/u][p] I don’t know if I understand this problem correctly, but it sounds like you are naming you packages with numbers. It is FOLDERS in the AppleUpdates folder you have to create with numbers, and then put you packages into these folders (one in each numbered sub-folder). So it will be the folder number that determines the order of updates, and not the name of the package.[/p][/QUOTE]

Hi, thanks for the help. I have created folders inside of AppleUpdates. In the AppleUpdates, I have created named folders (01,02,etc). In those named folders, I have the apple updates that have the standard name. I’m going to try this again to verify that I’m still having this issue.

[thegooch49]

I just re-built my image with a 10.5.0 baseOS and the 10.5.3 combo update. Everything came out fine. When I had an issue (Imaging with 10.5.3 combe showing as 10.5.2), I was using a 10.5.1 System Restore disk, with the same 10.5.3 combo update. I’m going to re-build this again, to see if I can recreate the problem.

But, all was fine when I used the 10.5.0 retail disk.

[thegooch49]

Confirmed, I have the exact same problem. When I then run SW update, it says I need 10.5.3 still. When I try to run it, it errors about ‘not having rights to install’. I’m glad I came across this, I thought I was going mad. My baseOS is 10.5.1 (system restore disk on a MacPro). I had no other AppleUpdates in the directory. Just the 10.5.3 combo updater (NOT the delta).

Very strange, it’s not just the GUI reporting this. system_profiler and sw_vers both report 10.5.2. Crazy.

[thegooch49]

Yes, I am. The custom updates run fine. My custom installes are all homemade, so I just prefixed the packages with 01, etc. I don’t want do do this with the apple updates, after the warning about receipts having wrong names.

[thegooch49]

Hi guys, I think I might have missed something. I have about 10 apple updates. I created a directory structure inside of AppleUpdates (01, 02, 03, etc). These did not run when I executed the script. My log shows the following. Did you have to modify your script at all to make this work? I didn’t see anything on this thread alluding to any edits.

Thanks,
Jeff

Beginning Update Installs from ./AppleUpdates
installer: Error the package path specified was invalid: ‘./AppleUpdates/01’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/02’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/03’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/04’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/05’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/06’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/07’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/08’.
installer: Error the package path specified was invalid: ‘./AppleUpdates/09’.

[thegooch49]

Yeah, Acrobat Reader is a bit tough. I made a package installer with logGen and pkgGen. Unfortunately this is NOT at universal binary (thanks Adobe), which is one of the reasons I have a PPC and a seperate Intel image.

[thegooch49]

Oops, I just read that you are looking for info in Tiger (not leopard). Sorry.

[Author]

Posts