Some will actually load but not run through the telnet server (visible only on
the host machine). I'm certain this has something to do with batch files and
error levels that I long forgot how to configure :).

Make sure you configure the doors to work in Fossil mode. I found
that is the trick to getting most doors to run. Also you didn't mention
if your running Maximus/dos or /NT and what version of windows.

Shawn
--- Platinum Xpress/Win/Wildcat5! v3.0pr3
* Origin: Omicron Theta | Grand Island's Finest! | robertwolfe.or (1:261/20)

Some will actually load but not run through the
telnet server (visible only on
the host machine). I'm certain this has something
to do with batch files and
error levels that I long forgot how to configure :).

Make sure you configure the doors to work in Fossil mode. I found
that is the trick to getting most doors to run. Also you didn't mention if your running Maximus/dos or /NT and what version of windows.

Shawn
--- Platinum Xpress/Win/Wildcat5! v3.0pr3
* Origin: Omicron Theta | Grand Island's Finest! |
R.or (1:261/20)
SEEN-BY: 31999/98 99
PATH: 261/20 38 396/45

--- Maximus/2 3.01
* Origin: Sursum Corda! BBS-Meridian, MS-bbs.sursum-corda.com (1:396/45)

Make sure you configure the doors to work in Fossil mode. I found
that is the trick to getting most doors to run. Also you didn't mention if your running Maximus/dos or /NT and what version of windows.

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

I'm running Maximus for DOS 3.01 under Windows XP.

-+- QuikEdit 2.41R+

--- Maximus/2 3.01
* Origin: Sursum Corda! BBS-Meridian, MS-bbs.sursum-corda.com (1:396/45)

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

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

I'm running Maximus for DOS 3.01 under Windows XP.

That should be fine. I assume your using netfossil or something like
that?

Shawn
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta | Grand Island, NY | bbs.robertwolfe.org (1:261/20)

Hello, SHAWN.

Replying to a message of SHAWN HIGHFIELD to LON SEIDMAN:

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

It's in DOOR.SYS (DOORSYS.MEC); I'd use the DORINFOx.DEF one.

Later,
Sean

// sean@nsbbs.info | http://nsbbs.info | ICQ: 19965647

--- FleetStreet 1.27.1
* Origin: Nocturnal State BBS - Johnson City, TN - bbs.nsbbs.info (1:18/200)

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

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

I'm running Maximus for DOS 3.01 under Windows XP.

That should be fine. I assume your using netfossil or something like that?

Shawn
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta | Grand Island, NY |
bbs.robertwolfe.org (1:261/20)
SEEN-BY: 31999/98 99
PATH: 261/20 38 396/45

--- Maximus/2 3.01
* Origin: Sursum Corda! BBS-Meridian, MS-bbs.sursum-corda.com (1:396/45)

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

Have you checked you com port config/drop file path conf in the TW setup program to be sure those are set correctly?

--- WtrGate/2 v0.93 Unreg
* Origin: Fallsview BBS * Grand Island, NY * OS/2 Baby! (1:261/20.2)

Hello Lon.

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

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

It might be the drop file. If your using door.sys try
dorinfo or vice versa. There is a bug in one of the mecca
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)