TIP: Click on subject to list as thread! ANSI
echo: cis.tandy.coco
to: Pete Lyall 76703,4230 (X)
from: Scott t. Griepentrog 72427,335
date: 1990-06-10 14:54:18
subject: #4221-Carrier Detection

#: 4225 S10/Tandy CoCo
    10-Jun-90  14:54:18
Sb: #4221-Carrier Detection
Fm: Scott t. Griepentrog 72427,335
To: Pete Lyall 76703,4230 (X)

There is a way to have the driver kill the program if CD is lost thoughset the
TYP (parity) byte to hex 10 to flag ACIAPAK's auto-kill routine. Be wary though
that the program gets no warning, just killed - and any other processes with
the port open will get killed too.

Otherwise the only safe way to take a look at the status of CD is as Pete says,
do a peek.  If you link to the module (may a little much for basic09) and get
the unit address, you can then operate correctly even if multiple ports are
being used.  Oh, and you should check to insure that the descriptor is using
ACIAPAK as a driver too in case somebody runs the program on a nonACIAPAK
device...

StG

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.