-=> Quoting Darin McBride to Peter Schuller <=-

 DM> I have a simple program that writes to the serial port.  In C++ it
 DM> goes something like this: 
 DM> #include a few headers as appropriate (i.e., I'm too lazy)

 DM> int main(int argc, char** argv)
 DM> {
 DM> if (argc < 2)
 DM> return -1;
 DM> ULONG ulComHandle = strtol(argv[1], NULL, 0);
 DM> ofstream ofComPort(ulComHandle);
 DM> ofComPort << "See this through the com port" << endl;
 DM> return 0;
 DM> }

Interesting program, but if you want to adjust any of the com port
parameters (and there alot of them) you need to pass a file handle to
DosDevIOCtl().

 DM> In fact, it runs between Blinky and Maximus to tell the user what
 DM> speed *I* think s/he's connected at, as well as my BBS motto: 
 DM> I'm going crazy, and I'm taking you with me.

Probably because Bink has already set everything.  SIO's SU is great for
inspecting the com port, but I think there is a bug that it doesn't
report anything higher than 255 for the Read/Write Timeout values.
These are defined as USHORT in the DCBINFO structure (bsedev.h), and I
have no problem setting/querying them at values higher than 255.

I reported this to Ray Gwinn and he said he'd look at it.

Phil Crown
pcrown{at}airmail.net
http://web2.airmail.net/pcrown/

--- Blue Wave/OS2 v2.30