[typofonic]

[quote]there is a createUser re-roll which we’ll bundle in the svn shortly
instaup2date.py requires light plumbing changes(or targeting a version of python without the specific bug we’re experiencing) due to the way modules are loaded[/quote]
—–
Not to be pushy, but any timeframes on these two (createUser and instaup2date.py)?

P.S. Don’t know why the quotes on the post I’m answering doesn’t show up…

[typofonic]

Thanks for your answer. I actually did this (and had the same build of 10.6.6). But it just doesn’t find it.I also tried downgrading findInstallerDisc.py to an older version with no luck. It seems though to be a known problem:
[url]http://code.google.com/p/instadmg/issues/detail?id=79[/url]

I tried ejecting all disks (which is described on the page above), and this actually worked when running InstaDMG by itself! But instaUp2Date still gives me the same error, so the installation can’t be setup properly.

Any ideas?

[typofonic]

[QUOTE][u]Quote by: cygnus2112[/u][p]But therein lies the facility of instadmg to minimize the overhead of maintaining different images. Just build your instaUp2Date catalog off the mbp grey disc instead of the retail generic build, and you have an identical image save for the driver differences between the retail and hardware-specific builds.[/p][/QUOTE]

Hi,

I just tried building an image using a 10.6.6 BaseImage from a 2011 MacBook Pro 15″. I updated instaDMG to the newest version from the svn, updated my catalogs with the 10.6.7 2011 specific update and ran InstaDMG. Unfortunately I got this error:

[code]Finding the Installer disc for setup
Traceback (most recent call last):
File “./instaUp2Date.py”, line 716, in
main()
File “./instaUp2Date.py”, line 678, in main
foundInstallerDiscs = findInstallerDisc.findInstallerDisc(allowedBuilds=thisController.installerDiscBuilds)
File “/Volumes/Lacie/instadmg/AddOns/InstaUp2Date/Resources/findInstallerDisc.py”, line 201, in findInstallerDisc
raise commonExceptions.FileNotFoundException(‘Unable to find OS Installer disc in any provided folder: %s%s’ % (str(searchItems), folderString))
Resources.commonExceptions.FileNotFoundException: Unable to find OS Installer disc in any provided folder: [‘/Volumes/Lacie/instadmg/InstallerFiles/InstallerDiscs’, ‘/Volumes/Lacie/instadmg/InstallerFiles/BaseOS’] ([‘.DS_Store’, ‘.svn’, ‘Mac OS X Install DVD.dmg’], [‘.DS_Store’, ‘InstallerChoices.xml’, ‘Mac OS X Install DVD.dmg’])
[/code]

Can’t quite wrap my head around what’s missing :-/ Any ideas?

[typofonic]

[QUOTE][u]Quote by: dead2sin[/u][p]Are you using the untouched 10.6_vanilla.catalog, or were changes made to it other then the build number? If it can’t find the installer disc, it is not even getting past 10.6_vanilla then. I would grab a fresh copy of 10.6_vanilla.catalog from the svn, rename your current one or move it out of the way. Then, add your specific build to 10.6_vanilla’s build section at the top and try running just the vanilla catalog.

If that works, then try one catalog up in the chain. You don’t have run a full build, just get to the point where it has found the installer disc and is about to build then control-C it to terminate. I suspect there is something wrong in the 10.6_vanilla catalog if it works for you in the example but not with your own catalogs. You should *never* edit the 10.6_vanilla catalog except for the build numbers and volume name if you want to change it. All the other items there are exactly what you need. No extra packages should be added to 10.6_vanilla that are non-Apple updates (normally 10.6_vanilla is updated pretty rapidly, so I have never had to really worry about this before).

Let me know what that does. You could also post your 10.6_vanilla catalog so we can see it. We might be able to pick out what is causing it to not find the installer. Make sure your catalogs are all linked correctly as well. 10.6_vanilla should not have any “include-file:” entries on it and I’d imagine basic.catalog would include 10.6_vanilla and on from there
[/p][/QUOTE]
No changes were made to the 10.6_vanilla file. Actually the default 10.6_vanilla file contains the build number of my Install DVD.

I must have done something though to the 10.6_vanilla file though, because after I ran svn update, as you suggested, it was able to find the installer disc – succes! 🙂 Thanks!

Or maybe a fix was checked in within the last 3 days.

Because svn updated all of these files:
[code]U AddOns/InstaUp2Date/Resources/tempFolderManager.py
U AddOns/InstaUp2Date/Resources/containerTypes/volume.py
U AddOns/InstaUp2Date/Resources/containerTypes/dmg.py
U AddOns/InstaUp2Date/importDisk.py[/code]

Really appreciate all of your help Nate!
Crossing my fingers that it will work now.

[typofonic]

Thanks! I actually followed this guide to the letter:
“http://www.osxdeployment.info/wiki/InstaUp2Date_Guide” and imported the image using “sudo ./importDisk.py –automatic”.

And I got a build number in the image file name. I just renamed it to Mac OS X Install DVD.dmg.
I added in the line “Installer Disc Builds = 10A432, 10B504, 10C540, 10D573, 10D575, 10F569” in all the catalogs and renamed the image back to “MacOS X Client 10.6.3 10D575.dmg” and it does the same.

When I run InstaUp2Date with the sample.catalog it finishes just fine, but with my own catalogs they error out like this:
[code]Finding the Installer disc for setup
Traceback (most recent call last):
File “./instaUp2Date.py”, line 665, in
main()
File “./instaUp2Date.py”, line 627, in main
foundInstallerDiscs = findInstallerDisc.findInstallerDisc(allowedBuilds=thisController.catalogFileSettings[‘Installer Disc Builds’])
File “/Volumes/Lacie/instadmg/AddOns/InstaUp2Date/Resources/findInstallerDisc.py”, line 190, in findInstallerDisc
raise commonExceptions.FileNotFoundException(‘Unable to find OS Installer disc in any provided folder: ‘ + str(searchItems))
Resources.commonExceptions.FileNotFoundException: Unable to find OS Installer disc in any provided folder: [‘/Volumes/Lacie/instadmg/InstallerFiles/InstallerDiscs’, ‘/Volumes/Lacie/instadmg/InstallerFiles/BaseOS’][/code]

This is how the beginning of my catalogs look (I have three catalogs chained together with include):

[code]# Description

Installer Disc Builds = 10A432, 10B504, 10C540, 10D573, 10D575, 10F569

#Output Volume Name = Volume Name
#Output File Name = File Name

include-file: basic.catalog[/code]

I edit all of my catalog files with Textmate b.t.w.

I simply can’t figure out what I’m doing wrong here (I am using a retail build 10D573)?

P.S. I think it would be excellent to make an option to disable the checksum to save time. For the type of of small scale deployment I do, it’s not really worth the time, especially when troubleshooting (if that makes sense). Consider this a feature request — maybe a flag to be added to InstaUp2Date.py?

[typofonic]

Thanks a lot for your answer Nate. Now I think I understand how it’s supposed to work. I have set up a chain of catalog files, however InstaUp2Date wont recognize my OS X Install DVDs.

I’ve tried putting discs named
“Mac OS X Install DVD.dmg” in both the BaseOS folder and the InstallerDiscs folder, but I get one of two errors each time I run InstaUp2Date:
———————————
Finding the Installer disc for setup
Traceback (most recent call last):
File “./instaUp2Date.py”, line 665, in
main()
File “./instaUp2Date.py”, line 627, in main
foundInstallerDiscs = findInstallerDisc.findInstallerDisc(allowedBuilds=thisController.catalogFileSettings[‘Installer Disc Builds’])
File “/Volumes/Lacie/instadmg/AddOns/InstaUp2Date/Resources/findInstallerDisc.py”, line 190, in findInstallerDisc
raise commonExceptions.FileNotFoundException(‘Unable to find OS Installer disc in any provided folder: ‘ + str(searchItems))
Resources.commonExceptions.FileNotFoundException: Unable to find OS Installer disc in any provided folder: [‘/Volumes/Lacie/instadmg/InstallerFiles/InstallerDiscs’, ‘/Volumes/Lacie/instadmg/InstallerFiles/BaseOS’]
——————————–
OR
——————————–
Finding the Installer disc for setup
Traceback (most recent call last):
File “./instaUp2Date.py”, line 665, in
main()
File “./instaUp2Date.py”, line 629, in main
foundInstallerDiscs = findInstallerDisc.findInstallerDisc()
File “/Volumes/Lacie/instadmg/AddOns/InstaUp2Date/Resources/findInstallerDisc.py”, line 115, in findInstallerDisc
raise ValueError(‘In legacy mode the item “%s” was named like an installer disc, but was not a dmg’ % thisItem)
ValueError: In legacy mode the item “/Volumes/Lacie/instadmg/InstallerFiles/BaseOS/Mac OS X Install DVD.dmg” was named like an installer disc, but was not a dmg
———————————

I have tried with both a retail 10.6.3 disc saved manually using Disk Utility and one saved using the importDisc InstaUp2Date script.

The weird thing is that both discs work just fine with InstaDMG by itself, just not InstaUp2Date.

I’ve run “svn update” so I’m on the newest version.

Also I have tried commenting out the build number in the catalog files as suggested on the forums. No luck yet.

Any ideas?

Also, isn’t there an option to skip the checksum part of InstaUp2Date completely?

[typofonic]

From the example below it does seem that it’s necessary to put the filenames of each package in the catalog:

I’m surprised though that the iLife upgrades in the example are put directly in the catalog, and not just included in the end of the file with “include-file: iLife09_Updates.catalog” – isn’t it possible to do it that way instead, to make the setup more modular ore does the includes always install before the rest of the packages in the file?
—–
# This is the catalog for the Base Leopard Image

include-file: Base.catalog

Output Volume Name = Macintosh HD
Output File Name = Snowleopard-1.0.0

System Settings:

Third Party Software:

Office 2008 SP2 Office Installer.mpkg sha1:021a599899d12958bc9aa02d0b9a5002c0b8d79f

Office 12.2.5 Office 2008 12.2.5 Update.mpkg sha1:c742570712129dfc4534de08a4250c41f9c83a59

iLife 09 iLife09.mpkg sha1:d58806ffbea052b45f0826d25ff41322333f6305

iPhoto_81 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-6710.20090818.Cwe4R/iPhoto_81.dmg sha1:e6b1bf494881ba3b357f7d023e2c434e8caf06c8
GarageBand51 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-6633.20090803.fr0Pp/GarageBand51.dmg sha1:7c771583c826c8c70e5c5f01d925e28636d0364d
iDVD704 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-6153.20090604.FqicZ/iDVD704.dmg sha1:d9b6fd4b1a4c8f875dc1a8ca3c8dd31ebae5e1c0
iLifeSupport904 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-7595.20100209.vgbyh/iLifeSupport904.dmg sha1:7cda1492d1bab91383b5738a7cda2cde24f72d2c
iWeb301 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-5977.20090626.B8952/iWeb301.dmg sha1:90a1616428c56f086a41e29528a84971f35f3842
iMovie806 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-7979.20100325.Mbnyh/iMovie_806.dmg sha1:5b63ad631d7a9b9e668db5cb1edf4d421c8af87f
iPhoto_812 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-7747.20100330.xSwe3/iPhoto812.dmg sha1:b7cdf308a45a2ce5b8e1cbf3a78cbaa17dc62c28

Apple Updates:

Software Settings:

[typofonic]

Thanks for your answer Nate! Actually the guide you linked to, as well as a podcast from University of Utah about instadmg, was the basis for my setup.

Ok, so I don’t need the full path in the catalog. But DO I need to add the file names of packages to the catalog, in order for the packages to install?
Or put another way, is it enough to ONLY put every new custom package in the InstaUp2DatePackages folder, or do I ALSO have to add the filename to the catalog at the same time, in order for InstaUp2Date to install them?

[typofonic]

Thanks for your answer. So I assume I just repackage it without any postflight script? Wouldn’t that make Wiretap Studio nonfunctional?

Can’t the path just be changed from /System/Library/Extensions/AmbrosiaAudioSupport.kext/Contents/Info to the same path but on the instaDMG image? If it can, how is it possible to find the path to this directory on the image?

[typofonic]

[QUOTE][u]Quote by: larkost[/u][p]I don’t know what is stopping your boot, but there are a few things:

1) The warning about the modem drivers is normal. I think that all boots get that because the kext that drives modems does not do one thing that it is supposed to do. It probably has not been changed because it is not actually hurting anything, and no-one wants to go through making the change then doing all the work to test to make sure the change does not cause other problems.

2) A trivial googling for the phrase “getWOW_PARAMETERS: Can’t set wow params. Wow is not supported.” tells me that it is in the Airport drivers. But in the reported cases this does not seem to be a fatal error. My guess is that this is not the cause.

3) With a vanilla setup only (so 10.6_vanilla) do you have problems? If not then you can build up from there to find the problem.

4) What is your Install image from? Is it a retail disc? Or is it a grey disc that came with a computer?[/p][/QUOTE]

Thanks for your reply! It is a retail disk. I tried what you suggested with a vanilla setup. There problem was that I accidently applied a security update meant for Leopard on SL 10.6.2 – I thought I had updated all my BaseUpdates – guess not. However after checking with the vanilla catalog I found the correct Security Update and fixed it! [url]http://code.google.com/p/instadmg/source/browse/trunk/AddOns/InstaUp2Date/CatalogFiles/10.6_vanilla.catalog[/url]

Thanks for your help. 😀

[typofonic]

Ok, after having removed most of the packages (with only my BaseUpdates left, a createUser.pkg, a Postflight Script.pkg, User Template.pkg and a package with some installed to /Library) I now get:

getWOW_PARAMETERS: Can’t set wow params. Wow is not supported.

Anybody has experienced this before?

When building a new user with createUser I assume that it uses the System/User Template/ directory. Could the problem be the package with the User Template, or doesn’t this error msg. have anything to do with that?

[typofonic]

Hey Giobbi,

Did it work with your changes?

[typofonic]

Hi pteeter,

I’m wondering if you have files for the newest CS4 updates as well?

[typofonic]

An interesting read about the manifests. Maybe a bit too overkill for my use though.

Anyway to answer my own question — “How do I include the settings I made in MCX in my InstaDMG build?” — for anybody with the same question, it is as simple as copying /private/var/db/dslocal/nodes/Default/computers/guest.plist (or whatever your plist is named) into your InstaDMG build (using a package for instance).

[typofonic]

I was wondering if any of you could post the Flat Package Editor? Haven’t been able to locate it.

[Author]

Posts