sorta Step by Step

The Theory that all is well with the world stops before you sit down... Chocolate drives all necessity... that said... you need a directory structure to start all of this off... + \-InstaDMG \--BaseOS \--AppleUpdates \--CustomPKG \--ASR_Output \--DMG_Scratch \--Logs in the basic form of the program - place the shell script into the "root" of this tree and then - shove a DMG of the OS install disk(s) into BaseOS shove any and all PACKAGES (.pkg/.mpkg) that relate to Apple SW updates into AppleUpdates shove any and all PACKAGES (.pkg/.mpkg) that relate to YOUR stuff, repacked installers, startup scripts, etc into CustomPKG ASR_Output is where the final ASR image goes DMG_Scratch is the temp space Logs is where you read about what went wrong you can rename packages to specify an order - this MAY cause problems down stream as the receipt file in /Library/Receipts will also have that prefix associated with it. what I tried to do with my revision is to add some error checking, and other capabilities.... if I could figure out the fileformat for the XML input on the installer command, it would be "trivial" (insert cough/sputter here) to have the script read the package BOM, prompt "you" the user to select which parts/pieces to install, generate an XML plist, then run the installer CLI with that as input.... after all, if you "know" that you only have HP Printers why install all printer drivers? same with the additional fonts, and languages. it should be possible to script some Automator Actions to do all of this as well... NOTES: the installer cmd is VERY different between 10.4.xx and 10.5 hdiutil and diskutil also seem to behave differently as well This should get folks started remember - LogGen and PkgGen? reacquaint yourselves - [url]https://www.afp548.com/article.php?story=20070820193811465[/url] the basics for repacking certain vendor's software into a pkg file is mandatory to make all this work and remember - you can install the serial numbers as well... Let me know how to help! Rich