On Jun 17, 1997, Chris Holten wrote:
 JS> That's the truth also.  I ran DV (on a 486) for a
 JS> couple of years and anything above 38400 was a useless
 JS> endeavor, to say nothing of the problems I had with a..
 CH> Well, to be clear, it shouldn't of mattered that the BBS was
 CH> being run in DV -if- snoop wasn't turned on as the local
 CH> screen wouldn't be written to. If one was using DV when..
I can't disagree with any of that, Chris.  And thanks for the response.
 JS> Now for a question.  I'm interested in running the
 JS> above under Win95 but I've been told that it can't be..
 CH> You have been told right. 95's command processor is 16 bit,
 CH> so when control is passed from one program to another, the
 CH> 16 bit command processor is loaded. This causes 32 bit comm
 CH> software to drop DTR. Brian Woodruff has written WINFOSSIL
 CH> for windows 95. If an only if the 32 bit comm software can
 CH> be FOSSIL driven and has a special hook to WINFOSSIL, is it
 CH> possible to pass off to another app without dropping DTR.
 CH> Binkley 32 v 2.60 is the only 32 bit fidonet/bbs software
 CH> that supports Winfossil. Maximus 3.01n doesn't and probably
 CH> never will. I run Bink32 and MaxNT in Windows NT, not
 CH> Windows 95.
Hmmm... I don't think I phrased the question in a clear enough manner.  What 
I'm looking to do is eliminate Win95's command.com from the equation and 
instead use a 3rd party, 32-bit command processor (Rex Conn's TCMD32).  Under 
this setup, do you think Bink32/MaxNT would fly or... would it still just 
drop DTR?
(If anyone else has ever tried such a thing, I'd appreciate hearing about 
.)
 -Jack
  ogre@nashville.com
--- Squish/386 v1.11
---------------