Hey all,
So I'm having a bit of trouble getting Mystic to work with DosEmu under Debian. The door or launch batch files get called and execute, and the doors start, but I don't get any output on the Mystic side, almost like it's just not interacting with the fossil output.
Here's an example command line for reference:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "/bbsshare/doors/dos/lord/start.bat" %3 /DOS

Though I have tried other simpler to setup doors like BRE as well. I have a feeling I'm missing something simple or obvious, but keep missing it. Hopefully someone else can spot it and point me in the correct direction.
--
Underminer <bbs.undermine.ca>
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

Here's an example command line for reference:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "/bbsshare/doors/dos/lord/start.bat" %3 /DOS

Whoops, noticed my brainfart on that particular command and changed it back to:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "e:\lord\start.bat" %3 /DOS

But the issue of no output on the terminal side remains.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

Whoops, noticed my brainfart on that particular command and changed it back to:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "e:\lord\start.bat" %3 /DOS

And noticed another brainfart with that and now it works:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "e:\lord\start.bat %3" /DOS

Variable needs to be in the string passed to dosemu :P Apparently I just needed to write things out to see my errors. Appologies to all, along with thanks, and I'll put this here anyways in case it helps someone else with the same problem
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

And noticed another brainfart with that and now it works:

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "e:\lord\start.bat %3" /DOS

Variable needs to be in the string passed to dosemu :P Apparently I just needed to write things out to see my errors. Appologies to all, along with thanks, and I'll put this here anyways in case it helps someone else with the same problem

Scratch that. Something in the load process is causing a fossil driver issue and it's just picking up STDIO for SOME doors. Need to get fossil working right, but if I load anything direct from dosemu it is picking up the presence of the fossil driver. Fossil is being loaded in autoexec.bat, no change between fossil, x00, or BNU.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

On 09 May 2021, 09:42a, Underminer said the following...

Scratch that. Something in the load process is causing a fossil driver issue and it's just picking up STDIO for SOME doors. Need to get fossil working right, bu t if I load anything direct from dosemu it is picking
up the presence of the fos sil driver. Fossil is being loaded in autoexec.bat, no change between fossil, x0 0, or BNU.

I have Mystic running on Debian 10 here, and am using dosemu for the door games.

What I needed to do on some of them, is in the batch file, run bnu before executing the door game. I'm not sure why it's needed when it's already loading from the autoexec.bat, but it helped here with quite a few doors.

D:
cd doors
bnu
cd abrige
abridge /LOCKED=38400 /NODE%1 /Pd:\mystic\temp%1\


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/04/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 09 May 2021, Underminer said the following...

Whoops, noticed my brainfart on that particular command and changed it back to:
ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }" "e:\lord\start.bat" %3 /DOS

But the issue of no output on the terminal side remains.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

I suspect the argument passing and path issues. Is this SBBS or Mystic? I see it's Windows, but which version or is that just due to the DOS emulation? Mystic doesn't allow things outside it's path, generally meaning it has to be under /mystic. So if the drive is really e:\mystic to DOS that's OK, but
if it's c:\mystic and the door is e:\anything it's not likely to work. Mystic changes from root owner to whatever whatever owns the mystic directory and won't let things outside the mystic path do much if anything. The DD command (Linux door) is an exception to that, you can run games from /usr/local/games using DD. Generally the temps have to be under mystic and that causes doors
not to work outside of the mystic directory. No idea if SBBS does that, but
I wouldn't expect it. I think more people work on that and it's inherited
the older DOS paths so they aren't as secure as the way g00r00 does it.

--- Mystic BBS v1.12 A47 2021/04/08 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

Hello Underminer!

On 09 May 2021, Underminer said the following...

ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }"

Hmm... Shouldn't that be "stty" instead of "ssty"?

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/04/08 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

working right, bu t if I load anything direct from dosemu it is picking up the presence of the fos sil driver. Fossil is being loaded in autoexec.bat, no change between fossil, x0 0, or BNU.

I have Mystic running on Debian 10 here, and am using dosemu for the door games.

What I needed to do on some of them, is in the batch file, run bnu before executing the door game. I'm not sure why it's needed when it's already loading from the autoexec.bat, but it helped here with quite a few doors.

D:

Yup, did some experimenting yesterday after posting and that's exactly what did it for me too. Thing is I'm almost positive I tried that same thing but with both the freedos fossil and x00 and it made no difference, but worked with BNU. Really strange. Probably something to do with comm initialization order when calling an executable on start or something. I might go back and try that with x00 just to see.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

I suspect the argument passing and path issues. Is this SBBS or Mystic? I see
it's Windows, but which version or is that just due to the DOS emulation? Mystic doesn't allow things outside it's path, generally meaning it has to be under /mystic. So if the drive is really e:\mystic to DOS that's OK, but
if it's c:\mystic and the door is e:\anything it's not likely to work. Mystic changes from root owner to whatever whatever owns the mystic directory and won't let things outside the mystic path do much if anything. The DD command (Linux door) is an exception to that, you can run games from /usr/local/games
using DD. Generally the temps have to be under mystic and that causes doors not to work outside of the mystic directory. No idea if SBBS does that, but I wouldn't expect it. I think more people work on that and it's inherited the older DOS paths so they aren't as secure as the way g00r00 does it.

There's no black magic going on with Mystic, at least not in *nix. Whether you can access things outside of /mystic or not, or whether they can access /mystic is entirely down to your permissions and ownership. I have a few instances on a few different LXC containers to test different things out, and in all cases have a shared bind mount with tools. There may or may not be additional checks being run within the windows binaries, but I wouldn't know as I don't touch anything MS if I can help it.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)