So, I connected fine with the nightly build, but when I started poking a bit trying to reproduce the crash, the BBS started disconnecting me instantly (still no crash in SyncTERM).
I'll try the Windows release build next once I can connect again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I emailed you a syncterm error log file from the event viewer to the email address you gave me on my board. Assuming it didn't have a typo, look in your junk folder.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, about all I got out of the event log was that it was an invalid memory access... I've fixed a few potential causes, but I don't have high confidence yet that I fixed the one you're seeing since I still haven't managed to reproduce it.
I would appreciate if you could try the latest nightly again and let me know if it's solved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This problem has been around at least since 1.3... I just never use syncterm, sorry! My users do.
So, I connected fine with the nightly build, but when I started poking a bit trying to reproduce the crash, the BBS started disconnecting me instantly (still no crash in SyncTERM).
I'll try the Windows release build next once I can connect again.
Yeah, looks like I'm being blocked, presumably because I connected without authenticating "too many" times.
Telnet mostly works fine though it appears.
You're white listed. I was doing some vm maintenance when you were testing, sorry. I shouldn't be taking it down for a while.
To update this ticket...
This seems to be system-specific (always happens on some systems, never happens on others). Still no solid theories.
I emailed you a syncterm error log file from the event viewer to the email address you gave me on my board. Assuming it didn't have a typo, look in your junk folder.
So, about all I got out of the event log was that it was an invalid memory access... I've fixed a few potential causes, but I don't have high confidence yet that I fixed the one you're seeing since I still haven't managed to reproduce it.
I would appreciate if you could try the latest nightly again and let me know if it's solved.