Date   : Thu, 06 Dec 1990 19:54:42 GMT
From   : crash!mwilson@nosc.mil (Marc Wilson)
Subject: INTTERM - Problems on my KP2-84

In article <1990Dec5.155950.22108@ico.isc.com> mikeod@ico.isc.com (Mike
O'Donnel) writes:

[saga on why INITTERM doesn't work on his Kaypro]

>1.  Why is it necessary to wait for the disk drive
>    to deselect?

     If you don't, your drives will stay selected forever.  The Kaypro
BIOS has a test loop in the character I/O routines.  If you haven't
talked to the drives by the time the counter gets to zero, it
deselects and turns off the motors.  When you run INTTERM, you are no
longer using the BIOS, so your drives stay selected.  This would be a
real problem on the K10, where your HD would stay selected forever.

>2.  Why does it relocate handlers into different areas
>    of memory and could this possibly be stomping on
>    something.  

     It moves itself above 8000h because it needs the ROM in order to
talk to the screen.  The ROM comes in at 0h-8000h.  If an interrupt
occurred while the program had the ROM enabled, the interrupt vector
would point to a random location in the ROM, not in the program.
Result:  BLOOOIE!

>3.  Does anyone have a memory layout and tech. info for
>    the KPII-84 that they would send me?

     Yes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~