Hi Wall E. Weasel

What version of NetFoss are you using? There was previously an issue (fixed in 1.23R or sometime around there) which caused a false loss of carrier from time to time. Is BRE getting this situation every time
the door loads or just on occasion? The NetFoss bug was pretty intermittent.

Okay my netfoss version is 1.14R but for same reason it working now
but what to use it without fossil if I can.

I changed to D3 Exec /w DOSXTRN (Win32)
Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

but after the no to enter bre it didnt enter jast came back to menu

D3 is used to shell to 32 bit doors. It doesn't actually load DOSXTRN.
You'll need to use DX instead. Also, have you manually installed DOSXTRN.EXE to the Mystic directory and SBBSEXEC.DLL to
Windows\System32?

Yes I notice I put it on D3 instead of DX but done now and downloaded DOSXTRN.rar from mysticbbs\downloads and put Mystic directory and SBBSEXEC.DLL to

Windows\System32?

Don't forget to stop loading NetFoss when using this option. DOSXTRN provides its own FOSSIL driver.

okay is is my Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3 line

To stop using FOSSIL support in BRE you'll need to edit the game's RESOURCE.DAT file and set the FOSSIL option to NO. Depending on your setup you might have more than one of the resource files to edit.

okay, I have done that now

I had a go at but doesn'y work for me, nothing happens after I press the no of bre on the menu

so there must be same thing else I have todo, do I have to change mt data line ie

c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

Thank you for your help

Ian 2nd Choice Core


___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Hi Wall E. Weasel

Yes I notice I put it on D3 instead of DX but done now and downloaded DOSXTRN.rar from mysticbbs\downloads and put Mystic directory and SBBSEXEC.DLL to Windows\System32?

I downloaded this version and tried it. This version of DOSXTRN does
not have UART emulation. It does function as a FOSSIL driver, but
that's what you're attempting to get rid of.

Be patient for a day. A newer version may somehow appear on your BBS.

Cool, I wait for the newer version.

okay is is my Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3 line

Can you post your BRE.BAT file if it isn't too huge? I don't think
it's the problem but let's make sure.

bre
@echo off
c:
cd \bbs\mystic\mydoors\fsxnet\bre
srdoor
bre planetary
bre
c:
cd \bbs\mystic
mis poll 21:1/10
exit

I had a go at but doesn'y work for me, nothing happens after I press
the no of bre on the menu

What do you see in the BBS window for that node when it attempts to run the game?

The graphic was all wierd menu all over the place

Do you have a physical serial port at COM1 on the BBS machine? If so, BRE is using that if it runs with the Fossil option set to No. You should see the game running but with no data going to the remote user.

I didn't thing so, I using hyper-v guest so really cannot answer that one

If you don't have one I would expect the NTVDM to barf when BRE
attempts to un.

yes I got that NTVDM when I was using nefoss the first time.

Thank you
Ian 2ndchoicecore.nz


___ MultiMail/Win v0.52

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Cool, I wait for the newer version.

Check your inbound directory for a newer copy along with the latest NetFoss.

While reinstalling dosxtrn in my test machine I re-discovered something I didn't mention. If you are using a version of Windows later than XP you'll need to copy sbbsexec.dll to both the Mystic root directory AND the Windows System32 directory. Mystic won't launch DX doors unless it's in the Mystic directory but Windows needs it in the System32 directory.

bre
@echo off
c:
cd \bbs\mystic\mydoors\fsxnet\bre
srdoor
bre planetary
bre
c:
cd \bbs\mystic
mis poll 21:1/10
exit

There's an issue here but it's not likely the cause of your other problems. As it's set up now, BRE will use another player's data if someone runs the game from other than the first node. Let's get things set back up and running before tackling this one. It's an easy fix but tedious.

If you don't have one I would expect the NTVDM to barf when BRE
attempts to un.

yes I got that NTVDM when I was using nefoss the first time.

Was that with the FOSSIL option in BRE set to Yes? If so, there something more going on here.
--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hi, Wall E. Weasel

Cool, I wait for the newer version.

Check your inbound directory for a newer copy along with the latest NetFoss.

Found them thank you.

While reinstalling dosxtrn in my test machine I re-discovered something I didn't mention. If you are using a version of Windows later than XP you'llneed to copy sbbsexec.dll to both the Mystic root directory AND
the WindowsSystem32 directory. Mystic won't launch DX doors unless it's in the Mysticdirectory but Windows needs it in the System32 directory.

okay I did all that and YES it is working fine now useing dx and
no fossel

bre
@echo off
c:
cd \bbs\mystic\mydoors\fsxnet\bre
srdoor
bre planetary
bre
c:
cd \bbs\mystic
mis poll 21:1/10
exit

There's an issue here but it's not likely the cause of your other problems. Asit's set up now, BRE will use another player's data if someone runs the gamefrom other than the first node. Let's get things
set back up and runningbefore tackling this one. It's an easy fix but tedious.

Now you fix DX, what do I have to do to fix my bat file

If you don't have one I would expect the NTVDM to barf when BRE attempts to un.

yes I got that NTVDM when I was using nefoss the first time.

Was that with the FOSSIL option in BRE set to Yes? If so, there
something moregoing on here.

okay it work now, so I am sure we don't have to do any thing about
NTVDM, right.


just another question about dx in linuk rasbperry os in mystic.
or is it only Window.

Thank you

Ian Segers 2nd Choice Core BBS

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Hi Wall E. Weasel

I think we have a language barrier here. Can you ask this again

sorry about the language barrier

I have installed mystic on a new raspberry pi (raspberry s linux) and
trying to get ssh to work in mystic, I have posted in this echo before

ie: sudo setcap 'cap_net_bind_service=+ep' mis it did work once but cannot
do it in the new setup

ie mis server

07:23:23 MANAGER Starting event system ░
│ 07:23:23 MANAGER Starting 2 server(s)
░
│ 07:23:23 TELNET Listening on IPV4 port 23 using interface "127.0.0.1"
░
**│ 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
░
│ 07:23:23 TELNET Listening on IPV6 port 23 using interface "::"
░
**│ 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)
░
│ 07:23:24 EVENT Starting 0 event(s)

mystic config

ssh server config
active yes
id ssh
adapter type ipv4=ipv6
ipv adapter 0.0.0.0
ipv adapter ::

my bbs is in /home/pi/mystic command ./mis -server

just like to now if you can help to get ssh to work again

Thank you
Ian 2nd Choice Core Nz
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Hi Wall E. Weasel

would I just change port to say 24 or would I have to insert it in
another line with out the # save a reboot.

You would either remove the # and change it to say "Port 24" or insert another line with only "Port 24". The # indicates the rest of the line is a comment so it's ignored by SSHD...

Okay, I have changed sshd port to 2222 rebooted and using port 22
for my mystic ssh server cool.

I tend to always insert a new line with my configuration and leave the original commented one in. It helps me remember the default values
when I'm messing with things.

I all so did this

It's just as easy to forward to port 2222 as it is 22.

True.

do you mean What I have done in mystic config server port 22 to 24
and set the router up for port

Yes, just have your router forward to whichever port you have set up instead of 22.

That's cool all fixed now with your help thank you

just a question in bre per mystic data command line
mine is c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

is this setting okay to use for the node1 node2 node3 etc

Thank you

Ian 2nd Choice Core NZ
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Hi Wall E. Weasel

That's cool all fixed now with your help thank you

Great! Glad it's working.

Yes it is great.

just a question in bre per mystic data command line
mine is c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

is this setting okay to use for the node1 node2 node3 etc

Yes, %3 passes the node # which is what you want to use. %N would also be fine.

Cool, and thank you very much for the help with bre and ssh settings
and have a nice day

Ian 2nd Choice Core Nz
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)