Thanks to the help from nelgin@EOTLBBS I now have a pretty well functioning BBS that supports Acorn BBC Mode 7 (teletext/viewdata). With my current BBS (OBBS from 1984) the user selects if they would like BBC mode 7 support/vt100 or ANSI at the start of their session. I'd like to set up SBBS so that connections coming in on port 6502 default to the terminal settings that allow BBC Mode 7 graphics to show and connections coming in on port *TBD* default to ANSI with vt100 fallback. Or have everything on 6502 but in the same way as my current BBS disable auto detection and have the user select their terminal type each session from 3 different profiles. Is this possible? I've scoured the different files and cannot find one containing the default terminal settings or how to disable auto terminal detection. I did try using the PETSCII port as 6502 and changing the .asc files I've used for BBC Mode 7 to .seq but this corrupts them.
Any help or ideas on how to achieve this, or achieve this in a different way welcome!
The answer.* file is displayed before login.js is executed, so you might want your answer.asc a blank/0-byte file (your >answer.ans could contain ANSI since it'll only be displayehd to ANSI-detected terminals).
You could check the server port in your login.js and take a different control path based on that.
Thanks for the reply digital man.
The answer.* file is displayed before login.js is executed, so you might want your answer.asc a blank/0-byte file (your >answer.ans could contain ANSI since it'll only be displayehd to ANSI-detected terminals).
I did try something similar to this previously, however if a person logs on with their BBC Micro (and a Mode 7 .asc file has been created) as they haven't got to the logon prompt where it loads up their terminal preferences it just shows them the un-formatted file.
You could check the server port in your login.js and take a different control path based on that.
This sound like what I'd like to do, ideally I'd like when they login on port 6502 it sets their formatting as extended ascii on and utf8 and ansi off...but I'm at a loss on how to do that.
Something like this in your exec/login.js:
Re: Setting a default terminal type for a specific port
By: vela025 to Digital Man on Wed Feb 14 2024 01:05 pm
Thanks for the reply digital man.
The answer.* file is displayed before login.js is executed, sowant your answer.asc a blank/0-byte file (your >answer.ans could
you might
contain ANSI since it'll only be displayehd to ANSI-detected
terminals).
I did try something similar to this previously, however if a
person logs on with their BBC Micro (and a Mode 7 .asc file has
been created) as they haven't got to the logon prompt where it
loads up their terminal preferences it just shows them the
un-formatted file.
I'm suggesting a blank/0-byte answer.asc file. Have your login.js
file display something to these non-ANSI users if you like, but don't
make it an answer.* file.
You could check the server port in your login.js and take acontrol path based on that.
different
This sound like what I'd like to do, ideally I'd like when they
login on port 6502 it sets their formatting as extended ascii on
and utf8 and ansi off...but I'm at a loss on how to do that.
Something like this in your exec/login.js:
if(client.socket.local_port == 6502) {
console.autoterm = 0;
console.printfile("somefile");
// etc.
}
Something like this in your exec/login.js:
Ahh OK I think that might be something I could manage, thank you.
I'm currently playing with msglist.js so that it presents nicely in
mode 7, however this breaks the ANSI version...could I have two
versions of msglist.js (e.g. msglist.js and msglist7.js) and use a
similar logic to above to direct the user to the correct version? Or
would it be best to instead have an extra menu entry for the adapted msglist.js from the main menu?
---
_ Synchronet _ Vertrauen _ Home of Synchronet _
[vert/cvs/bbs].synchro.net
Something like this in your exec/login.js:
Ahh OK I think that might be something I could manage, thank you.
I'm currently playing with msglist.js so that it presents nicely in mode 7, however this breaks the ANSI version...could I have two versions of msglist.js (e.g. msglist.js and msglist7.js) and use a similar logic to above to direct the user to the correct version? Or would it be best to instead have an extra menu entry for the adapted msglist.js from the main menu?
On Wed, 14 Feb 2024 13:46:12 -0800
"Digital Man" (VERT) <VERT!Digital.Man@endofthelinebbs.com> wrote:
Re: Setting a default terminal type for a specific port
By: vela025 to Digital Man on Wed Feb 14 2024 01:05 pm
Thanks for the reply digital man.
The answer.* file is displayed before login.js is executed, sowant your answer.asc a blank/0-byte file (your >answer.ans could contain ANSI since it'll only be displayehd to ANSI-detected terminals).
you might
I did try something similar to this previously, however if a
person logs on with their BBC Micro (and a Mode 7 .asc file has
been created) as they haven't got to the logon prompt where it
loads up their terminal preferences it just shows them the
un-formatted file.
I'm suggesting a blank/0-byte answer.asc file. Have your login.js
file display something to these non-ANSI users if you like, but don't
make it an answer.* file.
You could check the server port in your login.js and take acontrol path based on that.
different
This sound like what I'd like to do, ideally I'd like when they
login on port 6502 it sets their formatting as extended ascii on
and utf8 and ansi off...but I'm at a loss on how to do that.
Something like this in your exec/login.js:
if(client.socket.local_port == 6502) {
console.autoterm = 0;
console.printfile("somefile");
// etc.
}
He might have to specifically set the terminal type to accept IBM
extended ASCII (CP437) otherwise SBBS will filter out the BBC Mode 7
control codes also./sbbs/exec/load/termdesc.js may help with that.
For terminal output, CP437 is the default charset, so no 8th bit
filtering should be happening.
When you say "accept IBM extended ASCII", it sounds like you're
talking about input (from the user's keyboard), but I think you're
talking about output (from the server).
On Wed, 14 Feb 2024 15:42:40 -0800
"Digital Man" (VERT) <VERT!Digital.Man@endofthelinebbs.com> wrote:
For terminal output, CP437 is the default charset, so no 8th bit
filtering should be happening.
When you say "accept IBM extended ASCII", it sounds like you're
talking about input (from the user's keyboard), but I think you're
talking about output (from the server).
If going through a terminal setup through Default User Settings,
there's an option:
Does your terminal support IBM extended ASCII (CP437)?
If you select No, then the BBS will not send mode 7 characters. This
has to be selected as yes.
Re: Re: Setting a default terminal type for a specific port
By: nelgin to All on Wed Feb 14 2024 06:07 pm
On Wed, 14 Feb 2024 15:42:40 -0800
"Digital Man" (VERT) <VERT!Digital.Man@endofthelinebbs.com> wrote:
For terminal output, CP437 is the default charset, so no 8th bit filtering should be happening.
When you say "accept IBM extended ASCII", it sounds like you're
talking about input (from the user's keyboard), but I think
you're talking about output (from the server).
If going through a terminal setup through Default User Settings,
there's an option:
Does your terminal support IBM extended ASCII (CP437)?
If you select No, then the BBS will not send mode 7 characters.
This has to be selected as yes.
Right and "yes" is the default.
| Sysop: | zerwind |
|---|---|
| Location: | Worcester, Ma |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 00:46:54 |
| Calls: | 33 |
| Files: | 1,943 |
| Messages: | 16,169 |