-=> Quoting Jonathan de Boyne Pollard to James R. Cook <=-



 > Okie.  I assume that after I fiddle with the settings, I should probably

 > set them back the way I got them (when my proggie exits)?



 JdBP> Yes. The settings apply to the COM device itself, irrespective of

 JdBP> the open file handle that is used to change them.  So if you change

 JdBP> them in a child process, they will be changed for the parent as

 JdBP> well.



 That's what I figured.  Hmmm.



 > Also, should

 > I worry with setting up a thread to handle the I/O or just let OS/2 buffe

 > it.  I've been going round and round with that and I can't see much

 > benefit in buffering it myself.



 JdBP> On the other hand, if I were writing a terminal emulator, I'd use a

 JdBP> separate thread and an indefinite wait-for-something timeout for

 JdBP> reading from the COM device, in order to make the thing as

 JdBP> efficient as possible.



 Okay.  Perhaps some background on what I'm doing would help.  It's a mini

 sort of BBS.  It sits between my mailer and my BBS and routes calls to

 the BBS, a telnet proggie and a download area (subscription info).  Not

 a really huge thing.  (Not yet anyway.)  I can't get a decent enough handle

 on the comm end of things to set it all straight in my brain.  See, I've

 added some complexity that I want the output stream massaged so that ASCII

 callers don't get all the ANSI crap and that variables like {at}TIME{at} get

 replaced properly.  :(  This is getting beyond my grasp I think.



 ={) James (}=



--- Blue Wave/DOS v2.30