| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 39 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 63:25:15 |
| Calls: | 171 |
| Files: | 117 |
| Messages: | 63,112 |
https://gitlab.synchro.net/main/sbbs/-/commit/b2601ca82c2ef5a0893a65e2 Modified Files:
src/sbbs3/sbbsdefs.h src/sbbs3/scfg/scfgxtrn.c src/sbbs3/xtrn_sec.cpp Log Message:
Add support for 31-line DOOR.SYS file format (alternative to 52-line version)
But for doors that have compatibilty issues with the 52-line DOOR.SYS file created by Synchronet (e.g. Thunder cat V3.30), a sysop can now choose "GAP (original)" for the drop file type and Synchronet will create a 31-line DOOR.SYS file instead.
Re: src/sbbs3/sbbsdefs.h src/sbbs3/scfg/scfgxtrn.c src/sbbs3/xtrn_sec.cpp
By: Rob Swindell (on Windows 11) to Git commit to main/sbbs/master on Tue Oct 15 2024 03:29 pm
https://gitlab.synchro.net/main/sbbs/-/commit/b2601ca82c2ef5a0893a65e2 Modified Files:
src/sbbs3/sbbsdefs.h src/sbbs3/scfg/scfgxtrn.c src/sbbs3/xtrn_sec.cpp Log Message:
Add support for 31-line DOOR.SYS file format (alternative to 52-line version)
But for doors that have compatibilty issues with the 52-line DOOR.SYS file created by Synchronet (e.g. Thunder cat V3.30), a sysop can now choose "GAP (original)" for the drop file type and Synchronet will create a 31-line DOOR.SYS file instead.
I have Thunder Cat v3.30 installed on my BBS, and it runs with the 52-line DOOR.SYS. I updated Synchronet on my system and changed the option to the 31-line DOOR.SYS, but Thunder Cat didn't run. I haven't looked into the error yet, but I reverted back to the 52-line DOOR.SYS and it runs successfully. I'm running the door on dosemu2 on Linux, and I believe Rixter (who said he was seeing this issue) may be running Win32 - though for this issue, I wouldn't think that would make a difference.
created by Synchronet (e.g. Thunder cat V3.30), a sysop can now choose "GAP
Thunder cat V3.30?? wtf
I have Thunder Cat v3.30 installed on my BBS, and it runs with the 52-line
DOOR.SYS. I updated Synchronet on my system and changed the option to the
31-line DOOR.SYS, but Thunder Cat didn't run. I haven't looked into the
error yet, but I reverted back to the 52-line DOOR.SYS and it runs
successfully. I'm running the door on dosemu2 on Linux, and I believe
Rixter (who said he was seeing this issue) may be running Win32 - though
for this issue, I wouldn't think that would make a difference.
Interesting. The problem that Rixter reported was with line 42 (Time credit, in minutes). So it's possible the user account(s) he tested with had banked minutes, but your user does not.
Bummer than the 31-line version doesn't work. That is surprising since that is the original length of the GAP DOOR.SYS file. I wonder if adding 21 blank lines would resolve that problem.
Re: src/sbbs3/sbbsdefs.h src/sbbs3/scfg/scfgxtrn.c src/sbbs3/xtrn_sec.cpp
By: MRO to Rob Swindell (on Windows on Tue Oct 15 2024 09:17 pm
Thunder cat V3.30?? wtf
Re: src/sbbs3/sbbsdefs.h src/sbbs3/scfg/scfgxtrn.c src/sbbs3/xtrn_sec.cpp
By: Digital Man to Nightfox on Tue Oct 15 2024 05:55 pm
I have Thunder Cat v3.30 installed on my BBS, and it runs with the 52-line
DOOR.SYS. I updated Synchronet on my system and changed the option to the
31-line DOOR.SYS, but Thunder Cat didn't run. I haven't looked into the
error yet, but I reverted back to the 52-line DOOR.SYS and it runs
successfully. I'm running the door on dosemu2 on Linux, and I believe
Rixter (who said he was seeing this issue) may be running Win32 - though
for this issue, I wouldn't think that would make a difference.
Interesting. The problem that Rixter reported was with line 42 (Time credit, in minutes). So it's possible the user account(s) he tested with had banked minutes, but your user does not.
Bummer than the 31-line version doesn't work. That is surprising since that is the original length of the GAP DOOR.SYS file. I wonder if adding 21 blank lines would resolve that problem.
I looked into this more, and the door was giving an error value of 62 with the 31-line door.sys. I tried adding 21 blank lines to that door.sys and manually running the door, and it didn't report that error anymore - it just said it was unable to initialize the COM port - maybe because I was running it manually within dosemu rather than running it as a user on my BBS.