Octocontrabass wrote:
kerravon wrote:
Your telnet is unlikely to understand EBCDIC,
PuTTY does, if you pick an EBCDIC code page. It doesn't seem to work very well. I'm not sure if that's because PuTTY doesn't really support EBCDIC, or because I chose the wrong EBCDIC code page, or because PuTTY is a bit smarter than your average ANSI terminal.
Cool. I think the output will work with any EBCDIC code page, but the one that I actually support is 1047, especially noticeable when it comes to square brackets (x'AD' and x'BD').
Quote:
kerravon wrote:
It is character-based, so you shouldn't need to hit enter.
This might just be PuTTY again, but it won't accept input unless I press enter.
It only sometimes tells me whether or not I input a number. Is it supposed to tell me every time?
It is supposed to tell you every time, and it used to be behaving properly before I switched to EBCDIC so can no longer easily test. It may be Putty not switching to character mode because there is no Telnet negotiation done (I switched that off, as I want it to work with a "dumb terminal").
Anyway, thanks for trying it! The problem may not be Putty, it may be my end. It is more a "proof of concept". I'm not sure any of this EBCDIC software (like your Putty) has ever really been exercised. I'm not sure anyone is expecting to receive EBCDIC ANSI. I'm not sure anyone else actually produces that either.
I need to carefully check the current behavior of my BBS and start correcting things. I had to put in some hacks to get it to work at all. E.g. you shouldn't need to be the person who types first. I expected the BBS to display something first. There's probably a line in Hercules/380 I failed to comment out after commenting out the telnet negotiation, so now the first thing it does is a useless read or something.
Actually, I might try using Putty myself. I used it years ago for something.