-=> Quoting James R. Cook to Phil Crown <=-

 

 PC> I know P.EXE (the freeware Zmodem package) makes changes (to the

 PC> read/write timeout, at least) when it is passed a com port handle.

 JRC> 

 JRC> If it's done in a door or whatever, does the calling proggie need to

 JRC> reset the port when the called program is finished?  Say I write a

 JRC> little shim that sits between my BBS and my Mailer.  It prompts the

 JRC> user to download a textfile or something.  I shell out to P.EXE and it

 JRC> fiddles with the comm port handle.  When it's done, do I need to reset

 JRC> the port again, or does it automagically reset itself to the way it

 JRC> was? 



I think you need to reset it, p.exe does not seem to reset the com port

to its previous state.



This is how I found what I believe is a bug in SIO's SU.EXE program.

Running "su  mode" will not report values higher than
255 for the

usWrite/usReadTimeout values, though they are defined as USHORT in the

DCBINFO structure, and I can set/query them as values higher than 255 in

my own app.



Phil Crown

pcrown{at}airmail.net

http://web2.airmail.net/pcrown/



--- Blue Wave/OS2 v2.30