Hey folks, using Ubuntu 20.04 and moving my BBS to it. When I run ./mis server it shows up as UT8 on the screen and the ANSI characters are all wrong.. What are the rest of you doing with that? Are you using a different encoding or font? I can get it to display properly but then the backspace key doesn't work normally you must hit ctrl-backspace to backspace back. I am at a loss here, any ideas???

Al

... If a pig loses its voice, is it disgruntled?

--- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (1:267/157)

Hi Al,

Hey folks, using Ubuntu 20.04 and moving my BBS to it. When I run ./mis server it shows up as UT8 on the screen and the ANSI characters are all wrong.. What are the rest of you doing with that? Are you using a

I'm still trying to figure it out. If I set in the configuration to use CP437, the ansi is ok. But when I log in via ssh/telnet, I need to set the terminal program to use CP437 as well. However, the ANSI is still screwed up regardless of which setting you use when you log in using netrunner (nr21 version).

Edmund

... Classic: A book which people praise but don't read. - Mark Twain

--- Mystic BBS v1.12 A47 2021/11/18 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

I'm still trying to figure it out. If I set in the configuration to use CP437, the ansi is ok. But when I log in via ssh/telnet, I need to set the terminal program to use CP437 as well. However, the ANSI is still screwed up regardless of which setting you use when you log in using netrunner (nr21 version).

Are you using the default ANSIs or have you created new ones? Some of this could depend on how the ANSIs are saved.

There are three settings for character translation, one for the local UI and two used for each user when a connection is established.

The local UI setting is in System Configuration> General settings. When Mystic is installed it should give you a quiz so it can determine what that setting should. When you run "./mystic -l" (make sure you have the -l) the ANSI should look normal. If it does not, try changing it.

The second settings are in the Login/Matrix setting. The "default codepage" setting is what Mystic defaults to for each user that connects. Almost always you'll want this set to CP437. Then there is the "Ask Codepage" setting which can be set to "Detect" "Ask" or a specific codepage. You can try setting that to Ask to experiment with it but you can probably keep it on Detect unless you are having issues.

... Light year: 1/3 less calories than your regular year

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 19 Nov 2021, Edmund Wong said the following...

I'm still trying to figure it out. If I set in the configuration to use CP437, the ansi is ok. But when I log in via ssh/telnet, I need to set the terminal program to use CP437 as well. However, the ANSI is still screwed up regardless of which setting you use when you log in using netrunner (nr21 version).

The issue you are having is easily fixed by going into Configuration then General settings and choosing CP437 as your local code page, also set it to CP437 in Login/Matrix as the default codepage.. My issue was more of a Linux Issue and I solved it.. Is what I said correct g00r00??

AL

... As I said before, I never repeat myself

--- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (1:267/157)