[dead2sin]

I am going to try rev200 of InstaDMG. I read its a good solid candidate for version 1.5, so perhaps it will work for me.

[dead2sin]

I’ve tried building an image, I removed the ichat bom and it still didn’t work.

Clearly there is an issue with the 10.5.7 update that causes iChat to get pooched. I’m not sure what is causing this, but it is extremely frustrating. This is putting a complete halt on all my image building because if iChat doesn’t work in a regular vanilla image, there is no point doing anything else until I get it resolved.

I tried a fresh install of OS X 10.5 updated to 10.5.7 and it did the same thing.

I’m not sure where to go from here. I love InstaDMG, but this is a show stopper for me. I personally prefer Adium, but I won’t force everyone to use it (Adium doesn’t do video chat and screen sharing).

Any ideas? I’m willing to try anything at this point.

Thanks,

Nate

[dead2sin]

I’ve gotten a retail disc image now that I’m using to build images and it didn’t resolve the issue.

I did, however, build an image without the 10.5.7 combo updater and iChat works fine (so it was a plain 10.5.0 install). I’m suspecting there are some issues with how InstaDMG is installing 10.5.7.

As Larkost illuded to, the distrubution scripts look at the current system, so as such, I moved the BOM files for iChat and 10.5.7 in hopes that it will fix the iChat issue. If this doesn’t fix the issue, I’m king of at a loss for what would cause this. Perhaps I can check the install options for 10.5.7 and see if there is anything there that might cause issues (But it shouldn’t, considering that the default install of 10.5.7 works great if you install it manually).

Nate

[dead2sin]

Good question, I’m not sure. Its a 10.5.0 DVD Image, not sure if its retail or not though.

Will a OEM one cause an issue like this? I was reading that if you have certain updates installed, the distribution scripts from Apple will see it and not install certain things, so I’m curious if this was the issue. (I did a fresh install, updated to 10.5.7). We’ll see if that fixes it or not though.

We have licenses for all our computers on campus, but I’m not sure if Apple gave us a Retail DVD or not. I have a CPU drop-in disc that I could use. It is pretty much retail, is it not?

Thanks,

Nate

[dead2sin]

Ah, Alright. Good to know. Thanks =)

[dead2sin]

Oh, well its related in this way:

I need a way to set this up in my InstaDMG process and for existing computers (also for testing purposes), I plan on pushing it out via ARD.

So essentially I plan on making it into a package so I can just slide it into my instadmg lineup. I’m in the process of converting all our regular golden master images into InstaDMG images.

Thanks!

Nate

*edit* which Forum should the details of the LaunchD item be discussed in?

[dead2sin]

Yea. Well, they are not all that different. Heck, Server gets iTunes just like the client does (which I still don’t get…) I will have to try it out and see if it works or not.

Nate

[dead2sin]

I was looking into using a 10.5 Server in a virtual machine to build packages. Would this be a problem? I know there are slight differences in the OS (otherwise they are virtually identical other then the server pieces themselves).

Nate

[dead2sin]

Did you do the filesystem change method or the diff-based method?

I installed all the products, then select make a package from all installed adobe products. The package it created worked great.

When you open the product, it asks you to accept the agreement and thats it. No re-serialization or anything.

Nate

[dead2sin]

Isn’t MCX deployed via an OD server? We don’t have one quite yet, only AD.

Nate

[dead2sin]

Yep, it had the right permissions. I got this working, just forgot to post about it.

Basically, all do you do is copy the /etc/cups/printers.conf file and the /etc/cups/blah.ppd for the printers mentioned in the conf file and you are done. I just made a pkg that delivered those as the payload to the appropriate place and used the same permissions that were present on the master (I added them using the lpadmin command and then copied the files).

It seems to work great. Solved the problem quite well. Thanks to all who commented on here.

Nate

[dead2sin]

Ahh, Alrighty. On my file, I mention most of the things to not install specifically, that way I’m sure I got them. I never tried it by using the whole group, but others here have and it has worked.

Also, is your file InstallerChoices.xml? I don’t know if its picky about the name, but normally the commandline stuff is case sensitive.

Let me know how it goes. I have a build going right now involving CS4…I have my fingers crossed =)

Nate

[dead2sin]

The contents of that file should be in the following format. I’ll use your options in this example:

AdditionalFonts
PrinterDriversGroup
LanguageTranslations
X11

Now, I couldn’t tab in this box for some reason, so don’t cut and paste it, but its a tab after the array line. Also, there is an example file in InstaDMG_1.4b4/Documentation/InstallerChoices/InstallerChoices.xml

It should give you a good idea of the format the xml file needs to be in.

Nate

[dead2sin]

No Problem. I’ve asked quite a few questions here myself, so I figured I’d help someone else out for a change.

I have issues with the Camera Raw 2.4 update myself. I have not quite figured that out yet. It says it installs it, but software update pops up and says I need to install it.

Nate

[dead2sin]

If you are using straight InstaDMG, they MUST be a .pkg. If you use InstaUp2Date, you can use DMGs and it’ll work fine.

Nate

[Author]

Posts