Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!eng.ufl.edu!wasp.eng.ufl.edu!spike
From: spike@wasp.eng.ufl.edu (Spike)
Newsgroups: comp.sys.zenith
Subject: Re: 386/20 and 386/33E lockup
Message-ID: <1991May8.151125.5129@eng.ufl.edu>
Date: 8 May 91 15:11:25 GMT
References: <7C26A0AE6F1F40645F@Meena.CC.URegina.CA>
Sender: news@eng.ufl.edu
Reply-To: spike@wasp.eng.ufl.edu (Spike)
Distribution: inet
Organization: U of Florida Engineering Comuputing Services
Lines: 21

In article <7C26A0AE6F1F40645F@Meena.CC.URegina.CA> MEACHT@meena.cc.uregina.ca writes:
> According to a recent Zenith bulletin, this problem could be because of
>the keyboard. Apparently, the system will go through the boot process then
>waits for the password. They say that this problem occurs with keyboard
>part number 163-0073-00. It should be replaced with part number 163-0073-01.
>It should be covered under warranty.
>
> I have not yet seen this problem, so let me know if it works.
>
>
   Terry, the keyboard didn't make a difference. It is a I/O Problem
   That I have confirmed on several occasions. As far as I know there
   is no documantation from Zenith on the problem, I've looked though
   all of my FSB's and haven't seen anything on it.
   Somebody suggested that "no prompt" was selected in the setup, it isn't 
   and the problem is confirmed intermittent.
   

   Keep in touch  

   Ken Gage Caretaker of Zenith Heaven, University of Florida.