#: 12206 S12/OS9/68000 (OSK)
    12-Sep-91  04:18:21
Sb: #12205-OSK standards
Fm: Ed Gresick 76576,3312
To: Ed Gresick 76576,3312 (X)


 (Continued from part 1)

 Briefly, it works like this.  (I run tsmon on my modem port (m0).)  First I
 set the modem for auto-answer with the command 'echo "ATS0=1"'.  Then I
 use Brett Wyncoop's 'enable' to set up the port.  'Enable' activates tsmon,
 gets the pid for tsmon, sets up a lock file for port m0 and places
 tsmon's pid in the lock file.  This is the normal state for my system.
 If I want to use the modem for an outcalling call (or disable the modem
 for other reasons), I use Brett's 'disable'.  'Disable' reads the lock
 file for that port, gets the pid, kills the process and removes the lock
 file.  I follow this with the command 'echo "ATS0=0"' to turn off
 auto-answer.  Actually, I use two script files, 'start_m0' and 'end_m0',
 to activate and deactivate the port.  'Start_m0' is also in my 'startup'
 file.  I run UUCP and Kermit for both incoming and outgoing calls and Sterm.
 Most outgoing UUCP and Kermit calls are handled by 'cron' so you can see the
 process operates unattended.  I've had the system running this way for
 almost two years now.  If I ever get a version of UUCP that will work under
 OSK, I'll install it on my SYSTEM IV.  But I doubt I'll put it on line.  I
 use the CoCo only for unattended communications (file transfers, mail, etc.)
 so I'm not worried about security.

 How does Suno use two logical devices?  Seems to me that under OS9 and
 task switching, the two devices would get confused - the wrong one getting
 information.  I'm assuming you have tsmon running to one and doing an
 outgoing call from the other.

 Ed Gresick - DELMAR CO