I don't know what happened, but all the external doors I had on
the BBS quit working. I had made no changes to the configuration
or batchfile setups, but none of them run.
So, I zapped them all from SCFG, and reinstalled/re-entered them
from scratch...and still nothing works. I have to use a batchfile
for the doors, as several require the RTE200 patch to run properly.
The command line is batchfil.bat (where batchfile is the name of
the batchfile). I don't have anything after that, such as %f
I even had to get rid of the SyncNews door, as it quit working
as well.
I'm running Windows 10 32-bit, with Synchronet 3.19c
I can't run the BBS under Windows 11, as the legacy doors won't
work under 64-bit, and my Windows 11 laptop keeps going to sleep
and powering down after a certain period of time.
I'm sure it's something simple, but as of now, except for a few
Synchronet doors (I noticed the Synchronet BBS List had changed its
format), while the doors are still "on the computer", they won't
run. I looked at the wiki site for it, and it didn't really give
any help, either.
With a threat of thunderstorms and severe weather here from Sunday
through much of next week, the BBS will be down for several days,
and I won't be doing much until Easter weekend, if even then.
As a sysop, debugging problems like this, I would look closely at the settings in SCFG and the log output when these programs are run (or attempted to be run) from the BBS. You say you "Looked at the wiki
site", but what did you learn? What did you try? What are you seeing?
Rob,
As a sysop, debugging problems like this, I would look closely at the settings in SCFG and the log output when these programs are run (or attempted to be run) from the BBS. You say you "Looked at the wiki site", but what did you learn? What did you try? What are you seeing?
As for the Wiki site, I was looking on how to set up the doors. I had not changed anything, and one day, the doors just quit working. You would choose the desired door, and the system went right back to the doors (external programs menu). So, I deleted all the doors in SCFG, and re-entered all of them, but they either won't echo out the comport (with or without a fossil), or the door just crashes with an error message, and returns to the external programs menu.
I noted the external programs are showing FOSSIL or UART for the "mode"
in SCFG, but no matter what I try, nothing works.
I had to set up a batchfile for each door, as some require the RTE200 patch for the doors to run. So, the command would be DOORNAME.BAT for the batchfile -- I didn't have anything after that (such as %# for the node number)...but even trying that did no good.
I am tempted to go back to a much older backup with a previous version
of Synchronet. If that doesn't do it, then it's something that Microsoft Windows did with Windows 10 32-bit.
As for the Wiki site, I was looking on how to set up the doors. I had not
changed anything, and one day, the doors just quit working. You would choos
the desired door, and the system went right back to the doors (external programs menu). So, I deleted all the doors in SCFG, and re-entered all of them, but they either won't echo out the comport (with or without a fossil)
or the door just crashes with an error message, and returns to the external
programs menu.
What's the error message?
I noted the external programs are showing FOSSIL or UART for the "mode" in SCFG, but no matter what I try, nothing works.
Did you try modern 32-bit/socket doors?
As for the Wiki site, I was looking on how to set up the doors. I had not
changed anything, and one day, the doors just quit working. You would choos
the desired door, and the system went right back to the doors (external programs menu). So, I deleted all the doors in SCFG, and re-entered all of them, but they either won't echo out the comport (with or without a fossil)
or the door just crashes with an error message, and returns to the external
programs menu.
What's the error message?
You may have already asked him , but I wonder if he recently upgraded.
There are some new options on the door setup screen in SCFG. I noticed
that tradewars js (that comes with synchronet) was broken on my system again. I never change the settings for that one so it seemed weird that I started getting invalid configuration errors when trying to open the door...
I assume I need to tweak the new settings to get tradewars js to work
again.
You may have already asked him , but I wonder if he recently upgraded. There are some new options on the door setup screen in SCFG. I noticed that tradewars js (that comes with synchronet) was broken on my system again. I never change the settings for that one so it seemed weird that I started getting invalid configuration errors when trying to open the door..
What's the error message?
I assume I need to tweak the new settings to get tradewars js to work again.
I don't think so. More likely, it's just a data file error. Running 'jsexec twint500' will likely fix your issue, but I don't think that has anything to d
with the issue that Daryl is having.
You may have already asked him , but I wonder if he recently upgraded. There are some new options on the door setup screen in SCFG. I noticed that tradewars js (that comes with synchronet) was broken on my system again. I never change the settings for that one so it seemed weird that I started getting invalid configuration errors when trying to open the door..
What's the error message?
Invalid configuration
I assume I need to tweak the new settings to get tradewars js to work again.
I don't think so. More likely, it's just a data file error. Running 'jsexec twint500' will likely fix your issue, but I don't think that has anything to d
with the issue that Daryl is having.
I changed the new I/O Method setting from the default 'FOSSIL or UART' to 'Standard' and that fixed it.
Invalid configuration
Okay, just to confirm we're takling about the same thing: Tradwars 2 written i
JavaScript: xtrn/tw2/tw2.js? That script does have that exact error message, b
it does have: "ERROR: Configuration invalid" which would be fixed by running int500.js again.
I assume I need to tweak the new settings to get tradewars js to work again.
I don't think so. More likely, it's just a data file error. Running 'jsexec twint500' will likely fix your issue, but I don't think that has anything to d
with the issue that Daryl is having.
I changed the new I/O Method setting from the default 'FOSSIL or UART' to 'Standard' and that fixed it.
That setting will have zero impact on JavaScript modules/doors. Something else
hanged if the problem/error went away.
Invalid configuration
Okay, just to confirm we're takling about the same thing: Tradwars 2 written i
JavaScript: xtrn/tw2/tw2.js? That script does have that exact error message, b
it does have: "ERROR: Configuration invalid" which would be fixed by running int500.js again.
Yes, and that is the message.
I assume I need to tweak the new settings to get tradewars js to work again.
I don't think so. More likely, it's just a data file error. Running 'jsexec twint500' will likely fix your issue, but I don't think that has anything to d
with the issue that Daryl is having.
I changed the new I/O Method setting from the default 'FOSSIL or UART' to 'Standard' and that fixed it.
That setting will have zero impact on JavaScript modules/doors. Something else
hanged if the problem/error went away.
Well, I did not change anything else. I also didn't change anything before it started doing that, either, so who knows? I just know that as of yesterday it was working again after not working for about a week.
What's the error message?
Did you try modern 32-bit/socket doors?
Is the batch file executing? As a test, if you put a "pause" in the
batch file, do you see the batch file running and waiting for a key
press?
Rob,
What's the error message?
Overflow -- DOORFRAME ERROR 6. The documentation said to put in the AUTOEXEC.BAT file (likely AUTOEXEC.NT for Windows 10) the statement of
SET NO87=ON -- tried it, and it didn't work.
Did you try modern 32-bit/socket doors?
Not yet...I have had other issues outside the BBS. First, I'm going to need cardiac ablation surgery soon to take care of the atrial fibrillation, and the congestive heart failure. Second, power was out much of Monday, as the power company was doing infrastructure work. They gave no notice of the downtime, and it was out so long, that I had to throw out all the food I had in the refrigerator/freezer (there is no food here now). Third, we are in a stormy pattern with 2 days of thunderstorms, 2 days of sun, 2 days of thunderstorms, 2 days of sun, etc. So, that leaves precious little time
for computer or BBS work.
Is the batch file executing? As a test, if you put a "pause" in the batch file, do you see the batch file running and waiting for a key press?
It starts, the door generates the error noted, and quits.
You get that same error for every single one of your doors?
Which drop file is the door in question using? Having you tried configuring it to use a different drop file format that's supported by Synchronet (just about all of them)?
Rob,
You get that same error for every single one of your doors?
Error 6 for the Sunrise Doors, and Error 53 for the Parole doors.
I could not find an error log file for the Shining Star doors, so I
have to some more checking.
Which drop file is the door in question using? Having you tried configuring it to use a different drop file format that's supported by Synchronet (just about all of them)?
I use either DOOR.SYS or DORINFO1.DEF -- the PTB Ham Radio Doors use DORINFO1.DEF and the DreamNet Doors use DOOR.SYS -- both of those were without fossil drivers, so that's where the DOSXTRN module works with these...
and those work just fine.
I went into Command Prompt as Administrator, and copied the sbbsexec
files to c:\windows\system32 -- and the doors still didn't work.
Can you try changing the drop file type for those doors to another supported format?
Didn't you say earlier that *all* your doors stopped working? I'm confused. Some are working and some are not or all are not? Please
clarify and try to find a pattern between those that work and those
that do not.
Rob,
Can you try changing the drop file type for those doors to another supported format?
Changing it from DOOR.SYS to DORINFO1.DEF and putting the dropfile into the door directory solved the problem.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 70:41:30 |
| Calls: | 6,656 |
| Calls today: | 2 |
| Files: | 12,200 |
| Messages: | 5,332,157 |
| Posted today: | 1 |