CG>     First off, I've heard that native OS/2 software 
 CG> does not need a fossil 
 CG> driver.. is this true?  Either way, where can I find 
 CG> info on how to A) make my
 CG> own routines and/or B) use fossil routines?  Thanks!

*Real* operating systems do ALL I/O as if it were File I/O.  ;-)

So, there is no inportb/outportb type of functions, it is purely a file
operation.  Obviously there are a few things you can't do with files...
like set a baud rate, send a break, change to RTS/CTS flow control, etc. 
Thus we introduce a "kludge" - a generic "interrupt"
routine, DosDevIoCtl.

I would recommend getting a few wrapper functions - possibly a wrapper
class if you use C++ - just to make the code more readable.  A commercial
example of this is the Greenleaf Comm and Greenleaf Comm++ for C and C++,
respectively.  A freeware C example is something I got from Daniel Lynes
via the internet, oh, over a year ago I believe now.  ;-)  If you want the
communication routines, which he claimed to be in the PD (since he didn't
write them either), I can send them to your email address, or, possibly,
you could get them from Daniel who may have more "up to date"
files.  ;-)

Of course, if Daniel reveals to me that they aren't PD quite yet, and I had
just talked him into it at the time, then I'll have to rescind that
offer...  However, hope is not lost: if you have SIO, there are some
excellent docs on the DosDevIoCtl function there.  Combined with OS/2's
documentation for the API, you should be set to write your own wrapper. 
One o' these days I'm going to take the source and rewrite it into a
class... ;-)  BTW, I just found the text file... ACL (Asynchronous
Communications Library) is developed by someone named Merrick
Schincariol...


--- Maximus/2 3.01