Subj : Solved issue with SyncTerm after up/download on my BBS
To   : Digital Man
From : AKAcastor
Date : Wed Apr 24 2024 05:49 pm

 DM> I looked at the SyncTERM source and determined that though it attempted 
 DM> to track and restore the binary mode of the Telnet 
 DM> connection, it didn't take into account the server 
 DM> initiated commands for setting BINARY TX mode (in 
 DM> either direction). I committed a fix for that. If you 
 DM> have a chance and want to try it out, it's in Git and 
 DM> now and should be in nightly builds (e.g. for Windows, 
 DM> MacOS) within 24 hours. Let me know if you do try it 
 DM> and what you discover. I expect it'll resolve this 
 DM> issue.

Thanks for that.  I haven't had a chance to try it out yet but will take a look.

I did spend a bit more time on the DOSBox-X softmodem telnet implementation, I found that my hacky approach to forcing binary mode was in some cases (Netrunner) causing an IAC command loop.  So I cleaned up the tracking of telnet state and now don't send IAC WILL in response to an IAC DO if it didn't cause a state change.

I haven't properly implemented ASCII mode yet - I have some more questions.  In ASCII mode I understand a raw CR is sent as CR/NULL (or CR/LF in case of a newline). So any CR should be translated to CR/NULL and then from CR/NULL back to CR at the other end (or however that end chooses to interpret it), correct?

Other than CR (and sequences starting with the IAC character 0xFF) are there any other characters or sequences that either need to be escaped or can't be passed via ASCII mode telnet?  I'm not sure if I'm still missing other things.


Chris/akacastor

--- Maximus 3.01
 * Origin: Another Millennium - Canada - another.tel (21:1/162)

.