I have been running 3.19a without any issues. I upgraded to 3.19b and moved the new copy of sbbsexec.dll over to the System32 directory. I was doing testing to make sure my system was still running correctly and I noticed several of the door games no longer would run. I wondered if it might be the sbbsexec.dll from 3.19b. I grabbed the file from a back up of the BBS and now the games run again. The date on the file I used is: 12/6/2011.
The date on the file that did not work is: 1/2/2022.
When you say "several of the doors games no longer would run" - was it all t 16-bit DOS door games? Just some of the 16-bit DOS door games? Only those th are configured one way or another (e.g. FOSSIL vs UART for I/O)? If you are fact running sbbs v3.19b (and not v3.19a) and the sbbsexec.dll dated 1/2/202 isn't working, then those details will be important to help get to the botto of it.
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 06:20 pm
When you say "several of the doors games no longer would run" - was it all t 16-bit DOS door games? Just some of the 16-bit DOS door games? Only those th are configured one way or another (e.g. FOSSIL vs UART for I/O)? If you are fact running sbbs v3.19b (and not v3.19a) and the sbbsexec.dll dated 1/2/202 isn't working, then those details will be important to help get to the botto of it.
I will do some more research. I'll put the file back and try to determine what is going on. I won't be able get to it until Sunday.
Rob, I do appreciate all the work you put into this thing.
Re: 3.19b Door Game Issues
By: Tim Whitson to Digital Man on Fri Feb 04 2022 08:59 pm
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 06:20 pm
When you say "several of the doors games no longer would run" - was it all t 16-bit DOS door games? Just some of the 16-bit DOS door games? Only those th are configured one way or another (e.g. FOSSIL vs UART for I/O)? If you are fact running sbbs v3.19b (and not v3.19a) and the sbbsexec.dll dated 1/2/202 isn't working, then those details will be important to help get to the botto of it.
I will do some more research. I'll put the file back and try to determine what is going on. I won't be able get to it until Sunday.
Rob, I do appreciate all the work you put into this thing.
I appreciate you giving the additional details.
I can see fromr message's PID (Program ID) that you are indeed running SBBS v3.19b, so I guess I already know that answer:
Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 09:11 pm
Re: 3.19b Door Game Issues
By: Tim Whitson to Digital Man on Fri Feb 04 2022 08:59 pm
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 06:20 pm
When you say "several of the doors games no longer would run" - was all t 16-bit DOS door games? Just some of the 16-bit DOS door games Only those th are configured one way or another (e.g. FOSSIL vs UAR for I/O)? If you are fact running sbbs v3.19b (and not v3.19a) and sbbsexec.dll dated 1/2/202 isn't working, then those details will b important to help get to the botto of it.
I will do some more research. I'll put the file back and try to determine what is going on. I won't be able get to it until Sunday.
Rob, I do appreciate all the work you put into this thing.
I appreciate you giving the additional details.
I can see fromr message's PID (Program ID) that you are indeed running SB v3.19b, so I guess I already know that answer:
Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
Another thing to check is the date/time of your exec/dosxtrn.exe file. That could play a role as well.
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Sat Feb 05 2022 01:01 pm
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 09:11 pm
Re: 3.19b Door Game Issues
By: Tim Whitson to Digital Man on Fri Feb 04 2022 08:59 pm
Re: 3.19b Door Game Issues
By: Digital Man to Tim Whitson on Fri Feb 04 2022 06:20 pm
When you say "several of the doors games no longer would run" - was all t 16-bit DOS door games? Just some of the 16-bit DOS door games Only those th are configured one way or another (e.g. FOSSIL vs UAR for I/O)? If you are fact running sbbs v3.19b (and not v3.19a) and sbbsexec.dll dated 1/2/202 isn't working, then those details will b important to help get to the botto of it.
I will do some more research. I'll put the file back and try to determine what is going on. I won't be able get to it until Sunday.
Rob, I do appreciate all the work you put into this thing.
I appreciate you giving the additional details.
I can see fromr message's PID (Program ID) that you are indeed running SB v3.19b, so I guess I already know that answer:
Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
Another thing to check is the date/time of your exec/dosxtrn.exe file. That could play a role as well.
I went through several of the games. I had been running them on Gamesrv since when I first set it up it would run some of the older one that I believe 3.17 was not running. After playing with the new version it looks like the only game I can't get running is Caribean Contraband. The W & W Communications games (Star Market and Land of Barons) take a while to load but they do play.
I am going to move all the games off Gamesrv and back to Syncrhonet. I'll play with Caribean Contraband and maybe I can get it to run.
I'm not clear: are you sing that Caribean Contraband works with the older sbbsexec.dll but not the newer one? And the W&W Comm games take a while to l with the new sbbsexec.dll, but don't take a while to load when using the old sbbsexec.dll?
When you started this thread, you said there was a regression or new problem introduced in the v3.19b sbbsexec.dll, so I'm trying to understand that.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 368 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 86:28:45 |
| Calls: | 7,895 |
| Calls today: | 1 |
| Files: | 12,968 |
| Messages: | 5,792,010 |