I'm currently running my BBS using Synchronet on Linux. I have DOSEMU2 set up for DOS-based doors. I've set up my old
RemoteAccess BBS setup from the 90s to run as a door, and it runs, but it seems it's not detecting the user's ANSI
capabilities, and it's reverting to no ANSI. I'm curious if anyone has set up any DOS BBS software as a door in Linux with
DOSEMU? I'm wondering how I can get it to detect whether the user has ANSI capabilities.
I've checked the command-line parameters for RA.EXE (RemoteAccess), and it doesn't have a parameter to force ANSI. But it
also looks like Synchronet doesn't provide a command-line option to specify whether the user's terminal supports ANSI.
(unless I missed something in the docs..)
I'm currently running my BBS using Synchronet on Linux. I have DOSEMU2 set up for DOS-based doors. I've set up my old
RemoteAccess BBS setup from the 90s to run as a door, and it runs, but it seems it's not detecting the user's ANSI
capabilities, and it's reverting to no ANSI. I'm curious if anyone has set up any DOS BBS software as a door in Linux with
DOSEMU? I'm wondering how I can get it to detect whether the user has ANSI capabilities.
I've checked the command-line parameters for RA.EXE (RemoteAccess), and it doesn't have a parameter to force ANSI. But it
also looks like Synchronet doesn't provide a command-line option to specify whether the user's terminal supports ANSI.
(unless I missed something in the docs..)
under synchronet, there is "dosutils" in there is an ansi.com file... run that right before your door.. have to do that on a couple of other DOS door games that don't recognise the ansi capabilities. give that a whirl
I've checked the command-line parameters for RA.EXE (RemoteAccess),
and it doesn't have a parameter to force ANSI. But it also looks
like Synchronet doesn't provide a command-line option to specify
whether the user's terminal supports ANSI. (unless I missed
something in the docs..)
that is technically in the door drop file i beleive. the main issue you're going to have maybe the runtime error crap from turbo pascal stuff. having the dosemu flag set to 486 may stop that however.
I've checked the command-line parameters for RA.EXE (RemoteAccess),
and it doesn't have a parameter to force ANSI. But it also looks
like Synchronet doesn't provide a command-line option to specify
whether the user's terminal supports ANSI. (unless I missed
something in the docs..)
runremote access in local mode "RA -L".. just worked perfectly for me :D
under synchronet, there is "dosutils" in there is an ansi.com file... run that right before your door.. have to do that on a couple of other DOS door games that don't recognise the ansi capabilities. give that a whirl
runremote access in local mode "RA -L".. just worked perfectly for me :DInteresting, I wouldn't have thought the local parameter would work. The parameters I'm using are -C1 -R%d . Maybe I should
try -L to see if that's any different. However, if you're telling RA to run in local mode, I'm not sure if it will do any
detection of the remote user's terminal capabilities (which would still be useful).
yea i realise that, but as you said in the other note, it's not designed to run as a door so.
yea i realise that, but as you said in the other note, it's not designed to run as a door so.Yes, but RemoteAccess did take some command-line parameters (such as the user's connected speed, etc.) because it was
possible that another program would have answered the modem first (such as FrontDoor, a FidoNet mailer), and in such a case,
it was useful to be able to leave the modem connected and have RemoteAccess take over. That still wasn't local mode.
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 584 |
Nodes: | 8 (0 / 8) |
Uptime: | 06:01:16 |
Calls: | 10,746 |
Files: | 5 |
Messages: | 447,223 |
Posted today: | 1 |