MacNN Forums (http://forums.macnn.com/)
-   Mac OS X (http://forums.macnn.com/mac-os-x/)
-   -   Leopard Install Woes: Blank Blue Screen After Install (http://forums.macnn.com/90/mac-os-x/351999/leopard-install-woes-blank-blue-screen/)

 
Kenstee Oct 26, 2007 05:17 PM
Leopard Install Woes: Blank Blue Screen After Install
Installing on a PB 1.67. 2megs of RAM. Running 10.4.10. Ran Disk Warrior before install.

After doing a Upgrade Install it reboots
- Gray screen for a few seconds then...
- Blue screen for 1 sec then...
- Blue Screen again then nothing. Waited over 1/2 hour. Noticed my fans running hard and lots of heat

What I've done so far...

- Shut down
- Started up from Install disk
- Run Disk Utility (no problems found)
-Tries to do it again with same results

I do have a full clone on my FW external so not worried.

Anybody have any similar experiences or suggestions?
 
Kenstee Oct 26, 2007 05:32 PM
This is a major issue not just an isolated case...........

Apple - Support - Discussions - Installation appears stuck on a plain ...
 
cSurfr Oct 26, 2007 07:52 PM
Quote, Originally Posted by Kenstee (Post 3515752)
This is a major issue not just an isolated case...........

Apple - Support - Discussions - Installation appears stuck on a plain ...
The problem with this is that if you read the macrumors forums, 3/4 of the people that pirated leopard ended up with a bad copy that would do exactly this. And since today is launch day, I would guess that at least half of those posts are people that downloaded it and are trying to use apple support since it's officially released now. . .
 
placebo1969 Oct 26, 2007 11:32 PM
Quote, Originally Posted by cSurfr (Post 3515942)
The problem with this is that if you read the macrumors forums, 3/4 of the people that pirated leopard ended up with a bad copy that would do exactly this. And since today is launch day, I would guess that at least half of those posts are people that downloaded it and are trying to use apple support since it's officially released now. . .
My sister who has the full retail version was having the same problem. There is speculation that the Unsanity APE preference is causing the problem. I helped her with an Archive and Install and if finally worked.
 
zerostar Oct 26, 2007 11:42 PM
Had the same problem on my Powerbook G4, NOT A PIRATED COPY. Did not have APE (or any unsanity stuff installed) nor many non-stock things. I was thinking maybe it was UNO installed? I too did an archive and install and it works fine now. so something in the system. Hopefully we figure it out soon, Id like to upgrade my tower next.
 
Cadaver Oct 26, 2007 11:46 PM
Did it for me, too, today. Attempted an Upgrade install on my MacBook Pro. Perfectly legal copy - no pre-releases ever installed. No APE. No funny 3rd party extensions. Ended up doing an Archive and Install on top of it all. Works fine now and didn't lose anything (fortunately).

Did an Archive & Install on my Mac Pro from the beginning... no problems.
 
zerostar Oct 26, 2007 11:53 PM
These seem to be the culprits...

1. Reboot into single-user mode (hold Cmd-S while booting machine)
2. Follow the directions OSX gives you when you get to the prompt (I think these were them - just type the two commands it tells you to):
fsck -fy /
/sbin/mount -uw /
3. Remove the following files:
rm -rf /Library/Preference Panes/Application Enhancer.prefpane
rm -rf /Library/Frameworks/Application Enhancer.framework
rm -rf /System/Library/SystemConfiguration/Application Enhancer.bundle
rm -rf /Library/Preferences/com.unsanity.ape.plist
4. Exit, to continue booting normally
exit

I didn't have unsanity programs installed but did have some components in my previous system folder so who knows what program put them there...
 
Wiskedjak Oct 27, 2007 12:15 AM
So, the Leopard install is causing a blue screen of death? How ironic, especially given the BSOD joke icon they chose to represent Windows PCs!
Oh Apple, you card: Browsing networked Windows PC’s shows blue screens of death | Bus error: Jake Billo's weblog
 
TheJoshu Oct 27, 2007 12:45 AM
Same problem for me. Tried it twice. The third time, I erased the whole drive, started from scratch, and then moved over my user items from my backup drive. What a mess.
 
macJim Oct 27, 2007 09:01 AM
Thanks zerostar, It took me a couple of tries and some reading up on unix commands but learned new things and fixed the problem.

man that blue blue screen was ugly, wanted to call MS and complain, LOL.
 
83caddy16v Oct 27, 2007 11:47 AM
RE: Same with our iMac
MacBook Pro did not have the blue screen but our 2ghz Core Duo iMac did. I just let the blue screen sit there for 10mins or so and when I came back to the computer and it eventually was in OSX. (legit family pack)

Overall, the performance of Leopard on our iMac is sluggish. It takes a while to open windows and browse through directories. I may end up doing a clean install
 
quiklee Oct 27, 2007 02:05 PM
so i have the blue screen as well . . . . i have a legit copy that I bought yesterday after waiting in line . . . . the blue screen just sits there and does nothing . . . .

how do you do the archive and install?
 
zerostar Oct 27, 2007 04:11 PM
Look up a couple posts and try that fix.
 
Todd Madson Oct 27, 2007 08:45 PM
Ack!
Can I hit someone in the head here people?

Here's where this problem came from: Audio Hijack Pro from Rogue Amoeba
software which uses the piece of crap APE Unsanity garbage.

I followed the instructions here and was able to uninstall it but my machine
went into thermal runaway and on boot OS X crashed.

After a lengthy rebooting process it appears that my administrator privileges
no longer work with my administrator account.

I'm also apparently no longer able to log in as root.

The supposed Leopard introduction never showed.

And I'm not completely sure what or what else is broken.

But yeah, get rid of that Unsanity / Ape garbage and you'll at least be able to
boot.

Going back into single user mode to try and force admin rights on my account.
 
larrinski Oct 27, 2007 09:44 PM
Quote, Originally Posted by zerostar (Post 3516177)
These seem to be the culprits...

1. Reboot into single-user mode (hold Cmd-S while booting machine)
2. Follow the directions OSX gives you when you get to the prompt (I think these were them - just type the two commands it tells you to):
fsck -fy /
/sbin/mount -uw /
3. Remove the following files:
rm -rf /Library/Preference Panes/Application Enhancer.prefpane
rm -rf /Library/Frameworks/Application Enhancer.framework
rm -rf /System/Library/SystemConfiguration/Application Enhancer.bundle
rm -rf /Library/Preferences/com.unsanity.ape.plist
4. Exit, to continue booting normally
exit

I didn't have unsanity programs installed but did have some components in my previous system folder so who knows what program put them there...
That is what I found to be the problem! Doing an Archive and Install worked for me...
 
Todd Madson Oct 27, 2007 11:35 PM
Update:
I did manage to get my system administrator privileges back but did indeed
had to go back into single user mode to change the root password so I could
use it to authenticate my main account.

What a headache, I spent hours messing with this. I don't know if I should
yell at Rogue Amoeba for using the Ape stuff in their software, the APE people
for not following the rules of normal software development or Apple for not
testing it.

I figure the software developers should have had a copy of Leopard well in
advance of release to at least test their wares. Yipes.
 
C.J. Moof Oct 27, 2007 11:53 PM
Quote, Originally Posted by Todd Madson (Post 3517090)
Can I hit someone in the head here people?

Here's where this problem came from: Audio Hijack Pro from Rogue Amoeba
software which uses the piece of crap APE Unsanity garbage.
That part is worth repeating. I've read the "APE is the cluprit" posts online, but knew I never chose to install it. Now I know that Rogue Amoeba did it for me, and that my MacBookPro will break if I don't either pull that, or archive and install (which is how I got my iMac working after the blue screen....).
 
Todd Madson Oct 28, 2007 12:25 AM
Right. I think the piece of software Rogue Amoeba has put together is nice but they've opted to
use a piece of programming hack type software that can cause issues.

The biggest issue is this:
-Both the developers of Audio Hijack AND APE should have had copies of Leopard to test
their software on prior to release day.

-It would seem that one or both either didn't have a copy of Leopard to test this against
so the real question is: why did this become such a show-stopper?

And yes, mine also was a paid-for off the shelf copy of Leopard:
http://pod.ath.cx/leopard.jpg

It's easy to say "Oh, pirates downloaded it and they're the ones experiencing this" but
in my opinion this will happen to anyone who upgrades legitimate or pirate alike with
this software installed.
 
C.J. Moof Oct 28, 2007 01:43 AM
No, it's definitely not just a pirate problem. I waited in line for an hour to get my copy.
 
Chuckit Oct 28, 2007 01:48 AM
Quote, Originally Posted by Todd Madson (Post 3517300)
Right. I think the piece of software Rogue Amoeba has put together is nice but they've opted to
use a piece of programming hack type software that can cause issues.
Opted? As though Apple offers any other choice.
 
Todd Madson Oct 28, 2007 01:49 AM
Perhaps I'm being harsh here but there's more than one way to program a computer.

The developers had plenty of time to plan for this - apparently it wasn't tested or
Apple pulled the rug out from under them at the last minute.
 
larrinski Oct 28, 2007 01:54 AM
Here is a just released story on the APE problem...
 
Todd Madson Oct 28, 2007 02:02 AM
Interesting. The link to get the "working" version prompts you for an id and a password.

Then the link to their website does the same thing.

Someone got angry?
 
Chuckit Oct 28, 2007 02:04 AM
Quote, Originally Posted by Todd Madson (Post 3517379)
Perhaps I'm being harsh here but there's more than one way to program a computer.
And there are many ways to travel, but most of them will not get you to the moon. Do you think you could make an Audio Hijack clone using only supported API?
 
Todd Madson Oct 28, 2007 02:39 AM
Sigh
So you're saying the way it is being done is the only way to do it? I don't buy it.

But also, there shouldn't have been this problem in the first place.

How many people spent hours trying to get their systems to boot?

Looks like the Unsanity people got the word out on FRIDAY. Insanity.

They were still downloading the developers copy of the final image?

Sigh. They should have had it before but apparently they didn't get it.
 
Chuckit Oct 28, 2007 02:50 AM
Quote, Originally Posted by Todd Madson (Post 3517420)
So you're saying the way it is being done is the only way to do it? I don't buy it.
Not the only way, no. But there isn't any way that wouldn't qualify as a "system hack." (Or at least there hasn't been — for all I know, maybe they finally released one in Leopard.)

Quote, Originally Posted by Todd Madson (Post 3517420)
Looks like the Unsanity people got the word out on FRIDAY. Insanity.

They were still downloading the developers copy of the final image?

Sigh. They should have had it before but apparently they didn't get it.
Yeah, no kidding. I have no idea why Apple didn't give developers access to the OS until after it was in consumers' hands. Seems like you'd want to do it in the other order.

Anyway, glad people got it figured out. I can imagine how annoying it must be to get bit by this.
 
deedar Nov 7, 2007 03:21 PM
Me too...
I also got the BS of death on my PM G5 dual 1.8. Now, I don't have enough room on my drive to do an archive and install. Can I install OSX on a separate internal drive and boot from there so I can clean off some files from my original boot drive? How do I do this? Any help would be greatly appreciated.

Thanks
 
All times are GMT -4. The time now is 12:20 PM.

Copyright © 2005-2007 MacNN. All rights reserved.
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2015, vBulletin Solutions, Inc.


Content Relevant URLs by vBSEO 3.3.2