Ok I tried a number of other things, but there is still some sort of nagging "Carriage Return" problem that I cannot solve.
Is it possible that there is some issue not yet identified for incoming data to the WiModem232 related to the carriage return and how it is being passed to the serial port?
I have tried different ansi drivers, different fossil drivers, reconfiguring the applications, reconfiguring the BBS software, adjusting line width. I also tried a different telnet client, and it does the same thing. Everything points to a problem with how "Enter" is behaving when being translated. A period "." seems to be getting passed to the serial port on along with carriage return. It doesn't happen when I do carriage returns from the bbs host system while the client is connected.
Thoughts?
Is it possible that there is some issue not yet identified for incoming data to the WiModem232 related to the carriage return and how it is being passed to the serial port?
I have tried different ansi drivers, different fossil drivers, reconfiguring the applications, reconfiguring the BBS software, adjusting line width. I also tried a different telnet client, and it does the same thing. Everything points to a problem with how "Enter" is behaving when being translated. A period "." seems to be getting passed to the serial port on along with carriage return. It doesn't happen when I do carriage returns from the bbs host system while the client is connected.
Thoughts?