Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!ncsuvx!news
From: bank@lea.ncsu.edu (Dave The DM)
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Re: Hardware Problem?
Message-ID: <1990Oct11.051229.3635@ncsuvx.ncsu.edu>
Date: 11 Oct 90 05:12:29 GMT
References: <232800002@inmet>
Organization: Leazar Hall MicroVax II (CSCLEA), NCSU, Raleigh NC
Lines: 41

Beth,



    The "1024K" refers to the amount of memory that passed the power-on

checks.



    The "36 301" refers to a keyboard (301) failure and the "36" is

the scan code of the individual key that failed - I believe it is

shown in hex, so the scan code in decimal would be 54...the "6" (number

across the top) key.



     The "162" is either "Clock Not Set" or "Options Not Set"...I

don't have a PS/2 reference manual handy, so I can't say for sure.



     Solution: Check the keyboard for a stuck key. If nothing's

stuck and the problem persist, check the cable. If it STILL

doesn't work, take it in for service/replacement.



     The "162" error can usually be cured by using the Option

diskette to re-setup the system. 



                                  Dave the DM