Subj : re: Batch File Door Game Advi
To   : Lon Seidman
From : Marc Lewis
Date : Mon Aug 31 2009 07:05 am

Hello Lon.

<On 27Aug2009 16:39 Lon Seidman (1:396/45) wrote a message to
Shawn Highfield regarding Batch File Door Game Advi >

 LS> Even with that configuration set I am still striking out..
 LS> Doors like Trade WArs 2002 are executing locally but not
 LS> passing data over telnet.

 SH> It might be the drop file.  If your using door.sys try
 SH> dorinfo or vice versa.  There is a bug in one of the mecca
 SH> scripts that can cause that.

If you're using DOOR.SYS these lines in the DOORSYS.MEC file are
the most critical:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
[delete]%k\Door.Sys
[open]%k\Door.Sys
[islocal write]COM0[ comment          Write the COM port    ]
[isremote iftask]1 [write]COM3    <<<
[isremote iftask]2 [write]COM1    <<<
[isremote iftask]3 [write]COM2    <<<
[isremote iftask]4 [write]COM4    <<<
[isremote iftask]5 [write]COM5    <<<
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

Make sure the COM ports match what's actually being called for
in your startbbs.bat or .cmd file.  I remember now that this
fouled me up a long while back until one of the folks in here
reminded me of these variables in the .MEC files.  The same
thing holds true for all the other drop file "scripts."

Don't forget to "mecca" the edited .MEC file!

Best regards,
Marc

--- timEd/2 1.10.y2k+
 * Origin: Sursum Corda! BBS-Meridian, MS-bbs.sursum-corda.com (1:396/45)

.