Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems when using with Striketerm / Novaterm on C64 #365

Closed
2 tasks done
sreuter opened this issue Sep 16, 2021 · 3 comments
Closed
2 tasks done

Problems when using with Striketerm / Novaterm on C64 #365

sreuter opened this issue Sep 16, 2021 · 3 comments

Comments

@sreuter
Copy link

sreuter commented Sep 16, 2021

Describe the Bug

I've setup my Enigma BBS and it works awesome with SyncTerm.

Unfortunately, whenever I try to dial in via SyncTerm (in ANSI mode) on my C64, it only renders the first screen, but then does not continue to the login. I can't press enter or anything else. It's just frozen. I've tried logging into another Enigma BBS, but with the same result.

To Reproduce
Any relevant steps to reproduce the behavior:

Try using SyncTerm or Novaterm 9.6 on a C64, set to ANSI mode and try to login into any Enigma BBS.

Expected Behavior

Session should not hang after initial screen/graphic rendered.

Actual Behavior

It gets stuck

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • I am using Node.js v12.x LTS or higher
  • npm install or yarn reports success
  • Actual Node.js version (node --version): v12.22.6
  • Operating system (uname -a on *nix systems): Linux cybney 5.4.0-80-generic ENiGMA throws a database error on first launch #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  • Revision (git rev-parse --short HEAD): 1ffbf5b
  • Any additional relevant information about your setup: I'm using a Wi232 Modem in UP9600 mode.
@NuSkooler
Copy link
Owner

@sreuter it sounds like you're having the issue with Cursor Position Reports not being supported by your client. This is a known issue that I plan on tackling hopefully in the near-ish future. You can validate by using another menu in front/in place of that doesn't use MCI codes -- if it works, that's what what you're looking at.

@NuSkooler
Copy link
Owner

See #222

@NuSkooler
Copy link
Owner

NuSkooler commented Apr 8, 2022

@sreuter This should be working now! Feel free to re-open if that didn't do the trick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants