Anthony Tibbs wrote in a message to Robby Dittmann:
RD> configuration.  Your biggest probelm will be in your
RD> versions.  If you are using WinFossil 1.12, you must have
RD> final release 4. The others won't work.  If you have a one
RD> line system, version 1.11 works well, and you can FREQ it
RD> from me as "111".  Also, you cannot use Max/NT with a mailer
RD> under Win95.  You must use the DOS version of Max. Once
RD> that's all starightened out, just make sure to select the
RD> proper com ports and lock the baud rates at the same speed. 
RD> You should be good to go.
AT> Woops.
AT> You can use Max/NT under Win95, by using a 32-bit mailer, IIRC.
AT> Bink/NT (or Bink/32)?
 Not as far as I've heard, and this is something a lot of people would
 want.
 You can use Max/NT alone, with no mailer and no DOS doors. 
 Or, You can run Bink/32, Winfossil, and Max DOS and all the DOS doors
 you want.
 But you can't run Bink/32 with Max/NT.
 Simple answer: It's an OS problem.  An open com port can not be returned
 to a 32-bit app once it's been given to a 16-bit app (command.com) without
 closing the port. 
 Handing off from Bink32 to Max/NT is a 32-16-32 conversion.  Won't work.
 It'll close the port before it hands off to Maximus. 
 Handing off from Bink32 to Max DOS with DOS doors is a 32-16-16-16 (ect)
 conversion.  Works fine.  Port stays open.
 So a lot of people (everyone I know) run Bink32 and use the DOS version
 of everything after that.
 Now, if you have figured out the solution to the port closing, please
 let everyone know!  :)
 Patrick
--- timEd 1.10
---------------