Jump to content

Windows won't boot after Leopard Install..


8 posts in this topic

Recommended Posts

I installed Leopard onto a third primary partition on my computer, it prompted me to restart after installation and it started to boot up Leopard, i was met by a Grey Screen with the spinning wheel (setting this problem aside)

 

So i decided to try and boot up my trusted Win XP, i restarted again (through power down) and selected Win XP to boot up, however it cannot finish loading. It keeps getting stuck at this screen:

 

winxp_rc1_rev_02.gif

 

It stays stuck with this screen and NEVER moves forward onto this screen below

 

windows-xp-welcome-screen.jpg

 

(Note these are images taken from Google Image Search as examples, not my own)

 

I was wondering that this may be caused due to my Win XP partition not being set to Active, however i am unsure if this is causing the problem or whether it may be something different..

 

Thanks for any Help!

I have a question about your third party boot/partition software...

 

What Brand and version is it, did you install in windows XP?

 

Windows generally likes to be "active" and can have issues when it's not.

I was not using a third party bootloader etc, just Darwin bootloader which is auto installed through Mac installation.. however i used Acronis to partition my Hard Drive, but didn't set it to boot up or anything.

 

I was not using a third party bootloader etc, just Darwin bootloader which is auto installed through Mac installation.. however i used Acronis to partition my Hard Drive, but didn't set it to boot up or anything.

I used this guide - http://wiki.osx86project.org/wiki/index.ph...DualBoot_10.5.2

 

for dual booting XP and MacOSX. Everything went fine for me.

 

Try the Gparted CD.

 

I once had XP and Mac OS X installed and then followed instructions for OSX section step 19 onwards and Bootloading section (also make sure that the boot flag is not ticked for OSX). Worked for me.

 

19)Once it's done, you'll have to reboot. As it reboots, put the GParted CD in the drive.

20) Wait for it to load (window and all) then right-click on your Windows partition (it has a file system of NTFS). Click Manage Flags.

21) Tick the box for boot. Click OK.

21b) right-click on OSX partition. Click Manage Flags. Uncheck the box for boot.

22) Click quit on the desktop and when prompted, take the CD out. Reboot.

Thanks a lot! however, I'm still wondering whether it is actually this problem (the partition not being set to active) causing the problem..

 

Sorry, i previously forgot to mention, this happened a little while ago, i couldn't find an answer then, and resorted to reinstalling and losing everything :P

 

However, i shall keep this in mind if it happens again.

I am trying to chase it up and see what exactly caused the problem previously, so that it doesn't happen again if i reinstall.

 

Thanks everyone

I installed Paragon Hard Disk 2009, along with the Recovery CD, i tried making my booting C: (Win XP) partition inactive and rebooted, it did not lead to this problem.. instead i got MBR error. (note this is me trying to see effects of inactive)

 

So i rebooted with the CD and made the partition active again.. all fine and booting. Therefore it was not an inactive partition causing this...

 

So i done a bit of researching and a bit led to me corrupt user settings (which is possible) and also Alcohol 120 and Daemon Tools, which can conflict on boot-up and lead to the same issue that i had, no Welcome screen with User Profiles to log onto however a hang at the Windows Logo screen with the blue bar going from side to side.

 

I had both these softwares installed at the time. However, i will keep on researching to see if i can find other reasons which are possible. Also, through checking the boot order of Win XP, it shows that it could not have been an inactive partition due to the MBR recognising this. Sorry to have wasted time, i should have checked this earlier...

 

Open to any other suggestions. Thanks everyone!

 

Also just to mention - there were no error messages, ie no missing sys or dll files etc, just a hang

×
×
  • Create New...