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
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, 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.
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)
ssty cols 80 rows 25 && dosemu -I"serial { com 1 virtual }"
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:
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,054 |
Nodes: | 17 (0 / 17) |
Uptime: | 13:00:25 |
Calls: | 501,019 |
Calls today: | 6 |
Files: | 109,384 |
D/L today: |
1,563 files (102M bytes) |
Messages: | 304,808 |