Is it a buf of timeseal?

[Water]

Geschrieben von:/Posted by: Water at 11. June 2004 10:57:

I have built a chess server.
If the message sent by server contain non-ascii characters, my winboard displays them error.
for example:
Server send a line "aaa XXX". (aaa is ascii character string, and XXX is non-ascii character string like Chinese, Japanese and so on).
But on Winboard window, it display "XXX aaa".
Why?
I use timeseal alone like "timeseal HOST PORT" in a command line, it gets the same result.
So i guess that timeseal has a bug.
How do I?
How to get a newer timeseal.exe (my version is 1.0, and size is 48640 bytes. Is it the newest?)
Thanks!

[Fabien Letouzey]

Geschrieben von:/Posted by: Fabien Letouzey at 11 June 2004 13:41:15:
Als Antwort auf:/In reply to: Is it a buf of timeseal? geschrieben von:/posted by: Water at 11. June 2004 10:57:


Hi,
Please put your real name while posting.

Server send a line "aaa XXX". (aaa is ascii character string, and XXX is non-ascii character string like Chinese, Japanese and so on).
But on Winboard window, it display "XXX aaa".

Does "telnet" work fine with your server?
A potential problem to look at is the use of the byte FF (255 = IAC). The telnet protocol uses FF for special commands and guenuine FF bytes must be encoded/decoded (e.g. when sending a normal FF, the server should output "FF FF").
Another (more likely) possibility is the end-of-line encoding. A telnet server should use CRLF (as in DOS/Windows text files), but I remember LFCR issues with timeseal. Try different combinations.
Fabien.

[Rahman Paidar]

Geschrieben von:/Posted by: Rahman Paidar at 11. June 2004 15:27:
Als Antwort auf:/In reply to: Re: Is it a bug of timeseal? geschrieben von:/posted by: Fabien Letouzey at 11 June 2004 13:41:15:

Hi,
Please put your real name while posting.

Server send a line "aaa XXX". (aaa is ascii character string, and XXX is non-ascii character string like Chinese, Japanese and so on).
But on Winboard window, it display "XXX aaa".

Does "telnet" work fine with your server?
A potential problem to look at is the use of the byte FF (255 = IAC). The telnet protocol uses FF for special commands and guenuine FF bytes must be encoded/decoded (e.g. when sending a normal FF, the server should output "FF FF").
Another (more likely) possibility is the end-of-line encoding. A telnet server should use CRLF (as in DOS/Windows text files), but I remember LFCR issues with timeseal. Try different combinations.
Fabien.

Maybe the problem is the type of stack that is used for communication.
FIFO (first-in first-out) stacks act like this.
Rahman