I did an archive & install first. After install, I began installing my apps; One of those included Logitech Control Center (which installs Application Enhancer). Upon reboot, the machine never booted to the internal disk (automatically booted to one of the other disks I had plugged in running 10.4). While in 10.4, my new 10.5 disk did not appear bootable in the Startup Disk application. So, I popped the 10.5 DVD back in and did an upgrade install. Needless to say, everything, including Logitech Control Center & Application Enhancer are working fine. No issues on bootup, etc.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Leopard Install Blue Screen - CONFIRMED Solution
- Thread starter oliverlubin
- Start date
- Sort by reaction score
i havent got any of them installed on my macbookpro yet once i've double clicked on the install button and it tells me to restart i get the grey screen then dont even get the option to do a fresh install.
Here's something strange...
I have the LCC installed and do NOT have the unsanity apps installed with it. I know I never deleted them in the past, so I guess the version of LCC I have didn't need it or didn't install it. I don't have any of the files listed as the problem files for the Leopard Install. Now I'm waiting for my Leopard install disc...
Is it weird that I have a Logitech Control Center and not the other bad parts?
I have the LCC installed and do NOT have the unsanity apps installed with it. I know I never deleted them in the past, so I guess the version of LCC I have didn't need it or didn't install it. I don't have any of the files listed as the problem files for the Leopard Install. Now I'm waiting for my Leopard install disc...
Is it weird that I have a Logitech Control Center and not the other bad parts?
Logitech Mouse Drivers and other hidden dangers
To all the people who didn't install APE and are still planning to upgrade. Do a Spotlight search for "Application Enhancer" and see what comes up.
I have never knowingly installed APE or any other system hack, but just found two folders, one called "Application Enhancers" and one called "ApplicationEnhancer.loginPlugin"
For me it looks like it came as part of the Logitech mouse drivers I installed, though no mention of them was ever made in the installation.
After looking around my system and doing a more thorough search based on suggestions here, I have found and deleted the following folders and files:
"Application Enhacers"
"ApplicationEnhancer.loginPlugin"
"ApplicationEnhancer.bundle"
"ApplicationEnhancer.framework"
"com.unsanity.ape.plist"
"Logitech Control Center.prefPane"
If this happened with something as seemingly innocuous as mouse drivers, it could happen with other mundane installations. I encourage people who have not installed to look at the third-party software on their system even if it's from a reputable vendor.
To all the people who didn't install APE and are still planning to upgrade. Do a Spotlight search for "Application Enhancer" and see what comes up.
I have never knowingly installed APE or any other system hack, but just found two folders, one called "Application Enhancers" and one called "ApplicationEnhancer.loginPlugin"
For me it looks like it came as part of the Logitech mouse drivers I installed, though no mention of them was ever made in the installation.
After looking around my system and doing a more thorough search based on suggestions here, I have found and deleted the following folders and files:
"Application Enhacers"
"ApplicationEnhancer.loginPlugin"
"ApplicationEnhancer.bundle"
"ApplicationEnhancer.framework"
"com.unsanity.ape.plist"
"Logitech Control Center.prefPane"
If this happened with something as seemingly innocuous as mouse drivers, it could happen with other mundane installations. I encourage people who have not installed to look at the third-party software on their system even if it's from a reputable vendor.
Just to make things clear: if I'm on Tiger, not having installed Leopard yet, will doing an Uninstall using Application Enhancer's own uninstall-option protect me from this bug? Or will I have to do it via Terminal?
I have a tendency to always screw things up when messing around in there, so if a normal install will clear me of the problem beforehand I'd be much more happy
I have a tendency to always screw things up when messing around in there, so if a normal install will clear me of the problem beforehand I'd be much more happy
Just to make things clear: if I'm on Tiger, not having installed Leopard yet, will doing an Uninstall using Application Enhancer's own uninstall-option protect me from this bug? Or will I have to do it via Terminal?
I have a tendency to always screw things up when messing around in there, so if a normal install will clear me of the problem beforehand I'd be much more happy
I found out about APE 2.0.3 not causing Leopard issues just yesterday afternoon, after I upgraded to Leopard. Before I upgraded to Leopard on Friday, though, to play it safe I uninstalled every system hack I had installed, even if it didn't use APE (when in doubt, uninstall!). When I did uninstall APE, I used the included uninstaller. Additionally, I upgraded using the Archive and Install option (which I always do with OS upgrades). So far I have yet to encounter any problems.
Unsanity
Hi all, thanks much for your posts, they are very useful.
Unsanity just updated their blog, the information may be relevant to a few people:
http://www.unsanity.org/archives/haxies/leopard.php#comments
BTW, I have been using many of their programmes for years, but never encountered any serious problems.
Hi all, thanks much for your posts, they are very useful.
Unsanity just updated their blog, the information may be relevant to a few people:
http://www.unsanity.org/archives/haxies/leopard.php#comments
BTW, I have been using many of their programmes for years, but never encountered any serious problems.
Application Enhancer
I received the following from Unsanity.
We wanted to send out some information to our mailing list subscribers about Mac OS X 10.5 and Unsanity's Application Enhancer.
First and formost. *Before* you install Mac OS X 10.5, make sure you have Application Enhancer (APE) 2.0.3 or later installed. You can download it from http://www.unsanity.net/ape-203.dmg (the webpage is at http://unsanity.com/haxies/ape ).
Make *sure* you have APE 2.0.3 or later installed *before* you install Mac OS X 10.5. If you have an earlier version of APE installed before you install 10.5, you may exhibit one of the following symptoms upon booting into Mac OS X 10.5:
- Your goldfish may die.
- A strange dog might bite you on the street.
- A friend may punch you.
- Your computer may catch fire.
- Your loved one may leave you.
All of these things are really bad. So we urge everyone to make sure they have APE 2.0.3 or later installed. If you aren't sure, install APE 2.0.3 or later from the link above. APE 2.0.3 was released on March 14th, 2007. And please, always keep your software up to date.
A note about 10.5 and haxies:
As long as you have APE 2.0.3, nothing bad will happen in 10.5. Well, nothing we can control. However, none of your APE Modules will work either.
Developers in Apple's Mac OS X developer program (ADC) got the final 10.5 GM yesterday. We are still downloading the huge 6.66GB image and as soon as the downloads finish for our developers, we will be hard at work on making our software work on 10.5.
You can keep up to date with the status of haxies and 10.5 by viewing http://unsanity.com/products/compatibility/ and we will post more information as we have it on our blog at http://unsanity.org/ . Mac OS X 10.5 compatibility is currently our number one priority.
"If APE doesn't work in 10.5, shouldn't I just uninstall it?"
No, you should not. Just make sure you have APE 2.0.3 or later. A lot of third party (and Unsanity made) utilities depend on the APE framework itself being there. As it has some extremely useful functions. Removing it may cause these Applications and/or preference panes to stop launching.
For more information on Unsanity haxies, please visit:
http://www.unsanity.com/haxies/
Unsanity LLC is the creator of other popular haxies such as WindowShade X, ShapeShifter, FontCard, Mighty Mouse, Menu Master, FruitMenu, Xounds, Dock Detox, and Silk. Unsanity is dedicated to providing quality software for the Macintosh community.
-Rosyna of the Unsanity Team
I received the following from Unsanity.
We wanted to send out some information to our mailing list subscribers about Mac OS X 10.5 and Unsanity's Application Enhancer.
First and formost. *Before* you install Mac OS X 10.5, make sure you have Application Enhancer (APE) 2.0.3 or later installed. You can download it from http://www.unsanity.net/ape-203.dmg (the webpage is at http://unsanity.com/haxies/ape ).
Make *sure* you have APE 2.0.3 or later installed *before* you install Mac OS X 10.5. If you have an earlier version of APE installed before you install 10.5, you may exhibit one of the following symptoms upon booting into Mac OS X 10.5:
- Your goldfish may die.
- A strange dog might bite you on the street.
- A friend may punch you.
- Your computer may catch fire.
- Your loved one may leave you.
All of these things are really bad. So we urge everyone to make sure they have APE 2.0.3 or later installed. If you aren't sure, install APE 2.0.3 or later from the link above. APE 2.0.3 was released on March 14th, 2007. And please, always keep your software up to date.
A note about 10.5 and haxies:
As long as you have APE 2.0.3, nothing bad will happen in 10.5. Well, nothing we can control. However, none of your APE Modules will work either.
Developers in Apple's Mac OS X developer program (ADC) got the final 10.5 GM yesterday. We are still downloading the huge 6.66GB image and as soon as the downloads finish for our developers, we will be hard at work on making our software work on 10.5.
You can keep up to date with the status of haxies and 10.5 by viewing http://unsanity.com/products/compatibility/ and we will post more information as we have it on our blog at http://unsanity.org/ . Mac OS X 10.5 compatibility is currently our number one priority.
"If APE doesn't work in 10.5, shouldn't I just uninstall it?"
No, you should not. Just make sure you have APE 2.0.3 or later. A lot of third party (and Unsanity made) utilities depend on the APE framework itself being there. As it has some extremely useful functions. Removing it may cause these Applications and/or preference panes to stop launching.
For more information on Unsanity haxies, please visit:
http://www.unsanity.com/haxies/
Unsanity LLC is the creator of other popular haxies such as WindowShade X, ShapeShifter, FontCard, Mighty Mouse, Menu Master, FruitMenu, Xounds, Dock Detox, and Silk. Unsanity is dedicated to providing quality software for the Macintosh community.
-Rosyna of the Unsanity Team
It is worth noting that there is another problem/solution to this problem. Renaming DIVX folders. This can be done at the command line and has solved a number of users who were having these problems.
https://forums.macrumors.com/threads/375870/
http://discussions.apple.com/thread.jspa?threadID=1197076&tstart=105
https://forums.macrumors.com/threads/375870/
http://discussions.apple.com/thread.jspa?threadID=1197076&tstart=105
leopard problems!!!
hi all,
i just bought a new macbook on friday and it had the leopard disk in thebox to install over tiger, so i did a clean install, because i had nothing on the computer yet, and leopard worked fine...up until today when i got the blue screen. So i called apple support and they said to do an archive and install, which i was in the process of, up until about 20 mins ago when i got an error message saying that leopard could not be installed to my hard drive. I have no idea what's going on, im a new mac user. I'm typing this from my iPhone...which is great btw. Any ideas why leopard can't be reinstalled on my HD? What should i do.
thanks everybody
hi all,
i just bought a new macbook on friday and it had the leopard disk in thebox to install over tiger, so i did a clean install, because i had nothing on the computer yet, and leopard worked fine...up until today when i got the blue screen. So i called apple support and they said to do an archive and install, which i was in the process of, up until about 20 mins ago when i got an error message saying that leopard could not be installed to my hard drive. I have no idea what's going on, im a new mac user. I'm typing this from my iPhone...which is great btw. Any ideas why leopard can't be reinstalled on my HD? What should i do.
thanks everybody
Hi All,
I don't seem to be getting any where with the blue screen issue. Is it possible to re install a previous operating system, back up all of my file (should have done this in the first place) then reformat the had drive. Then install 10.5
The issue that I am having is that some of the files seem to be read only.
Also i'm in the middle of moving house so my brain has stopped working, to many heavy boxes and sofas up many many stairs
Many Thanks
Keith
I don't seem to be getting any where with the blue screen issue. Is it possible to re install a previous operating system, back up all of my file (should have done this in the first place) then reformat the had drive. Then install 10.5
The issue that I am having is that some of the files seem to be read only.
Also i'm in the middle of moving house so my brain has stopped working, to many heavy boxes and sofas up many many stairs
Many Thanks
Keith
There are a few lessons here.
Before you ever do a major upgrade/install, plug in your backup drive and make a bootable backup using SuperDuper or CarbonCopyCloner. If something goes wrong, you merely go back.
Check your System Preferences. Try to make sure everything is up to date.
When something like this is discovered, don't go crazy and start assuming every add on is going to cause a similar freeze. I'm reading things like "I'm going to uninstall every add-on". Go ahead but it's a waste of time and if you're fiddling around in the Terminal you could do harm just trying to prevent harm. (A bit like the 'repair permissions' snakeoil that is suggested for basically everything).
If you have been affected by this problem, here's what to do.
Go to Insanity's website and upgrade to 2.0.3. That's it. (Or do an uninstall).
If you can't boot up then you only need to remove ONE APE file, and that's the one in the system folder. (Do not use the Terminal if you can boot-up use the instruction above.)
Boot up in safe mode and type:
rm -rf /System/Library/SystemConfiguration/ApplicationEnhancer.bundle
[Hint: expand with the Tab key - this will stop mistypes; example
rm -rf /Sy then hit the tab key etc]
Apple cautions against installing anything in the System folder, and so clearly the ApplicationEnhancer.bundle
is breaking this rule. However, Unsanity may argue that the architecture of OS X doesn't allow developers to make certain changes without going into the system which is perhaps why there are no nice extensions to customize the Apple Menu (except Unsanity) AFAIK.
For me, I couldn't live without WindowShade (which John Siracusa also raves about), so it's a bit harsh to call the APE manager a piece of crap or what-have-you. If you have the latest version of APE manager it does nothing harmful. This issue has only affected those with outdated versions.
Before you ever do a major upgrade/install, plug in your backup drive and make a bootable backup using SuperDuper or CarbonCopyCloner. If something goes wrong, you merely go back.
Check your System Preferences. Try to make sure everything is up to date.
When something like this is discovered, don't go crazy and start assuming every add on is going to cause a similar freeze. I'm reading things like "I'm going to uninstall every add-on". Go ahead but it's a waste of time and if you're fiddling around in the Terminal you could do harm just trying to prevent harm. (A bit like the 'repair permissions' snakeoil that is suggested for basically everything).
If you have been affected by this problem, here's what to do.
Go to Insanity's website and upgrade to 2.0.3. That's it. (Or do an uninstall).
If you can't boot up then you only need to remove ONE APE file, and that's the one in the system folder. (Do not use the Terminal if you can boot-up use the instruction above.)
Boot up in safe mode and type:
rm -rf /System/Library/SystemConfiguration/ApplicationEnhancer.bundle
[Hint: expand with the Tab key - this will stop mistypes; example
rm -rf /Sy then hit the tab key etc]
Apple cautions against installing anything in the System folder, and so clearly the ApplicationEnhancer.bundle
is breaking this rule. However, Unsanity may argue that the architecture of OS X doesn't allow developers to make certain changes without going into the system which is perhaps why there are no nice extensions to customize the Apple Menu (except Unsanity) AFAIK.
For me, I couldn't live without WindowShade (which John Siracusa also raves about), so it's a bit harsh to call the APE manager a piece of crap or what-have-you. If you have the latest version of APE manager it does nothing harmful. This issue has only affected those with outdated versions.
This is easily the best thing I did. While the glitch was annoying and there was a good twenty minutes of "WTF!" I knew I could always go back and fix it, my data was safe.
And, since the terminal instructions didn't quite work, I just booted from my drive and went about working the problem, which was simply to hunt down and kill APE and then reboot from the internal drive. Although now I realize that was excessive and I only needed to remove, as macgruder suggests, the ApplicationEnhancer.bundle.
Now, I realize that I did two things wrong:
1. I should have checked to see if APE was updated, and to see if there were problems with it.
2. And, I should have taken the time to assess my software and see if there were going to be any hiccups. For instance that I was running an old version of APE for Clear Dock.
However, I realize that in my zeal to install Leopard, I skipped these steps and wasted a good bit of time, but I had a safety net.
If you don't have a backup you can boot from you either don't care about your data or you are insane.
Wow, that was a bit of a scare, i have no idea how this program got onto my comp, probably logitech
I would like to thank GOD from the IRC chat room who talked me through it .
Cheers mate
I would like to thank GOD from the IRC chat room who talked me through it .
Cheers mate
I'm having this same stupid problem, and I've tried to fix it using this solution but this is what hapens:
Either I get this "rm illegal option --/ usage rm [-f | -i]
So I tried it with rm -f..... and got some other syntax error.
When I added a space between -rf /library.... then when I hit enter, I didn't get a syntax error but nothing happen.
Same happens for all of the files.
Is it possible I just don't have the Enhancer files?
The irony of the situation is that my Boot Camp partition still works properly so I'm in XP on my mac and thankful to have it.
HELP!
Either I get this "rm illegal option --/ usage rm [-f | -i]
So I tried it with rm -f..... and got some other syntax error.
When I added a space between -rf /library.... then when I hit enter, I didn't get a syntax error but nothing happen.
Same happens for all of the files.
Is it possible I just don't have the Enhancer files?
The irony of the situation is that my Boot Camp partition still works properly so I'm in XP on my mac and thankful to have it.
HELP!
This is really pissing me off. I tried removing all files related to "Application Enhancer" (which I NEVER installed) and "unsanity" (I have no idea what that is, either). I managed to find ONE whole file, a crashlog.plist file, but none of the other files that people in this thread have mentioned were found. Yeah, it's possible that I might have some "incompatible third-party software" on my hard drive because, y'know, I don't only use applications that were made by Apple. But how am I supposed to know which applications are causing the problem?
In the meantime I have a useless iBook paperweight. I can't get past the blue screen of death, and I can't reinstall Leopard because the installation brought me down to 3.5gb of free space (from about 10.5gb free) and for SOME reason reinstalling it will require ANOTHER 9.5gb. GG Apple.
In the meantime I have a useless iBook paperweight. I can't get past the blue screen of death, and I can't reinstall Leopard because the installation brought me down to 3.5gb of free space (from about 10.5gb free) and for SOME reason reinstalling it will require ANOTHER 9.5gb. GG Apple.
It's not just the Application Enhancer stuff, or ShapeShifter, or DivX, it can be anything.
As I said above, I found the culprit to be the "driver" for my Eikon USB Fingerprint Reader.
Just do an Archive & Install.
As I said above, I found the culprit to be the "driver" for my Eikon USB Fingerprint Reader.
Just do an Archive & Install.
I can't do an Archive & Install because I don't have enough disk space. I can't do an upgrade because I don't have disk space. I can't do a clean install because I have no way of backing up my data (I can see it's all intact, via terminal). Is it in any way possible to move my data from the iBook to a shared folder on my PC? I could even boot into a Linux LiveCD distro if that's possible.
The Dreaded Blue Screen
Had the same blue screen-freezing problem...
If you have another mac working fine, booting the problem mac in target-disk mode on the other macmakes erasing the files much easier. (Hold down T when booting). After deleting the unsanity files she booted up fine! Thankfully
______________
PowerMac G5
PowerBook G4
MacBook G4
Had the same blue screen-freezing problem...
If you have another mac working fine, booting the problem mac in target-disk mode on the other macmakes erasing the files much easier. (Hold down T when booting). After deleting the unsanity files she booted up fine! Thankfully
______________
PowerMac G5
PowerBook G4
MacBook G4
Ugh...I had this same problem. I don't want to ever have to go through that again! lol It was bad enough the one time...
how does one uninstall application enhancer? if i hit the troubleshooter and do it that was will this problem not exist?