Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,258 of 4,255    |
|    mutazilah@gmail.com to Joe Monk    |
|    Re: ATDE    |
|    15 Jun 21 03:42:46    |
      From: muta...@gmail.com              On Tuesday, June 15, 2021 at 8:13:43 PM UTC+10, Joe Monk wrote:              > > For what reason does telnet support EBCDIC? Who        > > else is emitting EBCDIC and what does the data        > > stream look like?              > On my macOS shell (terminal app), I can set the code page to Western (EBCDIC       latin 1), which as I understand it is code page 037.              Ok, cool.              > I connect (in ASCII to kerravon.mooo.com port 64000). Then I change the code       page to the above. Pressing ENTER does nothing, so I type a "?", which gives       me:               If ENTER does nothing, try it again. The BBS should react       to that and complain. Unless nothing is being sent.              > …"Welcome to the Ten Minute Limit BBS…Back in action 24 years after a       fascist kicked me off Fidonet…brought to you in glorious EBCDIC…enter an       option below:…1. Message area (not yet implemented)…2. File area (not yet       implemented)…3. The        highest quality porn ever produced (coming soon)"        >        > When I press a single character, it just sits there, and does nothing.When I       type a "1" followed by the ENTER key, it gives me:        >        > "You entered an invalid option! (hex 71)…it wasn't even a digit!!!…              Ok, I'm thinking the Mac software is stripping the high bit, and       at some point it did actually generate a hex F1.              I doubt that it is my end that is stripping it.              > (coming soon)…ÝJYou              That funny "Y" character is probably the ESC. It's not       interpreting the ANSI escape sequence, ESC [ 2 J       It will have never been exposed to that before I think.       Although I don't know how IBM USS or whatever it is       called manages to run emacs and vi. Don't they send       ANSI control characters to drive a terminal? They're       running in an EBCDIC environment - what choice do       they have?              Note that you can see the BBS software here, it's not       that complicated:              https://sourceforge.net/p/pdos/gitcode/ci/master/tree/s370/bbs.c              Ah, actually - the "Y" is probably "[". If you're using 037       instead of 1047, the "[", which is sent as x'AD', will not       be translated correctly. Even if the Mac recognized       EBCDIC ANSI escape sequences.              > entered an invalid option! (hex 0A)              And this looks like an ASCII newline that was never translated       to EBCDIC. It should have been converted to one of LF x'25',       CR x'0D', NL x'15'. It is only the last one that is used anywhere       in my software.              So it sounds like multiple issues.              Very interesting!!! Thanks for doing that test. ASCII and       EBCDIC colliding.              BFN. Paul.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca