• Configure Mystic bbs for text only terminal

    From bruno.grampa@gmail.com@3:770/3 to All on Mon Dec 11 12:44:42 2017
    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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Todd Yatzook@1:142/799 to bruno.grampa@gmail.com on Mon Dec 11 16:35:38 2017
    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.

    --- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
  • From Paul Hayton@3:770/100 to Todd Yatzook on Tue Dec 12 10:57:05 2017
    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 :)

    --- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)
  • From bruno.grampa@gmail.com@3:770/3 to All on Tue Dec 12 10:49:48 2017
    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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From g00r00@1:129/215 to bruno.grampa@gmail.com on Tue Dec 12 12:39:46 2017
    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.

    --- Mystic BBS v1.12 A37 2017/12/10 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From g00r00@1:129/215 to bruno.grampa@gmail.com on Tue Dec 12 17:11:21 2017
    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.

    --- Mystic BBS v1.12 A37 2017/12/10 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From bruno.grampa@gmail.com@3:770/3 to All on Wed Dec 13 04:16:56 2017
    Hi,

    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.

    This it the problem i have: when i select "Ascii (No Color" i still got ANSI escape characters (you can view in my example at the start of each line).

    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?)...

    Thanks,
    Bruno

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From g00r00@1:129/215 to bruno.grampa@gmail.com on Wed Dec 13 13:50:14 2017
    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.

    --- Mystic BBS v1.12 A37 2017/12/13 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From Christopher Malo@1:317/2 to g00r00 on Wed Dec 13 17:56:41 2017
    On 12/13/17, g00r00 said the following...

    I've manually removed all the ansi codes in menus but i still get the 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.

    --- Mystic BBS v1.12 A37 2017/12/13 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

    Saw it in the whatsnew.txt for today's the one just picked up. =)

    --- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
    * Origin: Twinkle BBS # (1:317/2)
  • From bruno.grampa@gmail.com@3:770/3 to All on Sun Dec 17 10:44:55 2017
    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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From g00r00@1:129/215 to bruno.grampa@gmail.com on Sun Dec 17 19:35:28 2017
    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.

    --- Mystic BBS v1.12 A37 2017/12/17 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From g00r00@3:770/3 to All on Sun Dec 17 19:35:28 2017
    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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From winston.xoom@gmail.com@3:770/3 to bruno....@gmail.com on Mon Oct 15 14:37:19 2018
    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: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From gallaxial@1:249/206 to winston.xoom@gmail.com on Sat Oct 20 22:45:18 2018
    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 ....

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: SpaceSST (1:249/206)