Hope it works! Hate to see you stop with mudmoving!
:ernae:
Cees
:ernae:
Cees
Changed both the MB & CPU (I had already succeeded in returning to windows after the new installs).Did you change MB + CPU and not do a reinstall of XP or is it Vista? Did your HD's have the wide(1 1/2") ribbon or the sata (3/8") ribbon? If your new MB has different chipset you'll need to do a reinstall of OS. In BIOS it should give you choice of IDE or Sata. Oh, by the way, in BIOS did you select drive to boot from?
Except that I was running Vista. I have a restore disk from the original system, but since changing MB and CPU it no longer wants to work. If I could find my XP disk I would just do a clean install of XP and be done with it. . .never mind the fact, that all of my FS purchases over the last 6 years are housed on the C drive with no back up."hal.dll" is part of XP startup and I think from memory it has something to do with hardware, if you are on XP you could try a repair using your XP install CD but you will need to sellect boot from CD in bios hopefully on boot your mouse and keyboard should work to allow you to repair.
Changed both the MB & CPU (I had already succeeded in returning to windows after the new installs).
Both drives use the narrow SATA jumpers
I assume it does have a different chipset
No such options in BIOS, right now, using auto-detect it doesn't find either HDD and so while I did select to boot from the HDD, since it doesn't recognize either one, it simply doesn't boot now.
It's now giving me a different message that the reason windows was unable to start was because the file "hal.dll" is either missing or corrupt.
Except that I was running Vista. I have a restore disk from the original system, but since changing MB and CPU it no longer wants to work. If I could find my XP disk I would just do a clean install of XP and be done with it. . .never mind the fact, that all of my FS purchases over the last 6 years are housed on the C drive with no back up.
I'll never learn, lol.