[bw38]

So I’ve updated the document once again. I’d like to say it’s pretty much all I could include. Wish I had some feedback on the InstaDMG.bash stuff, but this will do I hope. It’s a 36 page document/guide/reference whatever you wish to call it. I’ll probably take a look at it one more time tomorrow for minor changes but I don’t think I’ll be adding more info unless anyone else feels like contributing. I think it contains a lot of the information that many of us have accumulated over time. I sincerely hope others find it useful. At the very least, I hope my coworkers find it somewhat useful.

I submit it to the community as a Word document. Whether it gets used or not, I’ll leave up to you guys.

[bw38]

It sounds like you want to know how to do a checksum. The easiest way to do this is using checksum.py which lives in ~/InstaDMG/Addons/InstaUp2Date/ – so open up Terminal and type:
cd ~/InstaDMG/Addons/InstaUp2Date/
./checksum.py ~/InstaDMG/InstallerFiles/InstaUp2DatePackages/HPprintdrivers.pkg

Of course if your InstaDMG folder is not in ~, change the directory accordingly in Terminal. Likewise, be sure to reference the specific HP printer pkg file name.

The checksum format will look like as an example:
CreateLionUser CreateLionUser.pkg sha1:83b4357037d82a254c5ef068c384e3fb2c1

You can copy that entire line from the Terminal window into the catalog. Just make sure it is tab-separated (including the tab prior to CreateLionUser…). And yes, there is a tab between pkg and sha1.

Hope that helps. Also, if you’re new, take a look at this documentation I’m working on: https://www.afp548.com/forum/viewtopic.php?showtopic=29466
It’s still a draft at this point, but perhaps it could benefit you.

[bw38]

adminMHS that was really good stuff in that post. I included your post and the one you referenced (which is also referenced in the Installer Choices read me). I think the more examples the merrier. And glad to hear you like the draft so far.

The document is definitely longer now at 24 pgs. Daunting I know! But it’s not just a guide, it’s also documentation which will definitely be referenced more than once as newcomers get started.

I wouldn’t say it’s complete quite yet, but maybe 95% done. I’d definitely like to add more to the instaDMG.bash portion. Not sure if anyone else wants to chime in here.

[bw38]

Did you import the InstallESD.dmg into InstaDMG? To do so, just mount it and run the import command (first page of documentation included in svn).

[bw38]

Guess I’m not alone in having issues:

In Snow Leopard:
It’s not installing the right version. It installs version 10.1 even though it is version 10.3 that is being used. I’ve confirmed that the pkg is legit by running it manually. If I go directly to the System Preference pane, it will say I am running 10.1. If I do a check, it tells me to upgrade. If I open up Firefox it even tells me that one of my plug-ins needs to be updated pointing to Flash 10.1. After updating manually, everything is good to go and I’m listed as running 10.3.

In Lion:
It displays the Flash pane in System Preferences, but when I go to detect what version is running, none are actually running! If I open up Firefox to detect whether its installed, nothing shows up at all for it under the plug-ins. After updating manually, everything is good to go and I’m listed as running 10.3.

Should I be re-packaging Flash?

[bw38]

It’s been a while since I baked my last image but once again I find myself not being able to get Communicator 13.1.2 to work! I thought I was going crazy when I said it worked with 13.1.1, but suddenly stopped working. But now I know for fact that something is screwy here.

The last time I created an image with InstaDMG was on Aug 1, 2011 using svn rev 420. Suddenly I checked out the latest svn (rev 425) for InstaDMG and it just stopped working. Just to note when I check out the latest svn, I download it to a new folder all together and manually move over any of my the catalogs, packages, etc. to the new InstaDMG folder. But I don’t believe this should be causing issues. Someone correct me if I’m wrong on that.

It’s rather minor in the grand scheme of things, but it drives me nuts that everything else in the image works fine except this one update (which worked at one point but not anymore). I’ve upload a zip file with two debug logs from rev 420 and rev 425.

http://www.woofiles.com/dl-263064-DlQcnpRz-InstaDMGdebugfile.zip

There’s definitely a lot more activity going on when it gets to the point of installing Communicator 13.1.2 in rev 420 compared to 425. But I’m not entirely sure what it means if anything at all. Any ideas here?

[bw38]

I actually had this happen recently too when I used the Office 2011 SP1 iso from Microsoft. I just got my hands on it and decided to test it out, but it didn’t work. I didn’t really get to dig too much into it though since I have the original Office 2011 installer which works fine for me. I’m not sure if others have had similar issues either.

Could you tell us what installer of Office 2011 you’re using? And which patchers you’ve applied to it?

[bw38]

Just to confirm, InstaUp2Date is now fully compatible with OS X Lion and InstaDMG?

[bw38]

I believe a few months ago there was an issue people were having with the order of the iLife Support update. And it wouldn’t install when used in the iLife catalog. Of course I don’t know if that’s still the case, but that was the experience with it a few months ago. I think so long as people installed the iLife Support update before iLife was installed and the other iLife updates, everything would work fine (at least that has been the case for me).

[bw38]

With Communicator 13.1.2 out, it seems the patcher works again. I tested this twice and both times the latest version was installed. You do need to install Communicator 13.1.0 before 13.1.2.

The update can be downloaded here: microsoft.com/download/en/details.aspx?id=26835

[bw38]

I wanted to confirm that the iLife Support 9.0.4 update is definitely needed.

I just created a new image today and excluded that from the vanilla catalog. But as soon as OS X booted to desktop, Software Update ran and asked to install the iLife Support 9.0.4 update.

So, if possible, please don’t remove it from the 10.6 vanilla catalog:
[code]iLife Support 9.0.4 h*tp://support.apple.com/downloads/DL1009/en_US/iLifeSupport904.dmg sha1:7cda1492d1bab91383b5738a7cda2cde24f72d2c[/code]

[bw38]

Out of curiosity, wouldn’t the recovery partition contain a restore DMG that could be used in InstaDMG?

[bw38]

[QUOTE][u]Quote by: Allister[/u][p]I heard they don’t come with USB sticks, so…
You can always just punt: boot a fresh-from-box new mini in target disk mode, pull off the cruft you don’t need and run createUser against it, then image that.
The usual warning applies, only restore that image to the new hardware please.

Oh, and what’s the build # on the new mini’s?

Allister[/p][/QUOTE]
What you’re suggesting is essentially the old way of imaging if I’m reading this right, correct? In other words, we have to make two images: one of the Mac Mini and the other of the MacBookAir.

[bw38]

[QUOTE][u]Quote by: Allister[/u][p]I don’t mean to sound harsh here, but…
See the difference between the iTunes sha1’s? This is why there’s a cooling off period. Apple deprecated the first iTunes the day after release, although both download links are still active in the cdn.
Also, FYI the iLife support update is not necessary for 10.6.8. Thanks to n8 and bw for posting, it helps me verify sha1’s and all that, I do appreciate it.

Allister[/p][/QUOTE]
Not harsh at all. I didn’t know Apple did that with updates. Also, the iLife support update for some reason was included on the svn I had downloaded (still included as of this writing). That’s the only reason I had included it in my post. May want to take a look at that when you get a chance. Glad the updates helped you out.

[bw38]

Just wanted to post that I created a basic wiki article outlining how to include Office 2011 into InstaDMG using the patchers that have been discussed in this thread. I encourage anyone to make any necessary modifications to the article. Wiki can be found here: http://www.osxdeployment.com/wiki/Office_2011

With that said, I have been unable to get Communicator 13.1.1 to work with the patchers. Has anyone else had luck getting it to work?

[Author]

Posts