Abit NF7-S v2.0 doesn't post...

[tHatDudeUK]

RMA'd board, now everything works...

 

[R.G. Saunders]

Hi,

Just stuck a new system together for my girlfriend and it doesn't work

All the system fans spin up including the graphics card's and the hard disk
spins up. There is no video output, the optical mouse doesn't light up when
plugged in to either the PS2 or USB ports. The keyboard lights flicker when
switching on at the PSU but there's no sign of activity when pressing the
switch at the front.

Once the system speaker beeped at a regular interval on and off. It seemed
to be about 2 secs interval between beeps. At all other times the system has
not beeped at all and could only be powered off by the PSU switch.

I have had the time to test the memory in my machine and it works fine so it
can't be that...

The fan is spinning on the graphics card so I presume it's working ok and
seated ok but will try test it on my machine.

Only other possibilities are a duff mainboard or a duff processor.

I've tried various combinations of the jumpers and connectors etc and using
the clr cmos jumper but no joy. I have also tried using only one DIMM and in
various slots etc.

I have no fan connected to the chassis fan connector as the case doesn't
have one. Would this cause this problem?

System spec

Abit NF7-S v2.0
Sapphire ATI Radeon 9600 pro fireblade E
256mb X 2 Twinmos cl2.5 PC3200
AMD Athlon 2500+ XP Barton
Antec 400 watt Psu.
Maxtor 120gb 8mb cache IDE.

Any help would be greatly appreciated...

Thanks in advance

Regards,

tHatDudeUK.

Just set up an NF7-S v2.0 - had almost exactly the same symptoms - no beeps,
no video, everything seemed to be running.
Went to the Abit site and used the method 3 for clearing the bios setup.
a. remove power cord
b. unplug ATX power cable from mobo
c. set CMOS jumper to clear
d. remove CMOS battery
e. went for a smoke. (smoke optional - just gave it a minute or two extra to
clear)
f. reinstall everything.
""Note"" - if you are using a WD 80GB drive (or similar) please check
jumper setting against the label on the drive, I made an unwarrented
assumption and left the jumper in the master position without a slave on the
same channel, it gave me nothing but grief as the boot cycle took 4-5
minutes and it wouldn't boot reliably from the HD. I removed the jumper when
I noticed the label settings and shortened the process to a matter of
seconds and it now boots properly from the drive instead of searching
endlessly for a slave on the channel. Working on these things for almost 35
years now, just goes to show you that fatigue and temper are a bad combo
with setting up a new system, regardless of experience.