I've noticed a few weird things with these doors... First, they
don't work with my fossil driver unless I use the commandline
"NOFOSSIL" instead of "FOSSIL". Also, if I run door.bat tb%1.cfg
NOFOSSIL for tribingo as an example, it always loads tb1.cfg and the
user name is always interpreted as the node 1 user. Does anyone have
any resolution for the latter? It happens in all of his games...
I've noticed a few weird things with these doors... First, they don't work with my fossil driver unless I use the commandline "NOFOSSIL"
instead of "FOSSIL". Also, if I run door.bat tb%1.cfg NOFOSSIL
for tribingo as an example, it always loads tb1.cfg and the user
name is always interpreted as the node 1 user. Does anyone have any resolution for the latter? It happens in all of his games...
I've noticed a few weird things with these doors... First, they don't work with my fossil driver unless I use the commandline "NOFOSSIL" instead of "FOSSIL".
Also, if I run door.bat tb%1.cfg NOFOSSIL for tribingo as
an example, it always loads tb1.cfg and the user name is always interpreted as the node 1 user.
Re: Michael Jordan Doors...
By: Martin Kazmaier to All on Tue Jun 24 2025 03:00 pm
I've noticed a few weird things with these doors... First, theydon't
work with my fossil driver unless I use the commandline "NOFOSSIL"instead
of "FOSSIL".
Just a guess, but did you mistype FOSSIL when you were trying it the first time? It just seeks "FOSSIL" on the command line instead of looking for any exact match. So "TRIBINGO.EXE FOSSIL" enables FOSSIL as does "TRIBINGO.EXE pleasedonotusetheFOSSILorweallaregonnadierighthereandnow".
The docs don't seem to be fully updated throughout. So the bits where it states to use "FOSSILOFF" to disable automatic FOSSIL detection actually will enable its use. But the current behavior is shown in the command line parameters section.
Also, if I run door.bat tb%1.cfg NOFOSSIL for tribingo as an
example, it always loads tb1.cfg and the user name is always interpreted as the node 1 user.
I haven't checked the docs for all of the games, but in Tri-Bingo at least:
-- SNIP --
The setup of Tri-Bingo changes the way my previous doors are setup. I now support and require the use of Environment Variables to supply the game with the Com Port and Node Directory information. The game will read any environment variable that you supply so names are not critical.
The game now only reads the TRIBINGO.CFG file and will not accept any other name for the configuration file. So this is the file that will contain the environment variables.
Sysop: | Nitro |
---|---|
Location: | Portland, OR |
Users: | 6 |
Nodes: | 10 (0 / 10) |
Uptime: | 142:24:13 |
Calls: | 162 |
Files: | 755 |
Messages: | 91,021 |