When you first added the commands to mystic for -ansi and -text it worked on the two 64 bit systems I tried it on. I added a DD ./mystic -ansi and -text
to my experimental directories and it worked fine on A37.
Just upgraded this one to A38 and got the usual UTF-8 weird characters when bringing up the ansi editor with DD ./mystic -ansi under mystic. Will have to look in to the configuration settings and see if they are different from the A37 one when I first tried the -ansi that worked well. So that might need to look at the configuration settings or have it's own. Found the same for
-text. When I just do ./mystic -ansi in mystic root however it works just
fine. Did update the three cfgroot1.ans, cfgroot2.ans, cfgroot3.ans files in data, not sure if it has any relation. For now we need to stick to doing it from mystic root where it seems to work fine.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Workpoint (21:1/145.3)

When you first added the commands to mystic for -ansi and -text it
worked on the two 64 bit systems I tried it on. I added a DD ./mystic -ansi and -text to my experimental directories and it worked fine on A37. Just upgraded this one to A38 and got the usual UTF-8 weird characters when bringing up the ansi editor with DD ./mystic -ansi under mystic.

You are trying to run two copies of Mystic at the same time, with the same user on both of them... one in local login mode and one as a remote logged in user.

You're over-thinking this. :) If you want to use the ANSI editor as a menu option, simply use the "ANSI Editor" menu command to open the ANSI editor. It should all be covered in the WHATSNEW.

======

As far as codepage, it sounds like you have your default local codepage set to UTF8. If you don't want UTF8 then turn it off and you shouldn't get UTF8.

If you have your default user codepage set to UTF8 then you are going to see UTF8 by default whenever you login to Mystic (./mystic, telnet, ssh, etc)

If you have your default LOCAL codepage set to UTF8 then you are going to see UTF8 whenever you use Mystic as a LOCAL login. (./mystic -l, ./mystic -cfg, ./mystic -ansi, ./mystic -text are all local mode command lines).

You can also override codepage when starting up Mystic, but really none of this is a concern to your problem. All you have to do is use the menu command to open the ANSI editor and you'll be okay. :)

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)