Post by: hingyfan on November 25, 2007, 11:51:36 AM
The attempted install was on a g5 imac (not Win).
Im on a g4 PB now that never gets much use so maybe that's the bright side.
Bascially i got a blue screen when trying to restart. Ran disc utility off both the Leopard and original discs. They said ok.
I just tried reinsalling Leopard and it failed! Said Essentials not found (or sonething, i'll write ir down next time as I'm trying it yet again.
I think my extended warranty is still in effect but not sure. Of course this being a Sunday i couldnt call anyway.
Thanks for listening!
Post by: Mayo on November 25, 2007, 12:26:50 PM
A well-known cause of this problem is Application Enhancer and it is mentioned in the above document.
Post by: hingyfan on November 25, 2007, 01:54:32 PM
QUOTE(hingyfan @ Nov 25 2007, 05:51 PM) <{POST_SNAPBACK}>
Topic title says it all, except i was until 6 trying to get rid of it.
The attempted install was on a g5 imac (not Win).
Im on a g4 PB now that never gets much use so maybe that's the bright side.
Bascially i got a blue screen when trying to restart. Ran disc utility off both the Leopard and original discs. They said ok.
I just tried reinsalling Leopard and it failed! Said Essentials not found (or sonething, i'll write ir down next time as I'm trying it yet again.
I think my extended warranty is still in effect but not sure. Of course this being a Sunday i couldnt call anyway.
Thanks for listening!
The attempted install was on a g5 imac (not Win).
Im on a g4 PB now that never gets much use so maybe that's the bright side.
Bascially i got a blue screen when trying to restart. Ran disc utility off both the Leopard and original discs. They said ok.
I just tried reinsalling Leopard and it failed! Said Essentials not found (or sonething, i'll write ir down next time as I'm trying it yet again.
I think my extended warranty is still in effect but not sure. Of course this being a Sunday i couldnt call anyway.
Thanks for listening!
Thanks. i also came across this. it seems the command line solution is the easiest.
one question. in this command:
/sbin/fsck -fy
/sbin/mount -uw /
rm -rf /System/Library/SystemConfiguration/ApplicationEnhancer.bundle
reboot
Is there a space after bundle going into reboot? They should turn these things without making such things clear.
Im on way to work now and will try this when i return late tonight. in the meantime, i hope to see some more suggestions flooding in.
Thanks again.
Post by: Xairbusdriver on November 25, 2007, 04:16:38 PM
QUOTE
Is there a space after bundle going into reboot?
No. AFAIK, the only time there is no space between 'words' is when there is a combination of commands or in a path. "bundle" is part of a path. But "reboot" is a command that is on a separate line. The line above it says to 'remove' "ApplicationEnhancer.bundle" and provides a path to it.A word to other would-be upgraders: Always read posts/threads by those who have done an upgrade/update before doing it yourself. If you are going to wait for the bleeding-edgers to 'bleed' you might as well see how much 'blood' they lose!
While the command line action is the 'easiest' plan now, it would have been even easier to have followed the advice of others to delete that file manually before doing the install (several times). TS (and a few other sites) are great for helping you out of trouble, they are even better at not letting you get into trouble in the first place. Believe me, I speak from experience! 
Post by: hingyfan on November 25, 2007, 04:53:09 PM
And i checked in on the status of Leopard. MAybe i missed it but all i saw were concerns about Super Duper.
Since ive run into this problem, i've read that it is a huge one, swamping apple's lines.
You would think they would run an update to take care of it in advance, since it is a known issue. I did run an update early yesterday afternoon, which is maybe why i thought of Leopard when i hit the mall yesterday.
Hey maybe even a caution flier at the store would help but it might make one customer think twice about speaning $129 on an application that hasnt been properly tested.
Post by: Mayo on November 25, 2007, 05:35:08 PM
The Application Enhancer problem has been mentioned here a number of times and has been included on the various Web sites people have linked to that list Leopard compatibility glitches. But you can't be expected to keep track of everything when it comes to these things, so if I were you I wouldn't feel at all bad about missing it. At least it is something that can be fixed relatively easily, even if it is a pain the rear... My impression is that there aren't very many TSers who use APE, but more than a few of us use SuperDuper! so it is more likely to come up in this forum. And some people aren't even aware that APE is on their system since it is usually installed as part of a software package that requires APE in order to function properly.
Post by: hingyfan on November 25, 2007, 07:05:23 PM
Now i realize what Application Enhancer is. I thought it was somehow part of the mac package even though it is third party.
Post by: Xairbusdriver on November 25, 2007, 09:32:26 PM
Since I do use and thoroughly enjoy some of Unsanity's products, so I naturally knew about it. And, even if you'd searched here for "ApplicationEnhancer" you might not have found anything. 