Hello Alan.

11 Jun 09 16:48, you wrote to Andrew Leary:

 AL>> You should be able to use them with no problems.  Tell the door to
 AL>> talk to COM1, as that's what the example dosemu setup provides.

 AI> Good, I have some old floppies around here yet that is full of
 AI> them so I'll have a go.

 AI> I have some kind of problem with dos doors on remote. Probably
 AI> something small.. I'll see if I can nail it.

I was also having lots of trouble getting dos doors going. In the end, 
installing the latest version of Dosemu and the following tips/hints helped a 
lot.

I'm sure William wont mind, as it's not like they are trade secrets!


Stephen

===cut me here===
Hi Stephen,



Sorry for the late reply. I've only just read your message.

SW> just been having a look around your system. Must say you've made
SW> the thing look good.. Also fast! (Your on Cable?.. stuck with adsl 1
SW> here)


Thanks a lot. Yeah, I've been making quite a few changes and fixing quite a
few bugs with the MBSE 0.95.5 release. I'll have to make a patch-set at some
point and I'll contact Michael to get them included in a future release.

Some areas could do with some better documentation also. I've been reading
through source to try and figure out how stuff works on the BBS because some
of the instructions are vague at best... doors especially.

SW> Is there any chance of getting a copy of the script/bat files etc that
SW> you've used to get dos doors going. Also on that you know works as
SW> well..


No problems.

I used the rundoor.sh script that was provided with the MBSE distribution.
I've made minimal changes. I created a directory called doors in
/opt/mbse/bin/doors and I create symlinks for all the doors I want to run.

For example, from the shell,

# cd /opt/mbse/bin/doors
# ln -s ../rundoor.sh tw2002  (without .bat)

Under /opt/mbse/var/dosemu/c/doors make sure you have a batch file matching
the symlink name. So,

# touch /opt/mbse/var/dosemu/c/doors/tw2002.bat


Edit this batch file with your favourite editor. I use joe. Make sure you
run it with DOS line endings support though. So,


# joe -crlf /opt/mbse/var/dosemu/c/doors/tw2002.bat

Provide the necessary commands in DOS required to start the Trade Wars door
in the batch file.


I have the following:

{at}ECHO OFF
C:
CD \DOORS\TW2002
TW2002 TWNODE=%1
CD \DOORS\NODE%1
DEL DOOR.SYS
DEL DOOR32.SYS


Jump into the DOSemu command line, go to your TW installation, make sure you
configure some nodes (I configure as many nodes as I allow MBSE socket
connections). Make them use serial comms on COM1, use a FOSSIL driver if you
want.


In the BBS menu editor, the command to start the door should be:

/opt/mbse/bin/doors/tw2002 /N


The /N passes the node number to the rundoor.sh script and that will be
placed as the first argument to your tw2002.bat batch file (%1).
Make sure you have Use COM port setting on, and door.sys active. Disable the
single use setting because TW is a multi-node door.


I should mention one other important setting.

In your dosemu.conf file, make sure the $_hogthreshold is set to 1 or 2
(something low). Some of the DOS doors hog the CPU due to the way they were
written and most assumed they were the only thing running on the machine (no
multi-tasking environments at the time).


SW> Been trying to get Tradwars2 going, and the virtual sysop from them
SW> mbse docs.

SW> I just end up with a blank screen {at}-(


Good luck with Trade Wars. If you manage to get one of the doors running,
configuring the second, third, fourth etc are easy.


Cheers,
William

===cut me here===



--- GoldED+/LNX 1.1.5