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

    Then that makes it easy, doesn't it? :)

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

    Okay.. sounds good so far. :)

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

    I'm not familiar with C++.  Only C.  So I'm afraid a "wrapper
function" 
(whatever that may be) will be of no value to me. :)

DM> However, hope is not lost: if you have SIO, there are some excellent docs o
DM> the DosDevIoCtl function there.  Combined with OS/2's documentation for the
DM> API, you should be set to write your own wrapper.  One o' these days I'm go

    I'll have to look into that.  Hopefully there is C documentation in there,
and not just C++.

    Thank you for the reply.  IT is appreciated.


C. Gaefke
cdgaefke{at}sgi.net
[CDRMAIL Author]

--- RG05-11/CDRMAIL 103á