Well, I thought I had the BBS set up to run the doors in
legacy mode, and even checked the command prompt window.
The legacy mode is activated, but the older doors don't
work.
What is "legacy mode"?
Rob,
What is "legacy mode"?
Where the 16-bit doors can run under Windows 10 32-bit.
I'm wondering if it's a DOSFIX (runtime 200 error), and
need to convert all the doors to just run off a batchfile.
More likely, it's one of these known configuration problems: http://wiki.synchro.net/faq:win#sbbsexecdll
Rob,
More likely, it's one of these known configuration problems: http://wiki.synchro.net/faq:win#sbbsexecdll
What I ended up doing was making backups of the ctrl, data, exec,
and text directories (with their subdirectories), then doing a full
install of Synchronet. Then, I copied that data back to the respective directories. To finish it, I copied NTVDM*.* from c:\windows\system32
to c:\sbbs\exec -- and all is working.
There are only 2 issues left...
1) I think it's because of the monitor resolution...in SyncTerm, I
have the mode at 80x25, but the bottom left of it looks funky.
2) Some of the incoming FTN/QWK packets are "bad"...not sure what
the cause is of that.
2) Some of the incoming FTN/QWK packets are "bad"...not sure what
the cause is of that.
Still using the 16-bit DOS version of PKUNZIP?
Most likely, the only thing you *needed* to do was copy sbbsexec.dll to your Windows/system32 directory.
Which version of SyncTERM? Post bug reports for SyncTERM here: https://sourceforge.net/p/syncterm/tickets/
2) Some of the incoming FTN/QWK packets are "bad"...not sure what
the cause is of that.
Still using the 16-bit DOS version of PKUNZIP?
Sysop: | KrAAB |
---|---|
Location: | Donna, TX |
Users: | 4 |
Nodes: | 20 (0 / 20) |
Uptime: | 15:07:45 |
Calls: | 559 |
Calls today: | 4 |
Files: | 2,286 |
Messages: | 46,340 |