ES>> I just switched my Max 3.01 bbs over to run under OS/2 Warp 4. I
 ES>> got the BBS and message areas up and working fine but I can't get
 ES>> the DOS doors to work.

I never had Warp 4 so don't know if anything is different than Warp 3.0,
which I did run for quite a while.  So my help may not apply.  

 ES> DEVICE=C:\SIO\SIO.SYS
 ES> DEVICE=C:\SIO\VSIO.SYS
 ES> DEVICE=C:\SIO\VX00.SYS

When you load SIO.SYS you need to define your com ports, plus use the
little documented "-" parameter to allow OS/2 apps to pass off to
a DOS application.

I'm running from memory here so this may or may not be correct.  It goes
something like:
DEVICE=C:\SIO\SIO.SYS (COM1,38400,3F8,IRQ4,-)

The important paremter is the last one, the ",-".  It allows SIO
to turn off protection for that port, which allows your DOS doors to access
the port.

 ES> It looks like Max isn't passing the right comm handle 
 ES> info to door.sys though. My modem is on com2 and it 
 ES> writes it's connected to com3 which is unavailable and 
 ES> causes errors???

OS/2 uses COM handles, which are not the same as the COM ports.  The way I
got around this was I defined my nodes to match my com ports.  That is,
Node 1 used COM1, Node 2 used COM 2, etc.  This confused my callers when I
went back to only one phone line but they were still logging onto Node
3..... :) 
 Then you alter your DOORSYS.MEC file and where it writes the com ports you 
substitute the token for writing the node number.  Since the nodes match
the ports, you'll be in bussiness.
 
Here is what I used at the top of my DOORSYS.MEC:

[delete]c:\max\node%k\Door.Sys
[open]c:\max\node%k\Door.Sys
[islocal][write]COM0:
[isremote][write]COM%k:[comment    COM port]

Make these changes and you'll either be running your DOS doors or a lot
closer to running them!

--- Maximus 3.01