- This topic has 40 replies, 8 voices, and was last updated 14 years, 4 months ago by
dead2sin.
-
AuthorPosts
-
November 19, 2010 at 7:15 pm #379938
Brigandy
ParticipantIf you do not install “iLife 09”, the “iLife 09 Support 9.0.4” update (along with all the other Mac OS X 10.6.x updates) will install fine and there are no issues.
November 19, 2010 at 7:17 pm #379939dead2sin
ParticipantiLife support 9.0.4 installs fine for me via InstaDMG. I have it as part of one of my catalogs and it doesn’t ask for 9.0.4 upon firstboot.
Nate
November 19, 2010 at 7:19 pm #379940Brigandy
ParticipantAll of the resolutions (mentioned above) do not work.
November 19, 2010 at 7:20 pm #379941Brigandy
Participant[QUOTE][u]Quote by: dead2sin[/u][p]iLife support 9.0.4 installs fine for me via InstaDMG. I have it as part of one of my catalogs and it doesn’t ask for 9.0.4 upon firstboot.
Nate[/p][/QUOTE]
Like I said before, you have a different version of iLife 09 or you do not have iLife 09 even installed.
November 19, 2010 at 8:07 pm #379943ndpete
Participant[QUOTE][u]Quote by: Brigandy[/u][p]
Like I said before, you have a different version of iLife 09 or you do not have iLife 09 even installed.[/p][/QUOTE]Which iLife09 package are you running? I have the same issue. Here is sha1 of my package: sha1:d21feae38398b52b982a5586ba0b1168534343ce
Is it just this package that has issues? Why did it work and then just not work?
I’m waiting for a build to finish and give it another test.
November 19, 2010 at 8:34 pm #379944Brigandy
ParticipantiLife 09 iLife ’09 Install DVD.dmg sha1:de8d2d59ad22a9de65142531ce1318e42cb62c88
November 19, 2010 at 9:15 pm #379945dead2sin
Participant[QUOTE][u]Quote by: ndpete[/u][p][QUOTE][u]Quote by: Brigandy[/u][p]
Like I said before, you have a different version of iLife 09 or you do not have iLife 09 even installed.[/p][/QUOTE]Which iLife09 package are you running? I have the same issue. Here is sha1 of my package: sha1:d21feae38398b52b982a5586ba0b1168534343ce
Is it just this package that has issues? Why did it work and then just not work?
I’m waiting for a build to finish and give it another test.[/p][/QUOTE]
This is exactly the same sha1 hash that I have for my iLife 09 .mpkg.
Nate
November 19, 2010 at 9:59 pm #379948ndpete
ParticipantI’ve finally built a successful build. In which the update was applied as it was supposed to. I probably need to run another test or two but I think I know what was causing the issue. I try to build my images with my Xserve, with the internal raid It was my fastest solution. The build I just did that worked I ran from a Clean Macbook install with a firewire external for scratch. No cache and it took FOREVER but the build had the iLife Update applied. 🙁 Must be something with the xserve that instadmg didn’t like…or possible just 10.6.5 server that created the conflict..sigh 🙁 well looks like I’ll have to get used to 4 hour builds…. haha Thanks for the help…
November 19, 2010 at 10:58 pm #379950dead2sin
Participant[QUOTE][u]Quote by: ndpete[/u][p]I’ve finally built a successful build. In which the update was applied as it was supposed to. I probably need to run another test or two but I think I know what was causing the issue. I try to build my images with my Xserve, with the internal raid It was my fastest solution. The build I just did that worked I ran from a Clean Macbook install with a firewire external for scratch. No cache and it took FOREVER but the build had the iLife Update applied. 🙁 Must be something with the xserve that instadmg didn’t like…or possible just 10.6.5 server that created the conflict..sigh 🙁 well looks like I’ll have to get used to 4 hour builds…. haha Thanks for the help…[/p][/QUOTE]
Yea, Karl has always said to build images on 10.6.5 Client OS. He can’t promise it will work perfectly on 10.6.5 Server.
Nate
November 20, 2010 at 3:29 pm #379957ndpete
ParticipantFunny how it just affected the iLife Support update.
November 20, 2010 at 6:56 pm #379958Brigandy
Participant[QUOTE][u]Quote by: ndpete[/u][p]Funny how it just affected the iLife Support update.[/p][/QUOTE]
Where did you place the “iLife Support 9.04” update (in what catalog and in what order)?
November 22, 2010 at 4:26 pm #379978ndpete
ParticipantI had a catalog that first ran the Vanilla catalog then it installed iLife.mpkg then right after that it installed the iLife Support 9.04 update then it installed the rest of iLife updates.
November 22, 2010 at 4:39 pm #379980Brigandy
Participant[QUOTE][u]Quote by: ndpete[/u][p]I had a catalog that first ran the Vanilla catalog then it installed iLife.mpkg then right after that it installed the iLife Support 9.04 update then it installed the rest of iLife updates.[/p][/QUOTE]
Wow, I have the same “exact” setup as you and when I restore the image to a brand new iMac 27″, the “iLife Support 9.04” still needs to be installed via Software updates.
When I create the image, it’s on a 10.6.5 Mac that has no RAID. It’s a simple setup. I use InstaUp2Date to create my image and the InstaUp2Date logs show me that the “iLife Support 9.04” was installed successfully, but once the image is restored, the “iLife Support 9.04” needs to be installed again.
Screw it. I’m tired of this issue. I’m moving on. 😐
November 22, 2010 at 4:45 pm #379981ndpete
ParticipantPost your logs and let us look through them. Also which Install disc are your running from? 10.6 or 10.6.3? I also made a switch from a 10.6 install disc to 10.6.3. not sure if that would affect it much it might!
Edit:
Other things i did was completely delete instadmg. Checked out a fresh version from svn. Re-imported Install disc. Also Re-checked sum my iLife package and the update package. Might help…November 22, 2010 at 4:49 pm #379982Brigandy
Participant[QUOTE][u]Quote by: ndpete[/u][p]Post your logs and let us look through them. Also which Install disc are your running from? 10.6 or 10.6.3? I also made a switch from a 10.6 install disc to 10.6.3. not sure if that would affect it much it might![/p][/QUOTE]
I’m using a retail 10.6 disk. I have a retail 10.6.3 disk but i’ve never used it with InstaUp2Date.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed