[dead2sin]

[QUOTE][u]Quote by: golbiga[/u][p]I’m newish at InstaDMG and I had a quick question. I’ve created my image on an older Mac Pro using a 10.6 retail DVD and then added the combo updater, etc. The image has worked fine on all my test machines, ones newer than my mac pro even. Today I just imaged a new Mac Mini and the ethernet port is not being recognized. I’ve checked to see if it was hardware related, but its not. I was always under the assumption that you didn’t need to necessarily run InstaDMG on the newest hardware and that since its 10.6.4 that the any machine at this point should work. Should I be using the 10.6.3 disc that came w/ the Mac Mini to make the default image? Or is it simply that I should do the whole instadmg config on the mac mini? Thanks in advance.

Allen[/p][/QUOTE]

There is a special version of 10.6.4 JUST for mac Minis. 10.6.4 should work on all hardware that was released before it came out. 10.6.4 was released June 15th, so it will have drivers for any hardware that came out before June 15th. Unforunately the best solution at the moment is to do a special image build just for the Mac Minis using that special 10.6.4 update or you could wait for 10.6.5, which should contain the Mac Mini drivers as well.

Here is the specific 10.6.4 update you’d probably want:
[url]http://support.apple.com/kb/DL1054[/url]

Nate

[dead2sin]

If you ever intend upon doing more then one image, I would highly suggest seperating stuff out from the beginning with future images in mind (so it would need to be a logical seperation, stuff that you know ALL images will get goes in common.catalog, etc).

If you only have one image and will always have only one image, then you could definitely put it in to one catalog and not worry about it. At the very least, I would leave 10.6_vanilla alone and make your image.catalog include 10.6_vanilla. That way, you can grab an updated vanilla from the instadmg google code site and not have to sieve through the changes and figure out what needs to be updated and what doesn’t, etc.

So at the least, 10.6_vanilla.catalog –> MyImage.catalog and at the most (and for multiple images) I would do 10.6_vanilla–>Common.catalog–>BaseLab.catalog (Shared between several lab images for instance)–>SpecificImage.catalog (Specific software beyond the base.catalog).

Again, that is my preference. I’m always looking for ways to make it less painful for myself in the future and I find that splitting things out in a smart manner saves a bunch of cutting and pasting between catalogs down the road.

Nate

[dead2sin]

[QUOTE][u]Quote by: chops[/u][p]So it’s Saturday and here I am. I decided to try to create my image differently, the InstaUp2Date way. Tried to checksum my custom pkgs (three createUser and the ClearReg) and got this in the terminal:
[code]sltools:InstaUp2Date chop$ ./checksum.py /instaDMG/InstallerFiles/InstaUp2DatePackages/* > checksums.txt
Traceback (most recent call last):
File “./checksum.py”, line 71, in
progressReporter.update(taskMessage=dataLine)
File “/instaDMG/AddOns/InstaUp2Date/Resources/displayTools.py”, line 105, in update
self.outputChannel.seek(lengthToOverwrite * -1, 1)
IOError: [Errno 22] Invalid argument[/code]
I’m using instadmg 384 in SL 10.6.4 on an iMac Intel Core 2 Duo.

Neglecting the home and family for yet another weekend… 😕 [/p][/QUOTE]

Does it work on a single package?

Also, SVN shows that the latest version is 334. Where is the 384 number coming from? I tested using checksum.py on a single file and a whole folder using the latest SVN and it worked.

Nate

[dead2sin]

This is in rough form, but here is a basic guide for customizing a Firstboot.pkg:

[url]http://www.osxdeployment.info/wiki/Firstboot_Package_Guide[/url]

Nate

[dead2sin]

That is a good resource that Allister linked there. I use Greg Negle’s blog for reference a lot due to his great documentation on the various issues that we all run into eventually. That Packagemaker template will work quite well if you can get the postflights figured out. I’ll write up a Composer Guide for the firstboot package when I have time (Beginning of the semester rush right now, so things are rather hectic).

I prefer Composer personally, but as Allister said PackagerMaker has become more then capable with the last couple of updates and Packages looks very promising as well. InstallEASE also has a free packaing app if I am not mistaken. The only reason I chose to mention Composer in that guide was because its my main go-to Packaging App simply because I’ve used it for the past 2 years and don’t feel like learning PackageMaker 😀

Let us know if you get the firstboot package working or if you have issues getting it going.

Nate

[dead2sin]

Updated guide specifically for CS5 + Acrobat 9 Pro:

[url]http://www.osxdeployment.info/wiki/CS5_Repackaging_Guide[/url]

Nate

[dead2sin]

[QUOTE][u]Quote by: Allister[/u][p]Hey Nessts,

I believe Nate’s referring to InstaUp2Date 10.6 vanilla catalog, which really is (at this point) a separate moving piece. While you may have used 10.6.3 media for the BaseOS image, InstaUp2Date would have pulled down many recent updates. Let us know which version of InstaDMG you’re using(and InstaUp2Date along with the catalog file being referenced if applicable.) Thanks,

Allister[/p][/QUOTE]

Ah, you are right 🙂 I’ve never used JUST InstaDMG, so I always assume everyone uses InstaUp2Date as well 🙂

[dead2sin]

If you built the image using InstaDMG, it should have applied all the latest updates on the image. The 10.6_vanilla.catalog gets updated as updates are released (normally in a timely manner).

Nate

[dead2sin]

I used Composer to package Final Cut Studio 3 and it worked just fine. I’ve never packaged just Final Cut Pro by itself, but I can’t imagine it would be worse then the whole FCS.

Are you packaging it using before and after snapshots or by watching changes in the file system? I can’t remember which InstallEase supports.

[dead2sin]

[QUOTE][u]Quote by: nobrainer[/u][p]I actually just ended up packaging with casper. Now when I deploy it and run off our local (hidden) admin account – all the apps except iPhoto work – which gives an error about no permissions. I assume it’s because of the admin account is hidden?
[/p][/QUOTE]

I just got iLife 09 working with InstaDMG straight out of the box today. The only side effect was that it made an iMovie Previous folder which was easily deleted with a payload less package.

[dead2sin]

Ah, I am not sure about that. I’ve repackaged iLife 09 using Composer before (With updates) and it seemed to work alright.

[dead2sin]

I’ve not baked in iLife 09 to my images for a while now, so I have not had a chance to try it, but they have a catalog file for the iLife 09 Updates and I believe you can use the iLife 09 DMG and InstaDMG will install it straight away.

The catalogs:

[url]http://tiny.cc/nb6co[/url]

I believe it will mount a .dmg of the iLife 09 DVD, then install the .mpkg as usual. Give it a shot and see how it works.

Nate

[dead2sin]

[QUOTE][u]Quote by: sumita[/u][p]Hi Nate,

Snapshotting workflow is not supported by AAMEE as of now.[/p][/QUOTE]

I’m not really interested in what Adobe says is supported or not, I’m more interested in what the AAMEE packages are capable of, which is why I try it. I am not snapshotting the install, I’m trying to use the AAMEE package directly with InstaDMG. I am currently building a snapshot package of CS5 + Acrobat 9 so I can install it using InstaDMG. I have done this many times with CS4 and now I am on my second build for CS5. Regardless of the fact that adobe does not support his method, I can confirm that not only does it work it works [i]well[/i], which cannot be said for Adobe’s “Supported” methods of installation. The whole point of InstaDMG is to make images that have never been booted and don’t require installs upon booting and Adobe’s methods of installing CS5 simply do not allow this. I’ve read over their documentation and I am well aware of what they would like me to do, but I find their suggestions unacceptable.

Nate

[dead2sin]

Nope! Nothing in Applications related to dreamweaver. Oh well, it got my hopes up that it didn’t error out, but I should of known better then to think it would [i]actually[/i] work 🙂

Nate

[dead2sin]

They JUST released an updated version of the AAMEE that fixes the bug where someone must be logged in. I just ran a test on InstaDMG and it reported in the log (AAMEE did) that it installed successfully. I’ll report back after I get a chance to apply the image if it worked or not 🙂

Nate

[Author]

Posts