Anyone using this on Linux as a WFC screen? When I go to log into the BBS by using the space bar and built in terminal the ANSI is all messed up -
thinking it might be a codepage thing but I am not sure how to change it. I have no issues when logging in locally by running mystic -l or telnetting
from putty. Just does it on the nodespy window. It would be nice to get
that working so I don't have to use a separate terminal to telnet into the board.

Any ideas?

Thx
-flynn

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

On 06/17/18, Flynn pondered and said...

up - thinking it might be a codepage thing but I am not sure how to
change it. I have no issues when logging in locally by running mystic
-l or telnetting from putty. Just does it on the nodespy window. It

You want to head to mystic -cfg > configuration > general settings > local
code page and set this to the opposite of what you have now, you'll probably want it on UTF8 :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

You want to head to mystic -cfg > configuration > general settings >
local code page and set this to the opposite of what you have now,
you'll probably want it on UTF8 :)

Already is/was on UTF8. I'm connected to the box running the board via Putty from my Linux desktop. Putty is on SSH and is configured for UTF8 as well. What is odd though is if I just run mystic -l everything displays and
operates perfect. It's just nodespy. Maybe I'll try a CP437 setup and see
if it works.

BTW the reason I'm using putty instead of just the in-built terminal is
because I can easily control things like the remote character set which there are also more options than in my linux terminal.

Thx
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

On 06/18/18, Flynn pondered and said...

displays and operates perfect. It's just nodespy. Maybe I'll try a
CP437 setup and see if it works.

I expect it will :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I expect it will :)

Nope actually same results as with UTF-8 .. everything else works fine and displays fine but Nodespy will not when I log into the board. The nodespy screen itself looks good with all the stats and info but as soon as I attempt to log into the board with space bar it's all messed up. Must be a problem with the nodespy terminal program.

Thx
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

On 06/18/18, Flynn pondered and said...

Nope actually same results as with UTF-8 .. everything else works fine
and displays fine but Nodespy will not when I log into the board. The nodespy screen itself looks good with all the stats and info but as soon as I attempt to log into the board with space bar it's all messed up. Must be a problem with the nodespy terminal program.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

Nodespy does work, it's the combination of settings between mystic and putty that is causing your problems - I used to have all kinds of odd stuff due to that. While putty gives you control it can be too much. First your on a Pi which pretty much handles CP437 with Raspbian Jesse. Also I suspect your logging in to the Pi via ssh, from Windows using putty. Login as Pi like
usual putty on UTF-8 so set mystic General Settings, Local Code Page to UTF8. Start nodespy and it should look normal as you said. Hit the Space & Enter
and it should still look OK, do ANSI and CP437 (Login/Matrix Default CodePage as CP437). Things should be fine. I do ASK for each of the settings on my
BBS, but it shouldn't matter. I'm setting ANSI & CP437 on the way in.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Also I suspect your logging in to the Pi via ssh, from Windows using putty. Login as Pi like usual putty on UTF-8 so set mystic General

Nope - I'm on Linux Mint (Cinnamon) desktop and I am using putty on Mint.

putty. Login as Pi like usual putty on UTF-8 so set mystic General Settings, Local Code Page to UTF8. Start nodespy and it should look

Yes, those are the settings I currently have.

normal as you said. Hit the Space & Enter and it should still look OK,

No - the ansi is all scrambled looking and even the login prompt the cursor
is to the left of the colon.

should be fine. I do ASK for each of the settings on my BBS, but it shouldn't matter. I'm setting ANSI & CP437 on the way in.

When you say "each" of the settings - I assume one is the matrix settings - what is the other one?

Thx for the help!
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

OK, time to keep it simpler then ;)
./mystic -cfg
Configuration, General Settings, Local Code Page is what controls what you
see on the system (The BBS not nodespy). Change it to get normal characters
on the BBS, it doesn't affect remote terminals (Users).
Login/Matrix Settings, Default CodePage controls what remote terminals see.
I find it's hard to detect what remote terminals see so I have it set to Ask on these so there is always a way to get it to work.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Login/Matrix Settings, Default CodePage controls what remote terminals see. I find it's hard to detect what remote terminals see so I have it
set to Ask on these so there is always a way to get it to work.

Ok I went in to those settings and set it to ask. I still get the same
results from nodespy.. very odd. I am testing this time because I'm on a different computer, from windows running putty and when I log in using
nodespy I've tried choosing both cp437 and UTF-8 and I get similar results
each time. If I just run mystic -l and select utf-8 everything looks fine.
If I telnet directly into the bbs (from remote) and select UTF-8 it works perfectly. It's only from nodespy that it's doing this. Maybe something in the version I'm running maybe changed in nodespy?

Thx
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

On 06/19/18, Flynn said the following...

looks fine. If I telnet directly into the bbs (from remote) and select UTF-8 it works perfectly. It's only from nodespy that it's doing this. Maybe something in the version I'm running maybe changed in nodespy?

OK, loaded putty under Linux and tried it, and I see what your seeing with
the defaults. Even if I change the codepage to CP437 it looks the same ;)
I'll have to experiment with it set this way to figure it out, I suspect
that "Override with UTF-8 if local says so", but will fight with it a while
and see what I can come up with as I know there should be a way to make it work. Since I have the Ask stuff set I can get in to the BBS setting up as ANSI and UTF8 and it looks fine, but nodespy is all messed up.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 06/19/18, Flynn said the following...

looks fine. If I telnet directly into the bbs (from remote) and select UTF-8 it works perfectly. It's only from nodespy that it's doing this. Maybe something in the version I'm running maybe changed in nodespy?

It's as I suspected. Change the settings (Translation) to CP437 and uncheck that 'Override with UTF-8 if local says so' and it will work fine. Then your using CP437 settings which is normal default for BBS anyway. ASCII is ASCII either way (so most command line Linux looks fine), it's the extended characters that were the issue.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

It's as I suspected. Change the settings (Translation) to CP437 and uncheck that 'Override with UTF-8 if local says so' and it will work
fine. Then your using CP437 settings which is normal default for BBS anyway. ASCII is ASCII either way (so most command line Linux looks
fine), it's the extended characters that were the issue.

I believe I tried that (I noticed the checkbox as well) but I will give it another go. I also could try CP437 under the default linux terminal (xterm
or whatever) and see if I can get it to work. Thanks for trying and testing.

Thx
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

I believe I tried that (I noticed the checkbox as well) but I will give
it another go. I also could try CP437 under the default linux terminal (xterm or whatever) and see if I can get it to work. Thanks for trying and testing.

Ok so apparently I didn't try complete cp437 ... it's working now if I have everything set to CP437 and use Putty on CP437. Now the problem is I can't
use it from my linux xterm because it apparently can't support CP437... but this is livable for what I'm wanting to do. Apparently NodeSpy doesn't
listen to the configuration settings about UTF8.

Thx
Rich

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Flynn's Arcade (21:2/102)

Is Nodespy supposed to automatically recalculate statistics throughout the
day? The reason I ask is that I had some new users today and it didn't update which I found curious. I restarted it and now the stats are correct. It does
a fine job of showing active users online without issue.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Baud BBS (21:4/113)