---------------------------
Bugs, notes, and specifics:
---------------------------

Disk DMA
--------
If you find the system really grinds to a halt just after a readout
and write to disk, so much so that the mouse is only barely
responsive, you probably do not have disk DMA turned on.  As root
execute "hdparm -d1 /dev/hda".

Petty annoyances
----------------
If otcom won't recognize "backspace" as backspace but reports ^H, you
you need a "stty erase ^H".  Otherwise use a literal ^H for backspace.

Resetting
---------
If otcom is completely unresponsive, or is acting weird, this is the
sequence of things to check.  Generally speaking you should not have
to go beyond (4), and even that is very rare.  If you do have to go
beyond (4) be sure to let me know along with as much diagnostic
information as possible.

  1. Is otcom hanging because it's trying to communicate with the TCS?
     These communications can block for a long time if the TCS is not
     talking.  Try to get the TCS going again.

  2. Try a "tdl" to see whether you can talk through the interface to
     the controller.  It may clear things.

  3. Try a "pof" / "pon" cycle.
     Try a "pof" / "df" / "pon" cycle.

  4. Try killing otcom and restarting it.

  5. If you see a message like 

       "read failed: Resource temporarily unavailable"

     it means that the driver is hung up.  You may be able to diagnose
     things with a unix "dmesg".  You can remove and reload the driver
     (as root) with 

        rmmod lotuspci
        cd /usr/local/inst/bin
        insmod lotuspci.o

  6. If necessary you may have to cycle the power on the controller at
     the telescope.  This is the power switch on the power supply
     box.  You then need to restart otcom, redownload, etc.