topic Re: Armada 1592DMT 162-System options not set in Operating System - Microsoft

Armada 1592DMT 162-System options not set

Adrian Redmond — Mon, 19 Apr 2004 07:31:57 GMT

Does anyone know the cure for the BIOS warning - 3 beeps and "162-system options not set" error when starting an Armada 1592. I have just acquired this unit second hand and installed my own 6GB drive and keep getting this error on start up - the first three times with no BIOS clock set (set to 01-04-1980) now the BIOS clock is set in the BIOS and OS, and holds OK, but I still get the error message.

Any ideas out there?

Re: Armada 1592DMT 162-System options not set

Gary Cantwell — Mon, 19 Apr 2004 09:32:52 GMT

Hi Adrian,

You could also post this one over in the Armada Category:

http://forums1.itrc.hp.com/service/forums/categoryhome.do?categoryId=274

The folks there should have a solution for you,

Cheers,

Gary

Re: Armada 1592DMT 162-System options not set

Bruno Ganino — Mon, 19 Apr 2004 11:52:43 GMT

Adrian,
POST Beeping Error General Codes

Bad Motherboard - 1 long and 1 short beep
Disk drive related problem / Video card problem - 1 short beep then nothing happens
Bad video card - 1 long and 2 short beeps
Bad power supply - 1) continuous beeps, 2) non-stop short beeps
Bad memory - 3 short beeps

(3 beeps Bad Memory, check Memory Ram, remove sticks and put again)

Bruno

Re: Armada 1592DMT 162-System options not set

Ramesh Pakkath — Mon, 19 Apr 2004 12:01:34 GMT

Hi Arian,

2 short beeps and 162 - System Options Not Set error generally means Incorrect Configuration. Try resetting the BIOS to its defaults. Remove the CMOS battery and boot the system and check if you still get the beep codes. If this does not help, update the BIOS from the following link.

http://h18007.www1.hp.com/support/files/Armada/us/download/8076.html

Ramesh Pakkath.

Re: Armada 1592DMT 162-System options not set

Bruno Ganino — Mon, 19 Apr 2004 12:05:11 GMT

Adrian, you see this attachment:
It is COMPAQ POST ERRORS !

Re: Armada 1592DMT 162-System options not set

Adrian Redmond — Mon, 19 Apr 2004 12:40:56 GMT

Thanks everyone! I suspected the BIOS but found that it was updated to the latest, however I reflashed and the problem disappeared. That was after setting the date/time about four times and still getting the alarm - even though a F1 to recognise drive type every time did get me up into W2K, and the date and time were right!

I guess I'll put that one down to experience or simple curiousity. It's working anyway...

Thanks for the Error code list - that's really useful!

Best regards / Adrian