it would be cool if it was made into a mystic bbs game.
to
spawn off to run it from my board.
Not many people run wwiv, but more run Mystic.
to
spawn off to run it from my board.
Not many people run wwiv, but more run Mystic.
Who runs WWiV? I'm talking about regular doors.
Not many people run wwiv, but more run Mystic.
Who runs WWiV? I'm talking about regular doors.
Maybe you're not aware of it, but one of the original and most popular onl BBS games that goes by the name "Food Fight!" was written (by Rigor Mortis a "WWIV Chain". It works in all versions of Synchronet too, but not most o BBS programs since it sends its output via DOS int21h (not FOSSIL or direc UART/COM I/O), it sends WWIV color codes, not ANSI escape sequences, and i reads WWIV's CHAIN.TXT file (not any other "standard" drop file). https://www.bbsgames.org/wiki/Food_Fight
Not many people run wwiv, but more run Mystic.
Who runs WWiV? I'm talking about regular doors.
Maybe you're not aware of it, but one of the original and most popular onl BBS games that goes by the name "Food Fight!" was written (by Rigor Mortis a "WWIV Chain". It works in all versions of Synchronet too, but not most o BBS programs since it sends its output via DOS int21h (not FOSSIL or direc UART/COM I/O), it sends WWIV color codes, not ANSI escape sequences, and i reads WWIV's CHAIN.TXT file (not any other "standard" drop file). https://www.bbsgames.org/wiki/Food_Fight
Shouldn't this be able to run on any BBS that makes the CHAIN.TXT dropfile then?
it would be cool if it was made into a mystic bbs game.
That's just stupid. What's wrong with it being a regular door? I hate when people make things that are "bbs specific" that SHOULD be
doors. There are ton of neat mystic doors that are wasted on shit because they are mystic only.
I hate having to have a mystic setup to rlogon to so I can run MRC just to spawn off to run it from my board.
I hate having to have a mystic setup to rlogon to
so I can run MRC just to spawn off to run it from my board.
Agreed. And I wish I could use the bbs onliners and last call doors... I tried to write scripts to handle them, but failed miserably.
I hate having to have a mystic setup to rlogon to so I can run MRC just to spawn off to run it from my board.
I'm surprised nobody has written a stand-alone MRC door. A DOS MRC door
is on my own to-do list, but a bit low on the list at the moment. Too
many doors to crack. ;)
Agreed. And I wish I could use the bbs onliners and last calldoors... I
tried to write scripts to handle them, but failed miserably.
I guess the limiting factor for writing a cross-platform BBS oneliners and last call doors would be access to the message base. I don't know how
many varieties of message base there would be to support? JAM, Squish, *.MSG?
I'm surprised nobody has written a stand-alone MRC door. A DOS MRC door is my own to-do list, but a bit low on the list at the moment. Too many doors crack. ;)
Quoting Akacastor to Shurato <=-
I guess the limiting factor for writing a cross-platform BBS oneliners
and last call doors would be access to the message base. I don't know
how many varieties of message base there would be to support? JAM, Squish, *.MSG?
There was a cross-platform oneliners a few years ago that stored the info on the interwebz instead of the message base. I wrote a door that worked with it and the last callers. Much easier then accessing the message base, but when he shut things down that was the end of it.
I hate having to have a mystic setup to rlogon to
so I can run MRC just to spawn off to run it from my board.
I'm surprised nobody has written a stand-alone MRC door. A DOS MRC door is on my own to-do list, but a bit low on the list at the moment. Too many doors to crack. ;)
Something I feel like always needs to be asked, because it supports everything - does Synchronet already support something like this? I
think they do have a oneliner system at least. Is there any kind of standard to implement for this, before reinventing the wheel?
wouldn't be useful to Exodus for example)
I guess the server would make sense to have a simple REST API and the clients could send HTTP GET to retrieve the lists. Should be pretty straightforward to implement on both ends.
via whatever scripting the sysop chooses, or an external door (DOS?
Win32? OS/2?) could be created. (at least this door wouldn't need
access to message bases)
Something I feel like always needs to be asked, because it supports everything - does Synchronet already support something like this? I think they do have a oneliner system at least. Is there any kind of standard to implement for this, before reinventing the wheel?
Maybe if the DOS door used named pipes to talk to a proper 32-bit locally-run server that then talked to the MRC server?
Maybe if the DOS door used named pipes to talk to a proper 32-bit locally-run server that then talked to the MRC server?
DOS programs don't support named pipes.
everything - does Synchronet already support
something like this? I think
they do have a oneliner system at least. Is there
any kind of standard to
implement for this, before reinventing the wheel?
There's this: https://gitlab.synchro.net/main/sbbs/-/tree/master/xtrn/oneliners
It uses JSON over TCP for shared database stuff.
On 29 Jun 2024, Digital Man said the following...
Maybe if the DOS door used named pipes to talk to a proper 32-bit locally-run server that then talked to the MRC server?
DOS programs don't support named pipes.
indeed they do. i can open and read from for example
\\.\pipe\something
from a dos pascal program and from what i've tested at least int21/5F35h (DosPeekNmPipe) and 5F33h (DosQNmPHandleState) seem to work to query pipe status
http://www.ctyme.com/intr/int-21.htm
On Windows 7 32-bit. OS/2 works too, but differenly.
Nope, those pipe functions are *not* present in the supported functions
of MS-DOS v4.
And indeed, from your linked reference:
"This function was introduced by LAN Manager but is also supported by the Novell DOS Named Pipe Extender, Banyan VINES, OS/2 Virtual DOS Machines, and others" not [MS/PC]-DOS.
<grabs his MS-DOS programmers guide>
Nope, those pipe functions are *not* present in the supported functions
of MS-DOS v4.
Yes, so are you mad I didn't preface that with "You could install LAN Manager Client for DOS, Novell network support and use DOSNP.EXE or run inside a VDM using named pipes" ?
Sysop: | Immortal |
---|---|
Location: | Spanish Fork, UT |
Users: | 16 |
Nodes: | 10 (0 / 10) |
Uptime: | 18:57:55 |
Calls: | 560 |
Files: | 3,435 |
Messages: | 103,373 |