This discussion is archived
89467 Views 408 Replies Latest reply: Jan 14, 2008 8:35 PM by CyberMac
Currently Being ModeratedNov 1, 2007 10:03 PM (in response to nitramluap)I ran into this problem upgrading our OS/X Server system to Leopard.
The troubling thing here is that, as a server, it had very little third party software installed on it. However, not wanting to completely mess up our server environment, mail, network settings, etc., I decided to try and solve the problem by looking for incompatible software.
I did NOT have DivX or ApplicationEnhancer installed.
However, I DID find DejaVu (a backup application) and Flip4Mac (a QuickTime codec). Despite reading (above) that Flip4Mac is not a problem, I decided to delete both of these.
That fixed the problem. So, add DejaVu and/or Flip4Mac to the list of problem software.G5, Mac OS X (10.3.x)
Currently Being ModeratedNov 1, 2007 10:30 PM (in response to Chris Mcculloh)I finally fixed the blue screen problem on my G5. It turned out that I had installed the application enhancer several years ago (probably on another machine and it got copied over since I carry everything with me). I hadn't used it since and it didn't show up in my System Preferences so I figured I didn't have it, but there were still a couple of preference files and such left over. Make sure you don't have any remnants or it will kill your system.PowerMac G5 DP 2.0Ghz, Mac OS X (10.4.7), 1.5GB RAM, 160+300GB SATA HDs, MOTU Ultralite
Currently Being ModeratedNov 2, 2007 4:03 AM (in response to cgrayson)
Guess I'll have to Archive & Install. Oh wait, first I have to use Terminal from the installer to go clear off enough disk space.
How much free space was on your drive prior to installing Leopard? As a rule thumb you should always have about 10% of the drive free for OS X's use for temporary files. If you don't have enough free space the OS won't work right. There is a warning built into the OS to tell you that the drive is getting dangerously full, but it is not foolproof -- it can only estimate this since many processes use the disk at the same time, especially after the first boot of a new OS while it is going through initialization of a huge number of processes.
If your drive was nearing the 90% full mark, it is possible the original OS would soon have been having problems even without the upgrade and/or given you the warning.iMac G5/2.0 GHz 17" ALS (Rev B), Mac OS X (10.4.10), 1.5 GB, Kensington Trackball
Currently Being ModeratedNov 2, 2007 4:07 AM (in response to Zacharias Beckman)
Zacharias Beckman wrote:
So, add DejaVu and/or Flip4Mac to the list of problem software.
I have both installed on my iMac G5 running Leopard with no problems. Although I have not tried to use DejaVu, Flip4Mac works OK, even though it is an older version.
Are you installing the Leopard server or regular version?iMac G5/2.0 GHz 17" ALS (Rev B), Mac OS X (10.4.10), 1.5 GB, Kensington Trackball
Currently Being ModeratedNov 2, 2007 7:28 AM (in response to nitramluap)I had the same problem, and no solutions from support, so here is what I did:
Copied everything off the drive to an external.
Wipe the drive and do a clean install of Leopard.
Manually move every single file over, replacing all that the system will allow you to. Normally you can do this in blocks to save time.
In SysPrefs, create a new user with the same shortname and password as the account that you copied over. Select the option to use the home folder that "already exists" there.
This took care of almost everything. I don't feel all that secure about, but that's why I still have a copy of everything on my external. Hopefully it should take care of any pervading issues.
*Note: I had two internal drives on my machine and accidentally installed Leopard on my storage drive instead of the startup disc the first time. This made for ownership issues on that disc that I'm still resolving. However, I don't see any reason the above process should be a problem for you.
Thought this might help. Good Luck!1.67Ghz - 17 PowerBook G4, Mac OS X (10.5), 2GB SD-RAMM
Currently Being ModeratedNov 2, 2007 11:35 AM (in response to Phill Horrocks1)I have never done a clean install on my mac. In the past I just went with the upgrade option on my disc. I just purchased Leopard, and I want a clean install on my system. Additionally, I have heard this is a good idea to do once a year, so I want to get in the habit. Thoughts? and How do you do this?iMac G4 20" Flat Panel, 1GB Ram, 1.25 Ghz processor, 250GB HD, Mac OS X (10.4.10), Airport Extreme, LaCie External 250GB HD, 60GB iPod
Currently Being ModeratedNov 6, 2007 7:35 AM (in response to Dan Bargen)I tried every solution proposed here and none worked. In the end, I had to do the same thing as you Dan. Firewire everything I needed backed up on another harddrive and do a clean install.
Unfortunately, I forgot to backup my Firefox bookmarks and archived email.
I'm just happy that I'm able to use my Mac again.iMac, Mac OS X (10.5)
Currently Being ModeratedNov 6, 2007 7:29 PM (in response to nitramluap)I have the same problem. Waiting won't fix the problem. Apple has blamed this problem on third party Application Enhancer software, but I have none on my recently purchased Mac Book. One solution is to do a new Archive and Install installation according to an Apple release but I can't boot after the failed installation from either the old or new operating system. I called Apple support, waited a half hour and then was disconnected in the call before learning much, apparently because quiting time had arrive on the west coast.Mc book, Mac OS X (10.5)
Currently Being ModeratedNov 7, 2007 4:55 AM (in response to jimf233)
Apple has blamed this problem on third party Application Enhancer software ...
Not exactly. Apple said that third-party "enhancement" software could be one cause of the blue screen hang, & specifically mentioned the ApplicationEnhancer.bundle in the advanced solution, but recommends an Archive & Install if that solution doesn't work. I conclude from that that any third-party bundles in /System/Library/SystemConfiguration are suspect. The contents of these bundles are loaded during startup, so any that are incompatible with Leopard could cause a hang.
But also note that Mac OS X 10.5: "Blue screen" appears after installing Leopard and restarting says Applications, plug-ins, and other software may have to be reinstalled after an Archive and Install, & to verify that each third-party software product is compatible with Leopard before reinstalling it, not just any application "enhancement" software.
One solution is to do a new Archive and Install installation according to an Apple release but I can't boot after the failed installation from either the old or new operating system.
Then why not boot from the Leopard Installer disk? With the disk inserted, you can try starting up while holding down the "C" key, or holding down the option key & selecting the disk if that doesn't work.
Message was edited by: R C-RiMac G5/2.0 GHz 17" ALS (Rev B), Mac OS X (10.5), 1.5 GB, Kensington Trackball
Currently Being ModeratedNov 7, 2007 5:21 AM (in response to nitramluap)I finally got past the blue screen disaster, by simply repeating the install by starting up the computer while holding down the "C" key as described in posts here. I mistakenly failed to select the "Archive and Install" but this second attempt worked and all is now fine. It is a little confusing to find my documents however, but they are there.Mc book, Mac OS X (10.5)
Currently Being ModeratedNov 9, 2007 12:18 AM (in response to Mark @ DTS)Mark's method worked like a charm for me the first time. I would suggest trying it first instead of the archive/reinstall. THANK YOU!!MacBook Intel, Mac OS X (10.5)
Currently Being ModeratedNov 9, 2007 1:06 AM (in response to Mark @ DTS)
This is what apple suggest...
The article with the suggestions (Mac OS X 10.5: "Blue screen" appears after installing Leopard and restarting) has been updated several times since Mark @ DTS quoted it here.
The command line solution has been updated to say to remove /System/Library/SystemConfiguration/ApplicationEnhancer.bundle instead of the individual enhancer files for a few days now. Yesterday, a third solution was added to the article, echoing suggestions here to use Target Disk Mode instead of single user mode to access the files for removal, & again suggests removing the bundle instead of the individual files.
Note that for either of these solutions, Apple says to do an Archive & Install if they don't work.iMac G5/2.0 GHz 17" ALS (Rev B), Mac OS X (10.5), 1.5 GB, Kensington Trackball
Currently Being ModeratedNov 16, 2007 6:11 PM (in response to R C-R)Both are kind of right:
a) the up-to-date version of APE isn't causing a problem, however, older versions do. So if you had APE installed and UPDATED, then upgrading to 10.5 isn't a problem. However, if you have an old version lingering on your hard drive, then you likely will have problems.
b) APE isn't always the problem. I have here a machine with verifiably no APE installed (I checked all the installation locations manually, and neither the APE framework, bundles or preferences are there), but still I get a blue screen.
The rest of our Mac OS X 10.5 non-server systems upgraded fine, but this one gives problems...
I will try putting it in target-drive mode and upgrading the volume to 10.5.1 that way, and see if that helps.PowerMac G5DP, MacBook Pro C2D, iMac G4, PowerBook G4, NeXT, Mac OS X (10.5.1)
Currently Being ModeratedNov 16, 2007 6:55 PM (in response to jimf233)Also getting the blue death screen. Here are my current issues:
1. Called Apple Support. Was on the phone for an HOUR AND A HALF. Guy did not even mention archive and install. He finally said he thought I had a defective disk and sent me a new one. Of course, same problem with new disk.
2. Cannot even get to archive and install screen b/c I get the blue screen before I get there.
3. Tried getting rid of the enhancement stuff. But, when I entered the codes, it said the mount was read only. I assume that's all of it b/c nothing came up. Then, it said it was checking this and that, then came back and said my hard drive was ok. That's it.
4. I'm going to try to boot up holding C, but I am really at a loss at this point. Disappointed in Apple for such a crappy release and completely annoyed with Apple Support.imac G5, Mac OS X (10.4.11)