corrupt/missing file - xp won't boot up

Question

corrupt/missing file - xp won't boot up

Hello,

I am unable to boot into the bootcamped Win XP. I get the message <<Windows could not start because the following file is missing or corrupt
C:\windows\system32\config\system.
You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair.>>

It won't boot into Safe Mode either, or into Last Known Configuration, or into any of the other F8 options. It won't boot up with the original Windows CD either (valid, non-OEM). I want to run Windows Recovery Console to attempt a repair.

Should I try through Bootcamp Assistant? If the Windoows CD is bad or unreadable in some way (which is what I suspect, judging by the scratch marks), then Bootcamp Assistant is not going to make a difference. Is there any other way to to repair Windows or run chkdsk?

MacBook Pro 15", Mac OS X (10.5.5)

Posted on Nov 13, 2008 2:38 AM

Reply

Answer 1

Nov 19, 2008 3:53 PM in response to SouthernCross

I've had the same problem twice; the first time I ended up re-installing windows via Bootcamp after a Mac OS X became corrupt. Now, the problem has recurred after clean install of both OS's. I've tried Parallels & Fusion to run the Windows XP OS virtually, and obtain same error as you do. What's weird is that the Windows OS runs fine when booting directly into Windows. I'm as puzzled as you, and hope to get useful replies going!

Reply

Answer 2

Nov 20, 2008 9:38 AM in response to Peter Willard

Having got no reply to my post, I decided to do some tweaking of Windows myself, knowing that if I didn't succeed, I'd have to reinstall XP, which I was resigned to do in any case as a last resort. So I copied the missing/corrupt file in question from Windows\repair directory and using Paragon NTFS pasted it into the windows\system32\config directory. Bootcamp Windows now booted up, all seemed to be working fine, and I reinstalled the Apple drivers. After a restart, however, I found that neither the trackpad nor the keyboard were working (both of which were working before the restart). Restarted again, and got a hal.dll missing/corrupt error! Restarted again in safe mode, no hal.dll error, but also no keyboard/trackpad functionality. The only saving grace is that Windows now boots up properly in Parallels with no errors and everything working.

From whatever little I've researched on this, it seems Parallels can screw up the boot.ini file. Apparently it makes changes to boot.ini which are fine for running Windows in Parallels, but not in Bootcamp. Well, whatever...... I think I'll just have to do a reinstall, and hope I have better luck than you.

Reply

Answer 3

Nov 21, 2008 6:11 AM in response to SouthernCross

thanks for your comments, SouthernCross; always helps to know where the problem lies (boot.ini); is that file generated in the BootCamp startup process? WinXP still runs fine on my system when directly booted into, but I can't run it through Parallels or VM Ware; I did try repair with Windows CD, reconstructed the boot systetm with BOOTCFG, and several other command line tips (obtained online), to no avail; if you have any other suggestions re. regenerating the system (I now get the can't find dll error) let me know, otherwise its wipe out Win XP and hope VM Ware doesn't foul up bootcamp when i use it as the Virtual system from scratch (earlier i'd used Parallels first).

Reply