StarDestroyer.Net BBS

Yep, my hard drive was failing for a good few weeks, so i finally went out and got a 200 gig one from scan. Got it home, put it in the place my old 60 gig was, everything was going fine, installed windows xp from a legit copy, all was working fine.

Started to run all the driver setups and whathaveyou that I'd been backing up to my other hard drive through the ages, running windows updates and the like, restarting periodically, all fine.

-THEN- the second hard drive started disappearing, the POST only detected the 200 gig, and severely slowly too, if the old hd was still connected. If I disconnected it, the POST was all fast as usual. If the second hard drive was the only drive in, it would find it, but put any other drives on on either IDE ribbon, and it would be lost again.

This was on thursday night, and as you might guess, i was getting severely pissed off, so i just yabked the power cable out the back and went to bed. Wake up friday morning and it finds them both but fails to get to windows. Kept breaking on the twelfth loading thing on the windows loading screen (I counted).

So I try to start up on safe mode, and it stops at mup.sys.

So I try to format and reinstall etc several times, each time it gets stuck when it examines the 200 gig drive.

For reasons unknown, it gets past that part sometimes and successfully formats and I reinstall xp (a few times, as those who will be noting how much i've been on msn lately could probably tell from my activity).

Currently, I can't even get xp installed, it keeps crashing on the "xp makes your pc more reliable" page of the install, ironically.

So far, these problems have only started after I installed the nvidia nforce mobo drivers, though it could be a bit of a post-hoc rationalisation to blame it on those.

Any ideas where to go from here?

sounds like it could be a combination of viruses and/or BIOS conflicts. . .did you scan for viruses before installing the new drive and do you have the most updated BIOS for your mobo?

Darth_Zod wrote:sounds like it could be a combination of viruses and/or BIOS conflicts. . .did you scan for viruses before installing the new drive and do you have the most updated BIOS for your mobo?

I scanned for viruses when I got the new drive working, it did find one, but that was due to me connecting to the internet and not fixing the whole remote procedure call e-sodomy stuff first.

The BIOS thing, well, I've not downloaded a BIOS update, so that's probably a good idea.

Hmm, the asus BIOS updates aren't downloading, does anyone know where i can get some? My motherboard is an a7n8x deluxe by the way.