Jump to content

Leopard Start up


aweber2
 Share

8 posts in this topic

Recommended Posts

I have installed Leopard on my 12" 1.5 GHZ Powerbook 1.25 GB of Ram and the install seemed to go smoothly but after I restarted and after the Gray screen with the Apple Logo and the spinning thing under neather that it's suppose to go the the screen where it says welcome to Mac OS X and show was is starting up but it doesn't do that it just shows a blue screen. I can move the mouse around and that is it. Has any one expereinced this any what can I do to fix it with out erasing the hard drive of my Powerbook? Let me know PLEASE.

Link to comment
Share on other sites

You get it working? Im experiencing the same problem. Anyone know where first aid is in the files? I don't want to have to burn a disc (Installed right off the hard drive), but if I have to I'll go buy a DL DVD and try that out.

Link to comment
Share on other sites

on my macbook, i had leopard installed fine, im quadbooting so reinstall is not an option unless i want to start from scatch Again ;)

i installed adium and growl and cleardock. resulting in teh issue you describe.

booted into single user, deleted cleardock prefs and growl and removed adium from startup itiems, still no good.

as soon as aqua starts it just sits there with no login.

Link to comment
Share on other sites

I had this exact same problem. I did a safe boot (hold down shift when you restart) and that seemed to fix the problem. Then I went into system preferences and turned off auto-login. From then on, leopard would boot ok.

 

Interestingly, I had the blue screen with mouse and nothing else problem even booting off the SL leopard minus xtools disc I burned. I ended up simply installing it onto another volume while booted into tiger (i.e. running the installer manually). It hung at the end of the BSD install part (which seems to be a common problem), but I simply force quitted the application that installer was infinitely waiting for (using Activity monitor sorting applications hierarchically to identify the offending app) and everything carried on as normal. Note, that I waited until the process had finished doing whatever it was supposed to be doing (by watching disk and cpu activity) before force quitting it.

Link to comment
Share on other sites

 Share

×
×
  • Create New...