mbp c2duo hangs in boot off of winxpsp2 cd

[junrelya]

hello,

i've got a macbook pro core2 duo 2.33ghz system and wanted to try bootcamp. so i got completely through until the last reboot before it comes up in xp and you need install the apple hw drivers. at this point, it won't boot the windows paritition at all, nor the win xp cd anymore. if i try to force it, it spins up the disc, shows an apple logo (no spinner underneath) then just sits there, getting hotter (fan getting louder) until i turn it off by holding the power down for a few seconds. it DID boot off the cd once, so i know it CAN, but it just WON'T anymore. anyone had this problem?

i've removed and recreated the windows partition, no luck. still won't boot off winxpsp2 cd again. i've booted off the osx install cd, so i know that's ok. i've reset the nvram. i've tried everything i can think of. please help!

osx: 10.4.9
firmware: MBP22.00A5.B01
smc version: 1.12f5

thank you!

[---neo---]

It seems i am experiencing a bug of the same kind, but during the first boot on the XPcd : Bootcamp doesn't "see" the wincd (which is in the drive), and i can only choose the main os X Partition.
And moreover, the fan gets crazy too!

mac book core2duo 2G, OS 10.4.9

Is there something with the 10.4.9 update?

[junrelya]

i've tried the rEFIt package from http://refit.sourceforge.net. this yielded slightly more info when i tried to boot the windows xp cd that i verified DOES boot in a pc:

Starting Legacy Loader
Using load options 'CD'
Error: Unsupported returned from legacy header
Error: Not Found from LocateDevicePath (repeat 7 times)
Fatal Error: Not Found while opening our install directory

i don't know what that's all about.

[junrelya]

in system profiler, my Boot ROM Version is MBP22.00A5.B01

on this page: http://docs.info.apple.com/article.html?artnum=303880

for the macbookpro 15" core 2 duo, it says the latest firmware is MBP22.00A5.B00

i'm all confused. i can't find any firmware updates that, when downloaded and run, don't say, "your computer doesn't need this update."

[Paul2660]

Just a few thoughts:

1. Can you test the XP CD on another PC? You won't hurt anything, just boot up to the first screen where XP will ask if you want to install. This is just to make sure that the CD is still bootable.

2. If possible, see if you can get a different XP CD. You can install with another CD and have the 30 days left to register. You can then register with your 1st CD's codes.
y
3. If you have blown the Entire XP partition away while in Boot camp under OSX and you still can't get XP to start, the only thing I can think of is to totally reload the machine with the OSX load. If you haven't installed alot on the mac side, this won't take too long, obviously if you have it's another matter.

Net, there are alot of strange things IMO that can happen during this process of loading XP and even after you get it up. If all else fails by starting with a fresh load of OSX you might get it to work.

One note on the 1st post, After XP has finished loading and makes the 2nd reboot (final one), you should come up into XP before you use the boot camp drivers disc. XP will give you alot of yellow !'s stating it can't find this and that. You then run the drivers as an .exe. This will launch off all the drivers in a process and XP will start to discover the devices. It's not a totally clean process IMO, as I would rather have the ability to address each device and update it's driver from the CD.

Paul C

[junrelya]

i did try it on a pc, it worked. i have the image file, straight from MSDN, so i burned another, just to make sure the media wasn't bad. i tried that one on a pc also. unfortunately, i've loaded the osx side up to the brim. i do still have my old pbook, and i can save off the mail i've received interim, but it would be a huge pain to have to wipe and reinstall.

i'm not sure i understand how data on one partition (that the efi shouldn't even be looking at yet) can adversely affect the boot process when trying another partition; however, i freely admit my ignance when it comes to efi and the mbpro's boot process in general.