From: ohland@charter.net   
      
   You keep getting codes that point to a board level problem. I have tried   
   to stay happy-dopey. It's getting harder to be naive. It seems that no   
   IML drive has been identified.   
      
   It would be great if you could run diagnostics...   
      
   0003 01XX   
        1. Keyboard Cable   
        2. System Board   
      
   0001 63XX Date and time error   
        1. Set Date and Time   
      
   00370200   
   0037 XXXX   
   Usually caused by SCSI controller on system board   
        1. System Board   
        2. Hard`Disk   
        3. Hard Disk Cable   
      
   00860200   
   0086 0100 / 0086 02XX   
        1. Pointing Device (Mouse)   
        2. System Board   
      
   00017300   
   0001 73XX Possibly a weak battery   
        1. Set Configuration / Features   
      
   Two beeps   
   * *	A problem exists, check config. Run diags, if no error code displayed   
      
   00018100   
   0001 81XX   
   The computer requires a network adapter for remote IPL or a hard disk   
   drive ID of LUN 0 for IML, neither of these were detected   
        1. Run Automatic Configuration   
        2. Network Adapter   
        3. Hard Disk Drive   
        4. System Board   
      
   Pertti Helander wrote:   
   > 00030100 (CP80 and HDD led turns on ) .   
   > 00016300   
   > 00370200 0000   
   > 00860200  ( HDD led turns off and fdd runs once).   
   > 00017300   
   > Two beebs and fdd stars to read refdisk then 00018100   
   > and FDD stops with light on and display went blank.   
   > No I999xxxx errrors I got.   
   > Is it possible that J14 is in wrong position and stops  refdisk to load?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)