G
Guest
Guest
Ok, I got the same board as mentioned in the title of this thread.
Specs - Athlon 1.4ghz (bought 2 days ago)
Asus a7v133 mobo (2 days old)
Infineon 256 megs of pc133 cas 2 ram
30 gig maxtor ATA100
13 gig maxtor 66
300watt ps
Geforce 2 gts asus v7700
Soundblaster live value
NIC (cruddy @home version)
16x dvdrom Pioneer
17" samsung mon
4x4x32 acer burner
Now, here's my prob.
Booted up, loaded up win98, everything detected fine. Got everything running again, since it was an upgrade, not a new comp.
Restarted, did the same for windows 2000 base install.
Now, I went into the System BIOS afterwards to disable ATA100 for the time being, as neither of my drives has that capability, and it was eatin' up my boot up time. I disabled the bios setting for the ATA100, and did a restart afterwards. Here's where it screws up. Cpu fan starts up, nice 'n loud, system does a short beep, then completely shuts down. Completely. No warnings, no nothing. Now, keep in mind, I've had it running for almost 30 minutes now, so it can't be heat related at this point.
I've tried resetting the cmos, but it doesn't seem to do anything either.
I don't know whats wrong now!
help!!!
-Bill
Specs - Athlon 1.4ghz (bought 2 days ago)
Asus a7v133 mobo (2 days old)
Infineon 256 megs of pc133 cas 2 ram
30 gig maxtor ATA100
13 gig maxtor 66
300watt ps
Geforce 2 gts asus v7700
Soundblaster live value
NIC (cruddy @home version)
16x dvdrom Pioneer
17" samsung mon
4x4x32 acer burner
Now, here's my prob.
Booted up, loaded up win98, everything detected fine. Got everything running again, since it was an upgrade, not a new comp.
Restarted, did the same for windows 2000 base install.
Now, I went into the System BIOS afterwards to disable ATA100 for the time being, as neither of my drives has that capability, and it was eatin' up my boot up time. I disabled the bios setting for the ATA100, and did a restart afterwards. Here's where it screws up. Cpu fan starts up, nice 'n loud, system does a short beep, then completely shuts down. Completely. No warnings, no nothing. Now, keep in mind, I've had it running for almost 30 minutes now, so it can't be heat related at this point.
I've tried resetting the cmos, but it doesn't seem to do anything either.
I don't know whats wrong now!
help!!!
-Bill