toreshift.blogg.se

Syncterm on wondows crashes c64 mode
Syncterm on wondows crashes c64 mode











TCP packet sent from Hyperterminal to UDS. I captured a few more packets below to show what happens with the UDS telnet mode enabled and disabled.ĭisconnect mode 0xC0 (telnet mode enabled) I could duplicate this function in the BBS but I don't see how it would be any different than the UDS. It seems the Lantronix UDS-10 is doing what is expected by escaping the 0xFF character, leading to successful transfers (in some cases). If the 0xFF character is the problem, I'm confused as to how the others BBSs and terminal emulators are handling it. Qodem goes a bit further, using the Echo, Suppress Go Ahead, and transmit binary options. Netrunner terminal also uses the Suppress Go Ahead option. (3) the escape sequence results matched your post #78, in that for every two 0xFF sent by the BBS, only one was displayed.Įdit: what I found regarding the suppress go ahead

syncterm on wondows crashes c64 mode

(2) the DOS telnet client echoed locally I was able to send a fffb01 sequence (from the BBS) to turn this off (1) I see no telnet commands in the data stream When I turned off the UDS Telnet mode option: I did not see any other telnet commands in the data stream. In response from Hyperterminal to UDS (and dos telnet) (PC->9640) With the UDS Telnet mode option set, here is what I am seeing in the first few packets:įrom UDS to Hyperterminal (and DOS telnet): (port 9640->PC) I had a few minutes to poke around with Ethereal. (This configuration caused some trouble for people in the past so for now I have re-enabled telnet negotiation). In the gameroom is a Telnet test program that shows every other successive 0xFF byte is being gobbled by either Hyperterminal or the UDS, when the UDS telnet negotiation is turned off. If I turn the negotiation off, transfers fail with short packets. With the UDS set to negotiate the Telnet terminal type, file transfers work properly.

syncterm on wondows crashes c64 mode

I'll circle back to this thread in the morning after I catch some shut-eye.Įdit: I did a quick test by connecting to Heatwave with Hyperterminal. This is where Shift838 and I got a bit twisted up in our testing as we tried to find a solution that would work with all devices. So if there is some escaping, it is being managed by the UDS. I also wonder what would happen if you turn on the telnet escaping on your end?įor reference, the BBS sends and receives data to/from the RS232 without any byte manipulation or escaping. I could temporarly turn off the UDS Telnet mode setting if you'd like to try testing that sometime. The Lantronix UDS device connected to Heatwave is set with Telnet enabled, which could mean the UDS device is trying to negotiate with the WiModem232 behind the scenes and/or enables the escaping based on its response or lack thereof.

syncterm on wondows crashes c64 mode

One of us might still have our testing logs - I'll take a look for them this weekend. Shift838 and I spent some time earlier this year testing various configurations and settings with the Lantronix UDS-10 device, wifi232 device, and tcpser (serial to IP emulation). I must confess that I am no Telnet guru myself. Thank you, Jim, I appreciate your looking into this.













Syncterm on wondows crashes c64 mode