Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!gatech!ncar!zaphod.mps.ohio-state.edu!usc!ucselx!crash!mwilson
From: mwilson@crash.cts.com (Marc Wilson)
Newsgroups: comp.os.cpm
Subject: Re: Strange Kaypro problems
Summary: of course it's normal
Message-ID: <5783@crash.cts.com>
Date: 21 Nov 90 19:29:02 GMT
References: <1990Nov20.201720.5035@techbook.com> <1990Nov20.221811.7383@techbook.com>
Distribution: usa
Organization: San Diego Mesa College, San Diego, CA.
Lines: 27

In article <1990Nov20.221811.7383@techbook.com> fzsitvay@techbook.com (Frank Zsitvay) writes:
>
>   something else i should have mentioned...  is it normal for the
>drive access led to stay lit even after the drive has been accessed??
>right now, the machine has been sitting after booting for a good
>half hour, and the led for drive a is still lit.   of course, the
>led goes out when i turn the machine off.   if i access drive b, it
>will do the same for drive b.

     That's the way the D BIOS works.  The last drive selected STAYS
selected until you select another.  It's not dangerous, it's just the
way the ROM BIOS deals with the drives.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Marc Wilson
     ARPA: ...!crash!mwilson@nosc.mil
           ...!crash!pnet01!pro-sol!mwilson@nosc.mil
     UUCP: [ cbosgd | hp-sdd!hplabs | sdcsvax | nosc ]!crash!mwilson
     INET: mwilson@crash.CTS.COM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Marc Wilson
     ARPA: ...!crash!mwilson@nosc.mil
           ...!crash!pnet01!pro-sol!mwilson@nosc.mil
     UUCP: [ cbosgd | hp-sdd!hplabs | sdcsvax | nosc ]!crash!mwilson
     INET: mwilson@crash.CTS.COM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~