Hi All,
I'm just curious if anyone else has noticed this. I've had door games running on CRBBS for quite awhile, with no problems. I've noticed, with the help of Andrew, that some of the games are not running right. They will show up fine
in the popup dosemu window on the BBS system, but not show remotely.
I do think I've finally found the issue. I'm not sure when this problem started, but when running a game that requires the socket handle to be passed via #0, it's not working.
Example setup for Gary's AF Slots game
Command | (DD) Exec external program
Data | dosemu -I"serial { com 1 virtual }" "d:\doors\afslots\start.bat
%0 %3" /DOS
Access |
Execute | Select
The contents of the start.bat file are:
d:
cd \doors\afslots
afslots.exe /H%1 /Cd:\doors\afslots\adoor%2.cfg
playered scores
copy scores.txt d:\mystic\text\afslots.txt
However, when I check the logs as far as what is happening when trying to run this game, this is what I'm seeing:
2019.04.21 22:05:30 Executing: dosemu -I"serial { com 1 virtual }" "d:\doors\afslots\start.bat 8 2"
2019.04.21 22:05:35 Execution complete: 0
Now, I'm going by memory here, which at my age isn't as good as it used to
be, but the socket number was always a 5 digit number, wasn't it? I don't see
8 as being a valid socket.
Has anyone else noticed any problems like this, or did I end up breaking something?
BTW, I am running CRBBS on 64bit Ubuntu 18.04LTS.
Thanks,
---
Black Panther(RCS)
a.k.a. Dan Richter
Sysop - Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again....
--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)