InstaDMG 1.4b3 won’t use my base dmg

[tkw4u]

I’ve been successfully building images with InstaDMG 1.3. I decided to give 1.4b3 a run. On the same machine I copied over the disc image file of my base OS installer into the BaseOS folder and then moved all my other packages over to the CustomPKG folder for 1.4. When I run the 1.4 version it mounts the disc image for the Base OS install and then immediately gives me the following error:

ERROR: the main install disk was not sucessfully mounted!

It is mounted however. I know the files are good because they are working just fine under 1.3. Anyone have any thoughts or ideas why I’m getting this error with the new build?

Thanks!

[fiftiesdean]

+1

13:16:34 ######InstaDMG build initiated######
13:16:34 ######Mounting Mac OS X installer image######
Mounting a support disk from ./InstallerFiles/BaseOS/./InstallerFiles/BaseOS/leopard.dmg
ERROR: the main install disk was not sucessfully mounted!

mine mounts as well

EDIT: 1.4b2 seems to work though….

[larkost]

At this point InstaDMG is looking for exact names for the base image files. The two that it will accept as the “primary” disk are:

Mac OS X Install Disc 1.dmg
Mac OS X Install DVD.dmg

These happen to be the names that the disks automatically have. So if in creating your installer disks you changed this, it will not find them. The code will mount everything else in the “BaseOS” image as supporting disks, and that is what you are seeing happen. If you change the name to one of those names it should work fine.

I have plans to change this system a bit at some point, namely to have the location of the base image file and any supporting disks to come in through command line flags. I am still toying with ideas, and need to get consensus of the other people on the dev team (this is all new to them as well), but here is the idea that is rolling around in my head right now:

Do away with the automatic searching through the BaseOS folder, and force all users to provide either a name of an image (the name of the dmg file), the path to the dmg file, or a dmg checksum. An option on this one would be to default to the checksum of the 10.5 retail disk. Users could also provide multiple “supporting disks” with another command line switch (called as many times as you would like).

This would allow you to have multiple BaseOS disks and to choose between them. It would also be easy for InstaUp2Date to add this as another variable in the catalog files, and pass it along when it is used to call InstaDMG.

[tkw4u]

That solved the problem for me. I had named my base dmg file “Leopard_base.dmg”. Changing it to “Mac OS X Install DVD.dmg” got everything running fine.

Thanks!

[steve.wood]

I know I’m late to this thread, but I wanted to comment on this. I too was hit with this, where versions prior to 1.4b3 seemed to work fine with a Base OS image named something different, but 1.4b3 and higher would not. The error was a bit cryptic, but that is fine.

What bothers me is that this functionality was changed and you guys didn’t mention it anywhere in the included documentation. A mention should be placed in the docs that indicate the dmg file has to be named something specific in order for InstaDMG to run.

I love InstaDMG and sing its praises everywhere I go, and I really appreciate the work you guys are doing, but please consider mentioning this change in the docs somewhere.

Thanks.

Steve

[thisgarryhas2rs]

I was having problems with this and I finally put the main install disk just in the BaseOS folder and not in a numbered folder and the support discs in a numbered folder in the BaseOS folder and this fixed the error. This doesn’t seem intuitive to me though. Why would putting a main install disc image in a numbered folder like “01” not work. Why can’t instadmg look for the main install disc in a numbered folder?

[mlinde]

Wanted to comment that this still isn’t fixed in 1.4b4 – and was biting me as well. You might do well to include the file name notes in the documentation, not just the ReadMe – especially since you are symlinking to the documentation not the read me. I’ll let you know what I think as soon as it finishes my first run at a ProTools system installation package 🙂

[Author]

Posts