• Mystic 1.12a43 pause on connect

    From Digital Avatar@46:1/145 to All on Saturday, September 21, 2019 19:58:36
    So I've noticed an obnoxious bug with Mystic 1.12a43 on RPi ... on connecting there's roughly a 4 second delay before preuser.ans is triggered. I'm
    wondering if this is a regression of a similar bug that appeared in the 1.10 series that involved some cockup with ANSI autodetection? I set Ask Emulation to force ANSI on the idea that was the case but it had no effect. Any ideas?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (46:1/145)
  • From maskreet@46:1/148 to Digital Avatar on Sunday, September 22, 2019 00:50:34
    On 21 Sep 2019, Digital Avatar said the following...

    So I've noticed an obnoxious bug with Mystic 1.12a43 on RPi ... on connecting there's roughly a 4 second delay before preuser.ans is triggered. I'm wondering if this is a regression of a similar bug that appeared in the 1.10 series that involved some cockup with ANSI autodetection? I set Ask Emulation to force ANSI on the idea that was
    the case but it had no effect. Any ideas?

    That doesn't sound like any issue I had on mine when I was running it on a
    Pi. Sure, it was a tad slower than on a VM or other more powerful systems,
    but yeah, never saw that on mine. Might be the model you're using? Or maybe something with the hardware?

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (46:1/148)
  • From Digital Avatar@46:1/145 to maskreet on Sunday, September 22, 2019 07:06:55
    on 22 Sep 2019, maskreet said...

    That doesn't sound like any issue I had on mine when I was running it on
    a Pi. Sure, it was a tad slower than on a VM or other more powerful systems, but yeah, never saw that on mine. Might be the model you're using? Or maybe something with the hardware?

    It's a brand new RPi4.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (46:1/145)
  • From maskreet@46:1/148 to Digital Avatar on Sunday, September 22, 2019 14:32:31
    On 22 Sep 2019, Digital Avatar said the following...

    on 22 Sep 2019, maskreet said...

    That doesn't sound like any issue I had on mine when I was running it a Pi. Sure, it was a tad slower than on a VM or other more powerful systems, but yeah, never saw that on mine. Might be the model you're using? Or maybe something with the hardware?

    It's a brand new RPi4.

    Oof, I don't know then. Is it just the initial screen, but everything else
    runs fine?

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (46:1/148)
  • From Digital Avatar@46:1/145 to maskreet on Sunday, September 22, 2019 21:22:37
    on 22 Sep 2019, maskreet said...

    On 22 Sep 2019, Digital Avatar said the following...

    on 22 Sep 2019, maskreet said...

    That doesn't sound like any issue I had on mine when I was runni a Pi. Sure, it was a tad slower than on a VM or other more power systems, but yeah, never saw that on mine. Might be the model yo using? Or maybe something with the hardware?

    It's a brand new RPi4.

    Oof, I don't know then. Is it just the initial screen, but everything
    else runs fine?

    Yes. As soon as I connect to the server it pauses for like 4 seconds, and thereafter everything is fine. I tried fiddling with the settings for Code
    Page and Terminal Emulation auto-detect but I got nowhere.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (46:1/145)
  • From maskreet@46:1/148 to Digital Avatar on Monday, September 23, 2019 10:33:09
    On 22 Sep 2019, Digital Avatar said the following...

    Oof, I don't know then. Is it just the initial screen, but everything else runs fine?

    Yes. As soon as I connect to the server it pauses for like 4 seconds, and thereafter everything is fine. I tried fiddling with the settings for
    Code Page and Terminal Emulation auto-detect but I got nowhere.

    When you connect, does it show the Mystic version immediately, or does that take four seconds to show as well? I figure if that shows immediately and
    then first ansi shows four seconds later, then it's a Mystic thing. If it's
    the former, then it might just be something with the OS performing a connection.

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (46:1/148)
  • From Digital Avatar@46:1/145 to maskreet on Monday, September 23, 2019 21:33:21
    on 23 Sep 2019, maskreet said...

    When you connect, does it show the Mystic version immediately, or does that take four seconds to show as well? I figure if that shows
    immediately and then first ansi shows four seconds later, then it's a Mystic thing. If it's the former, then it might just be something with
    the OS performing a connection.

    No, when I connect the Mystic version string doesn't print until ~4 seconds after connect. Likewise, the entry in MIS's message log signaling a
    connection doesn't appear until that time. I used linux's telnet client to verify this wasn't a Syncterm thing. When I connect with the telnet command
    my connection is established immediately, but MIS doesn't log it, nor do I
    get any text, until after 4 seconds... so it's pretty clearly a Mystic thing.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (46:1/145)
  • From maskreet@46:1/148 to Digital Avatar on Tuesday, September 24, 2019 01:22:57
    On 23 Sep 2019, Digital Avatar said the following...

    No, when I connect the Mystic version string doesn't print until ~4 seconds after connect. Likewise, the entry in MIS's message log
    signaling a connection doesn't appear until that time. I used linux's telnet client to verify this wasn't a Syncterm thing. When I connect
    with the telnet command my connection is established immediately, but
    MIS doesn't log it, nor do I get any text, until after 4 seconds... so it's pretty clearly a Mystic thing.

    Sounds like it. I honestly don't know what the issue would be. Have you tried another BBS package to see if it's specifically Mystic?

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (46:1/148)
  • From Digital Avatar@46:1/145 to maskreet on Tuesday, September 24, 2019 21:21:45
    on 24 Sep 2019, maskreet said...

    Sounds like it. I honestly don't know what the issue would be. Have you tried another BBS package to see if it's specifically Mystic?

    No, but i suppose i can try throwing synchronet on there this weekend and
    start debugging this issue.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (46:1/145)
  • From maskreet@46:1/148 to Digital Avatar on Wednesday, September 25, 2019 11:51:59
    On 24 Sep 2019, Digital Avatar said the following...

    on 24 Sep 2019, maskreet said...

    Sounds like it. I honestly don't know what the issue would be. Have y tried another BBS package to see if it's specifically Mystic?

    No, but i suppose i can try throwing synchronet on there this weekend and start debugging this issue.

    Yeah, that'd be something I'd try just to help narrow down what might be the issue. If the same thing happens it might just be something with the
    hardware, or OS.

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (46:1/148)