Hello all,
Which platform do YOU run Synchronet on?
If you run on Linux, are you able to run the legacy doors that are built for MS-DOS?
(I ran a MS-DOS based BBS many years ago, but have since migrated most of my systems to Linux)
Do you run any doors that use DOOR32.sys (socket handoff) drop files?
If so (and you're hosting on Windows) have you noticed any issues using DOOR32.sys drop files? The DOOR32.sys spec seems to be plausible for a *nix environment, but I have doubts it would work in the presence of certain Layered Service Provider (LSP) chains that can be installed on Windows.
Looking at the Synchronet source, it appears the code is using Win32 DuplicateHandle -- which is valid, but notes some potential for issues (likely due to the LSPs I mentioned earlier). Microsoft has an alternate API call that seems to allow working around the LSPs by exporting additional state (WSADuplicateSocket(...)), but of course that isn't going to be compliant with the DOOR32.sys spec that *nix systems [presumably] work just fine with?
Anyways, just curious what the Synchronet host landscape looks like for systems hosting doors via Door32.sys.
Hello all,
Which platform do YOU run Synchronet on?
If you run on Linux, are you able to run the legacy doors that are built for MS-DOS?
(I ran a MS-DOS based BBS many years ago, but have since migrated most of my systems to Linux)That's nice.
Do you run any doors that use DOOR32.sys (socket handoff) drop files?No.
Looking at the Synchronet source, it appears the code is using Win32 DuplicateHandle -- which is valid, but notes some potential for issues (likely due to the LSPs I mentioned earlier). Microsoft has an alternate API call that seems to allow working around the LSPs by exporting additional state (WSADuplicateSocket(...)), but of course that isn't going to be compliant with the DOOR32.sys spec that *nix systems [presumably] work just fine with?
Anyways, just curious what the Synchronet host landscape looks like for systems hosting doors via Door32.sys.
Do you run any doors that use DOOR32.sys (socket handoff) drop files?No.
Re: Re: Which platform do you run Synchronet on?
By: Nelgin to Mike Anderson on Tue Dec 01 2020 12:56 am
Do you run any doors that use DOOR32.sys (socket handoff) drop files?No.
There are several doors in the src/doors directory of the Synchronet source repository which use the door32.sys drop file and were ported to *nix by Deuce, if you care to play with them.
Mike Anderson wrote to All <=-
Which platform do YOU run Synchronet on?
If you run on Linux, are you able to run the legacy doors that
are built for MS-DOS?
(I ran a MS-DOS based BBS many years ago, but have since migrated
most of my systems to Linux)
Do you run any doors that use DOOR32.sys (socket handoff) drop
files?
Hello all,
Which platform do YOU run Synchronet on?
If you run on Linux, are you able to run the legacy doors that are built for MS-DOS?
Do you run any doors that use DOOR32.sys (socket handoff) drop files?
Which platform do YOU run Synchronet on?
Anyways, just curious what the Synchronet host landscape looks like for systems hosting doors via Door32.sys.
I'd never heard of Windows LSP, but according to wikipedia, it's a deprecated feature:
https://en.wikipedia.org/wiki/Layered_Service_Provider
The *nix external program execution code (including socket duplication/sharing) code in Synchronet is very much
separate from the Windows implementation of that same function. i.e. We can use WinSock or Win32 API calls just fine
in
the Windows implementation of sbbs_t::external().
Anyways, just curious what the Synchronet host landscape looks like for systems hosting doors via Door32.sys.
there's like 4 doors that use door32.sys so there ya go
i've only ran them on windows bbses
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 595 |
Nodes: | 8 (0 / 8) |
Uptime: | 05:06:14 |
Calls: | 10,784 |
Files: | 5 |
Messages: | 469,678 |