Jim Raver wrote in a message to Victor Loberger:
VL>        If I want to run *any* DOS on-line games or other things, I mus
VL>run the DOS version of Maximus.  This is because Maximus/NT
VL>(really NT) can not pass an open comm port to a 16 bit
VL>application more than once (?).  I can use a NT mailer (i.e.
VL>Binkley/NT) and have it spawn the DOS version of Maximus and
VL>I'd still be ok.
VL>
JR> I've been living with this problem for a long time, at least with
JR> WIN95. You can not pass a "hot" comm port from a win32 app to a
JR> 16bit app. or vise versa.  What happens is passing from one to the
JR> other drops the DTR signal while one app closes the port and the
JR> other takes it over.  The way I've gotten around it is to run the
JR> modem with ignore DTR set (&D0 on a USR).  Then you can pass back
JR> and forth between them until your heart is content.  Hanging up the
JR> phone line does become a bit of a problem then.  I have set my
JR> modems to hang up when they receive the +++ string.  So my hang up
 Hmmn.... very interesting. :)
JR> string in Binkly WIN32, Maximus, and PowerBBS no longer toggles the
JR> DTR.  Instead the string says pause for one second, send +++, pause
JR> for one second, then send ATH0.
JR> The ATH0 is not actually necissary anymore since I told the modems
JR> to hang up on receiving the +++.
JR> It takes a LOT longer to terminate a call this way but lets me get
JR> away with running about anything I want.  Most doors that have a
JR> hangup function do not hangup because of this but that seems to be a
JR> minor problem that nobody really notices.
 Heck with the doors, most of us would probably just be happy
 to run 32-bit mailer and BBS.  At least I would. 
JR> I also run Winfossil which really does not seem to care who grabs
JR> the comm port and how they do it.  It seems to leave any app alone
JR> that does not initiate it's communication with the fossil.
 Will have to try this out.
 Thanks!
 Patrick
--- timEd 1.10
---------------