1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • ANSI parsing of arrow keys via Telnet

    From Pepper@21:1/187 to All on Friday, February 09, 2018 19:47:38
    I'm having an issue with my old IBM Model25 using a WIFI232 to emulate the Hayes modem. When I connect to a Mystic BBS all the commands work (as far as
    I can tell) apart from the UP/DOWN keys.
    When you browse the messages and you use the arrow keys to go up and down through the different areas, as soon as you press the key the BBS jumps back
    to the main messages menu.
    As UP is Esc[A] and Down is Esc[B] is it possible that Mystic is acting on
    the Esc and not waiting for the second part?
    I have tried Bannacom & Telix to connect, so I don't think it's client related.... It seems related to the fact that the WIFI232 is emulating the Hayes modem.
    Other non Mystic BBS's don't seem to exhibit the issue.
    Any thoughts I'd appreciate it??

    -=Pepper=-

    --- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
    * Origin: Cosmik Debris BBS | Little Falls,NY (21:1/187)
  • From NuSkooler@21:1/121 to Pepper on Friday, February 09, 2018 19:47:01

    On Friday, February 9th Pepper muttered...
    Any thoughts I'd appreciate it??

    g00r00 will probably have to answer for sure, but are you positive this isn't terminal related? The terminal is what sends the keystrokes, the modem ("real" or not) is just a data transport. It's possible that at lower baud rates the keystroke is being split as you said though, e.g. packet : ESC, packet 2: [A.


    --- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 8.9.4)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From Beery@21:4/109 to Pepper on Saturday, February 10, 2018 11:56:32
    I have a WiModem232 and have no problem connecting to my bbs running under Mystic. I did have to use two command, the AT&K0 and the AT*T1 commands to
    get everything right.

    Is the developer of the WiFi232 modem still updating the firmware? I've got a friend with one, and he was testing it out and did identify some issues that were with it and the WiModem232 as I think they used the same or similar code base. The developer of the WiModem232 updated the firmware. Not sure what is happening with the WiFi232.

    Beery

    --Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
    * Origin: 9640 News BBS (21:4/109)
  • From Pepper@21:1/187 to Beery on Saturday, February 10, 2018 13:20:04
    On 02/10/18, Beery said the following...
    under Mystic. I did have to use two command, the AT&K0 and the AT*T1 commands to get everything right.

    I'll have a look at those and see if it makes a difference.

    Is the developer of the WiFi232 modem still updating the firmware? I've

    Yes he's still updating, I downloaded new firmware the other day.

    -=Pepper=-

    --- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
    * Origin: Cosmik Debris BBS | Little Falls,NY (21:1/187)
  • From Pepper@21:1/187 to Beery on Saturday, February 10, 2018 17:27:38
    On 02/10/18, Beery said the following...
    under Mystic. I did have to use two command, the AT&K0 and the AT*T1

    I changed the setting to reflect Telnet and no difference. After some
    Googling I found this mention for Mystic and another Terminal Emulator .. Unfortunately I can't test this one as I don't think it'll run on Win3.0..lol It seems to mention the same issue... https://github.com/klamonte/qodem/issues/65

    -=Pepper=-

    --- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
    * Origin: Cosmik Debris BBS | Little Falls,NY (21:1/187)