-=> Quoting Charles Gaefke to Phil Crown <=-

 PC> #define INCL_DOSDEVIOCTL

 CG> I'm not including that one.. and it works fine (I got it working
 CG> after I  posted my question.  It usually happens that way.)  But thanks
 CG> for the help.   When I get a free moment or three, I'll see which ones
 CG> I can #define and still have it work.

Good, but don't forget this one, you may need it.
 
 PC>  CG> And if a port is "locked", do you have to
"unlock" it before you
 PC>  CG> can  change the rate, then do you have to "relock" it?
 PC> 
 PC> I'm lost here, I use SIO which locks the port.

 CG> So do I.  My question was from a programs standpoint.  SIO locks
 CG> the port, yes.  When you tell it to change the port rate, and it's
 CG> already locked, does  SIO unlock, then change it, then lock it, or does
 CG> it just change it, and it  stays locked?  So if it was locked, by SIO,
 CG> and I changed it to a new value,  would it still be locked?

I seem to remember reading something about SIO and locking the port.  It
may have been in the SIO docs.  I may be wrong, but I think once SIO
locks the port it can't be changed, but an application can set its own bit
rate, probably by calling DosDevIOCtl().  This is what I do and its
working.
 
 PC> Get pmtermsr.lzh from Peter F.  I need a copy too, maybe he'll upload it
 PC> to an ftp site?

 CG> Who is he? :)

The moderator of this Echo.  I thought he'd jump in when he sees what
we're talking about and about his code.  May have to write to him directly.

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

--- Blue Wave/OS2 v2.30