Subj : Re: Mystic and DosEmu, am I missing something obvious?
To   : Underminer
From : bcw142
Date : Sun May 09 2021 06:55 pm

On 09 May 2021, Underminer said the following...
 
 Un> Whoops, noticed my brainfart on that particular command and changed it
 Un> back to:
 Un> ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }"
 Un> "e:\lord\start.bat" %3 /DOS
 Un> 
 Un> But the issue of no output on the terminal side remains.
 Un> --- SBBSecho 3.14-Linux
 Un>  * 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)

.