That's about what I'm doing right now with my setup. The doors have
quit working, and I don't know if it's the software, or something
Microsoft did in a recent update (I suspect it's the latter).
I updated Synchronet about a month ago. I noticed recently that
tradewars js (which is distributed with synchronet) quit working.
There are some new door settings in SCFG. I suspect maybe you need to play some with those.
From Newsgroup: Micronet.MIN_BBS
Mike,
I updated Synchronet about a month ago. I noticed recently that tradewars js (which is distributed with synchronet) quit working.
There are some new door settings in SCFG. I suspect maybe you need to play some with those.
Most of the non-fossil doors are back online. Several others are generating an OVERFLOW (DOORFRAME ERROR 6) ERROR. The documentation said to put in the AUTOEXEC.BAT file (which is a dummy entry for NTVDM under Windows 10 32-bit;
so I guess I'd have to try AUTOEXEC.NT) the statement SET NO87=ON -- it did not work.
Another Sysop said to copy the sbbsexec files to c:\windows\system32 -- access was denied. I guess I have to reboot into command prompt mode, and
do it.
okay what doorgames do you have problems with exactly?
you shouldn't have to do any of this.
no. you right click on cmd.exe and choose run as administrator
then go into your administer command prompt and copy the files.
i'm surprised you have ANY doorgames working on synchronet without
copying the fossil to windows\system32
so answer me this:
what operating system?
what doorgames?
what version of synchronet?
Tried that...they still don't work. I had to logon locally as I
could not remember the Windows password (I had been using a PIN to
logon). My Microsoft passwords wouldn't work.
i'm surprised you have ANY doorgames working on synchronet without copying the fossil to windows\system32
I never had that problem before 3.19 was released.
so answer me this:
what operating system?
Windows 10 32-bit. I have a bunch of legacy 16-bit doors that will NOT run under 64-bit.
I ran the jsexec install-xtrn.js, and got several doors installed,
but I haven't tested them out. There were some doors that would not
Tried that...they still don't work. I had to logon locally as I
could not remember the Windows password (I had been using a PIN to
logon). My Microsoft passwords wouldn't work.
i had that problem too. also it just wouldnt work when it was setup to autologon. so i just reset my password on the microsoft site.
so i can help you sunday, so email me. it wont take that long. i am working 2 jobs so my time is short now.
i'll backup everything before making any changes and you can watch as
i check things out and make changes.
Send an email to me at wx1der at gmail dot com -- I'm in a pattern with
2 days of storms, 2 days of dry weather, and it starts over again.
Daryl
you email me. that way i know you see it when i reply back
From Newsgroup: Micronet.MIN_BBS
you email me. that way i know you see it when i reply back
Well, I tried an option that Rob Swindell (digital man) suggested.
I changed the dropfile from DOOR.SYS to DORINFO1.DEF, and placed the dropfile in the door directory. Preliminary testing on 2 of the doors
solved the problem...but, I have a whole slew of other doors to redo.
Daryl
... Why does the Psychic Hotline have to ask for your name??
that solution makes no sense. if your doors were working fine before
and they didn't why would changing the dropfile fix it.
From Newsgroup: Micronet.MIN_BBS
that solution makes no sense. if your doors were working fine before and they didn't why would changing the dropfile fix it.
It may have been a deal with the format of the DOOR.SYS file itself.
Daryl
i'd have to see it to see what the problem is.
you didn't email me so i couldnt take a look.
i'm curious to see what the problem is and if you want to know i can
find out.
From Newsgroup: Micronet.MIN_BBS
i'd have to see it to see what the problem is.
you didn't email me so i couldnt take a look.
I never saw your email, so I didn't know where to send it.
i'm curious to see what the problem is and if you want to know i can find out.
It appears that changing the dropfile from door.sys to dorinfo1.def
solved the problem in most cases. There are a few doors that won't
run at all, so I'm still working on those...but that's not critical.
My main issue now is where the BBS won't run the nightly maintenance batchfile for the doorgames and the message area processing. I can run
it from a scheduling utility, but it does NOT busy out the BBS (where
no one can login while this is done, to avoid corrupting the message
areas, file areas, and doorgames). So, I have to manually take the nodes offline while this runs...which requires being up at midnight (although
if I have thunderstorms in the area at the time, I take care of that manually once the weather clears, and go to bed early). Then, I have to
be up at 7am to do my vital signs, so I don't get much sleep at night
(I wasn't getting such, anyway...and have to take a power nap).
In short, the batchfile starts, and then immediately exits with error level 255, without doing anything.
From Newsgroup: Micronet.MIN_BBS
I was about to say the same thing....
-Nugax
here's an example of a time event that works.
notice the settings for it. if you change one or two of those
settings, it just wont launch.
It appears that changing the dropfile from door.sys to dorinfo1.def
solved the problem in most cases. There are a few doors that won't
run at all, so I'm still working on those...but that's not critical.
Codefenix wrote to Daryl Stout <=-
No idea WHY it works. But it does.
As a door author since 1998, I can tell you why: there are several intreptations of the DOOR.SYS standard and nearly all of them are wrong. I always recommend using DORINFO1.DEF or DORINFOx.DEF if the door supports it.
As a door author since 1998, I can tell you why: there are several intreptations of the DOOR.SYS standard and nearly all of them are wrong. I always recommend using DORINFO1.DEF or DORINFOx.DEF if the door supports it.
Be that as it may, the issue never surfaced until moving the BBS to Windows 10. It was the same DOOR.SYS file passed to the door program before and after the move.
THAT'S the part that I don't understand.
whats the doorgame? what exactly happened? it could not find the dropfile? was it only displaying local?
what os did you move FROM?
digimaus wrote to Codefenix <=-
I developed my own dropfile format for my doors and tucked it away. I
may bring it back as an additional solution for BBS systems that can create their own dropfiles (Maximus and Telegard come to mind).
what os did you move FROM?
Moved from Vista to Windows 10.
Now that you're done laughing at that previous statement, I did also update
SBBS from 3.18 to 3.20a at the same time. Something I didn't think about until now is it's possible the newer version of SBBS could be writing the DOOR.SYS file differently now than it did in the older version.
yes, i was like wtf vista?!
i've seen that issue with that door library and i've just used dorinfo1.def
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 255 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 152:47:44 |
| Calls: | 1,724 |
| Calls today: | 4 |
| Files: | 4,107 |
| D/L today: |
10 files (9,986K bytes) |
| Messages: | 392,941 |
