Hi,
i'm setting up a bbs using Mystic BBS software but i've encountered a problem that i can't solve: is there a way to configure it for text only terminals?
I'm using a Sinclair Spectrum to connect but i always got characters that are not interpreted by the (real simple) terminal program.
My focus is a bbs for computers such as Commodore 64, MSX, etc. etc. and they don't have ansi-bbs...

Thanks,
Bruno

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Paul.Hayton@f100.n770.z3.binkp.net

On 12/11/17, Todd Yatzook pondered and said...

characters that are not interpreted by the (real simple) terminal program. My focus is a bbs for computers such as Commodore 64, MSX, e etc. and they don't have ansi-bbs...

Should be able to. Just use all straight .asc files in the TEXT folder, have the BBS set to detect the codepage and emulation.

Yes agree I would create a text / asc only theme and offer that :)

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

Hi,

i'm setting up a bbs using Mystic BBS software but i've encountered a problem that i can't solve: is there a way to configure it for text only terminals? I'm using a Sinclair Spectrum to connect but i always got characters that are not interpreted by the (real simple) terminal program. My focus is a bbs for computers such as Commodore 64, MSX, etc. etc. and they don't have ansi-bbs...

Should be able to. Just use all straight .asc files in the TEXT folder, have the BBS set to detect the codepage and emulation.

Tried, but i still get ansi characters:

(UMystic BBS v1.12 A35 for Linux Node 1
Copyright (C) 1997-2017 By James Coyle

(0) Ascii (No Color)
(1) Ansi (Color)

Graphics Mode -> 0

[0] MS-DOS CP437
[1] UTF-8

Select Terminal Codepage [Enter = CP437]: 1

Available themes:

1 ..... HAL's theme
2 ..... Default

Select your theme [Enter/Default]: 1


==================================

As you can see at the very start of each line i got unexpected characters. How i can avoid this behaviour?

Thanks,
Bruno

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Todd.Yatzook@f799.n142.z1.binkp.net

On 12/11/17, bruno.grampa@gmail.com said the following...

Hi,
i'm setting up a bbs using Mystic BBS software but i've encountered a problem that i can't solve: is there a way to configure it for text only terminals? I'm using a Sinclair Spectrum to connect but i always got characters that are not interpreted by the (real simple) terminal
program. My focus is a bbs for computers such as Commodore 64, MSX, etc. etc. and they don't have ansi-bbs...

Should be able to. Just use all straight .asc files in the TEXT folder, have the BBS set to detect the codepage and emulation.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.g00r00@f215.n129.z1.binkp.net

As you can see at the very start of each line i got unexpected characters. i can avoid this behaviour?

I am not really seeing any unexpected characters in this example, but it
looks like it has been filtered between your initial post and it arriving to me.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.g00r00@f215.n129.z1.binkp.net

i'm setting up a bbs using Mystic BBS software but i've encountered a problem that i can't solve: is there a way to configure it for text only terminals? I'm using a Sinclair Spectrum to connect but i always got characters that are not interpreted by the (real simple) terminal
program. My focus is a bbs for computers such as Commodore 64, MSX, etc. etc. and they don't have ansi-bbs...

You can configure it to not use ANSI at all if you want to, but by the default settings it should be detected on the login (or in your case not detected) and then Mystic will switch to ASCII.

I think the issue is probably that the defaults use the IBM-PC ASCII character set so there are probably going to be places where you'd need to reconfigure those prompts so that they do not use the upper-ASCII text from IBM-PC ASCII.

The good news is...

In Mystic everything that is displayed to the user is configurable, and you can create an unlimited number of "themes" all of which have their own unique prompts, menus, and display files. It can also do 40 column themes, although I never saw someone actually attempt it so it might be buggy...

The bad news is...

The possibility is there, but it might take a bit of work on your side to change the display text around so that it uses characters and lengths that
will work with those computers.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

Hi,

I've manually removed all the ansi codes in menus but i still get them
only at the start of each line. It is something hardcoded in Mystic i suppose (or a bug?)...

I had a chance to take a look at it. It was a bug and its been fixed. Mystic in Unix was defaulting to ANSI prior to the graphics prompt.

The fix will be in the next pre-alpha build which hopefully will be out

today,

but if not, it will be out on the weekend at the latest.

Thank you!
Where i can download it?

Bruno

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.g00r00@f215.n129.z1.binkp.net

Thank you!
Where i can download it?

www.mysticbbs.com/downloads/prealpha

This is where daily builds are, but keep in mind there are unfinished
features and other things may be broken as there are work in progress.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

On Tuesday, December 12, 2017 at 1:49:49 PM UTC-5, bruno....@gmail.com wrote:

Hi,

i'm setting up a bbs using Mystic BBS software but i've encountered a problem that i can't solve: is there a way to configure it for text

only

terminals? I'm using a Sinclair Spectrum to connect but i always got characters that are not interpreted by the (real simple) terminal program. My focus is a bbs for computers such as Commodore 64, MSX,

etc.

etc. and they don't have ansi-bbs...

Should be able to. Just use all straight .asc files in the TEXT folder,

have

the BBS set to detect the codepage and emulation.

Tried, but i still get ansi characters:

(U [8;25;80t [1;25r [1;1H [2J [1;1H [1;1H [2J [1;1HMystic BBS v1.12 A35 for

Linux Node 1

[2;1HCopyright (C) 1997-2017 By James Coyle
[3;1H
[4;1H(0) Ascii (No Color)
[5;1H(1) Ansi (Color)
[6;1H
[7;1HGraphics Mode -> 0
[8;1H
[9;1H[0] MS-DOS CP437
[10;1H[1] UTF-8
[11;1H
[12;1HSelect Terminal Codepage [Enter = CP437]: 1
[13;1H
[14;1HAvailable themes:
[15;1H
[16;1H 1 ..... HAL's theme
[17;1H 2 ..... Default
[18;1H
[19;1HSelect your theme [Enter/Default]: 1
[20;1H
[21;1H
[22;1H ==================================

As you can see at the very start of each line i got unexpected characters.

How i can avoid this behaviour?

Thanks,
Bruno

Can someone provide an EXAMPLE of say the prelogin.mnu configured as an ASCII prelogin TEXT menu. I do have mystic setup anormat BBSd running but I just want
a plain old retro ascii BBS and this package just aint cutting it.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.gallaxial@f206.n249.z1.binkp.net

Can someone provide an EXAMPLE of say the prelogin.mnu configured as an ASCII prelogin TEXT menu. I do have mystic setup anormat BBSd running
but I just want a plain old retro ascii BBS and this package just aint cutting it.

I found 2 way to do it ,
EveryThing Files With *HDR.ASC
Your Can use Only Text

or remove the Ansi Choice
But the BBS ASK at the Beginning ....

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)