Thank you ducasp!
I just tested the new version (how nice is HUB UPGRADE TELNET!). Great to see the cursor on the screen and the keys working correctly! However something weird happens: when the BBS loads the editor, the MSX sends an abort request and it is immediately closed. That was not happening in the previous release, so something must have been changed.
You can see what I am talking about here:
Thank you ducasp!
I just tested the new version (how nice is HUB UPGRADE TELNET!). Great to see the cursor on the screen and the keys working correctly! However something weird happens: when the BBS loads the editor, the MSX sends an abort request and it is immediately closed. That was not happening in the previous release, so something must have been changed.
You can see what I am talking about here:
That's weird, the Client itself has changed just two things, the received buffer size and location so it won't interfere with the larger size of the latest ansi-drv and what it sends when an arrow key is pressed... Obviously something is wrong, just that something that could cause it doesn't come to my mind :P I'll check it this weekend, thanks for testing and reporting it, for me the editor that appeared is not the same you used, probably why it worked on my video.... oO
By the way, I am curious, how it is possible to the client to work in MSX1? It only has 40 columns and SCREEN 2 is tiled.
It will be a dumb terminal, no ANSI escape code rendering, just use screen 0 and msx dos calls to write to screen . If using an 80 column card and setting screen to 80 columns before calling the client, it will work with 80 columns as well (I've tested the routines for screen detection / initialization on OpenMSX using Gradiente 80 Columns card) , otherwise, 40 columns. Not a great experience, but it is usable and a faster and more complete alternative to TCPCON. 
It will be a dumb terminal, no ANSI escape code rendering, just use screen 0 and msx dos calls to write to screen . If using an 80 column card and setting screen to 80 columns before calling the client, it will work with 80 columns as well (I've tested the routines for screen detection / initialization on OpenMSX using Gradiente 80 Columns card) , otherwise, 40 columns. Not a great experience, but it is usable and a faster and more complete alternative to TCPCON.
That's way better than a MSX1 had until now
Yesterday I was talking with a friend who managed to also connect his ZX Spectrum to the BBS, I was pretty surprised it was able to display the 80 columns and most of the colors. They must be using the tiles to redefine the ANSI chars and colors, but they avoid attribute clash quite well:
Probably a MSX1 can do better :P (this is NOT a feature request)
Thanks to you for the great work you put in the client And about MSX1, I was just being curious, it was not a feature request. I don’t think there are many MSX1 ethernet users out there
