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

  Re: Solved issue with SyncTerm after up/download on my BBS
  By: AKAcastor to Digital Man on Wed Apr 24 2024 05:49 pm

 > 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.

Yup, that's how Telnet is: they used the same byte value for a request and an acknowledgement. Dumb design.

 > 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?

I've never really found a use case for translating ENTER to CR/NUL. But if the Telnet server receives CR/NUL *or* CR/LF (while in ASCII mode), it should treat that as a bare CR.


 > 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.

That's it.
-- 
                                            digital man (rob)

Sling Blade quote #9:
Doyle Hargraves: Morris here is a modern-day poet, kinda like in olden times.
Norco, CA WX: 61.8øF, 67.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs

.