WG> Also, I'm planning on hatching out the first serial 
 WG> comm module sometime in the next week. No promises, 
 WG> though.
 WG>  
 WG> Oh! You mentioned that your run BinkleyTerm XE. Do you 
 WG> know how it hands off the serial port to the 
 WG> application?

I'm just starting to get things together under Linux, including BinkleyTerm
XE.  I've been running BinkleyTerm 2.60 under OS/2.  In that version, there
are three methods for handing off to a BBS, in my case Maximus/2, version
3.01.  One is via a shell script error level exit.  This is NOT recommended
under OS/2 (or Win32), and probably not recommended in Linux.  If I
remember correctly, the one I use is the SpawnBBS method, where Binkley
starts up the Max process directly, passing commandline info, including
(under OS/2) the needed handle to the serial port.  [Under DOS, this passes
the fossil port number.]  I don't remember the third type at the moment.  

In Win32 (and maybe OS/2), you have to use the method that spawns the code
directly, because of how the (16 bit) DOS command shell initializes the
serial ports......

As I said, I'm not up on the Linux version, but I assume it works
similarly....  I'd have to look up in the documentation to see what the
order is for the items passed on the command line.  Stuff like the open
serial port handle, the port speed, the task number and number of minutes
to the next binkley event are passed as parameters.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01