Hello Ryan.

19 Oct 03 19:54, you wrote to All:

 RL> BTW can someone tell me why when I use the win32 version of Maximus 3.1,
 RL> doors don't work? I've noticed that it doesn't output the right COM port
 RL> to the dropfile .. but I've tried hardcoding the proper com port into the
 RL> doorsys.mec and doors still wouldn't work. That's why I'm using the DOS
 RL> maximus on windows.

It's because Win32 uses a dynamically assigned com port handle as opposed
to 16 bit DOS-based OS's, that use a static comm port handle that is linked
to the port number. That means that when a Win 32 app tries to pass a hot
comm port handle to a DOS app, the comm port handle that the Windows app
sends doesn't match what the DOS app expects.

There are only two ways around this; either use a virtual modem device
which mimics what the DOS apps expect, and run a DOS BBS package which will
then pass the port handle properly to a DOS door under this setup, or run
the Win32 BBS with a special fossil driver that is called everytime the DOS
based door is called, which will then translate the Win comm port handle
setting to what the DOS app expects.

Programs like COM/IP and Netmodem work in the first example. Programs like
SyncFos and NetFoss work in the second. An NT-based system is required for
the special fossil drivers to work.

--- GoldED/W32 3.0.1