Netserver 4/100 LC hangs up

[Max_11]

I have an HP Netserver 4/100 LC.
After turn on power, the Server beeps, shows the message "EISA Configuartion EISA - RUN EISA Configuration Utility". When he is ready with beeping, the screen is cleared an there appears a half "58" in the upper left corner and the system hangs up.
The Server don't access the Disk drive or another drive.
What is wrong with my Netserver?

[Greg Carlson]

Max,

Try these steps first, Change the CMOS battery, that machine is old enough to need a new one if that hasn't already been addressed.

Next, with the server powered off and unplugged for 5 minutes flip switch 3 to the OFF position. Leave the switch to the Off position and power the server on until you get a message that your configuration has been cleared. Then power the server back off and unplug and flip switch 3 back to the ON position.

Then boot to the ECU disk that you create from: http://www.hp.com/cgi-bin/cposupport/swindex.pl?p=hpnetserve5436&l=en&c=BIOS Save the file to your desktop and double click on it to extract it to a diskette. It will create a bootable diskette. Boot to the ECU and save and exit.

If this still doesn't resolve the issue the CPROM may need to be replaced.

Good luck,
Greg

[Greg Carlson]

Max,

Sorry I forgot to add to create the BIOS diskette at the same time as creating the ECU diskette off the previous post link and after you clear CMOS and saving config flash the bios and see if that resolves the issue.

On a side note, if you have any EISA cards you will need to reinstall the .cfg files associated with those cards as well.

Ciao,
Greg

[Max_11]

Hi Greg,

thank you for the answer.
After reswitching the "Config valid"-switch, the Netserver starts without beeping. But he hangs up after showing the message "Real Time Clock error". No disk access.
After restarting he began once again with beeping (2-2-3-1, unexpected interrupt-test error).
Is that possible, that the BIOS-EEPROM is defect?

[Greg Carlson]

If you've changed the system battery and you are still getting those errors its either the System ROM or the System Board that have failed and I would start with the System ROM first as the suspect cause.