if you are using an OEM disc then that is why, apparently... get a retail or VL copy and repair from that.
already did using retail disc gave me the recovery console, which the OEM did not, but i still can't get the repair screen
well it should give it to you, the only reason it would not i would think is if you didn't actually have xp installed... otherwise it should come up if xp is on a partition may be corrupt beyond recognition lol
Boot from your CD and follow the directions to start Recovery Console. Then: Attrib -H -R -S C:\Boot.ini DEL C:\Boot.ini BootCfg /Rebuild Fixboot
Can you boot to safe mode??? Just curious..Uninstalling IE8 could be a fix... If you can get to the recovery console command line, use this command: expand E:\i386\hal.dl_ c:\windows\system32 (E: is the optical drive your cd is in..change to suit your needs) If the Hal.dll error was the only problem (corrupt HAL) then this should fix it..
ok I deleted boot.ini, did /rebuild, then fixboot.. same problem restored hal.dll now restoring ntoskrnl.exe. what's next? who knows.
A winternals release that allows to access the windows install from cd. Very useful for replacing files, and will also allow to restore some installs..
if you absolutely must have somethings that are with your install, i would use a live cd of some kind and backup those files to another partition/usb drive and format and reinstall. i prefer a fresh install to having to fix unbootable problems in xp myself. and on decent hardware xp installs fairly fast.
I put the HDD on another system, ran virus scans (clean) and backed up the hard drive, now I'm gonna try ERD and system restore.
I forgot to provide some information when I got this I was told it had Windows 7 on it, so the first thing I did was Windows 7 startup repair. that didn't work (obviously) and I investigated further only to find out it has XP on it. also, when I got it was in AHCI mode. so what does this mean? it means either someone else changed it to AHCI trying to fix it, or it is supposed to be in AHCI. so what did I do by attempting all these repairs in Native IDE? totally screw it up? should I have been using F6 drivers? or does that just mean I have to change it back to AHCI before trying to boot? edit: how the heck can I tell if it's supposed to be booted in AHCI or Native IDE? I experience the same results either way.
I meant to say Startup repair, and it did run and failed saying there was a problem with the boot sector