New echo_on() function's behavior is very strange in WIN95.
Basically, user screen "freezes" after sending echo_on() until server
sends "\r\n". Text between echo_on sequence and "\r\n" is lost! :(
I tried to track this down:
/////
for(i=0;i<total;i++)
log("debug:sent:%d", (int) ((unsigned char)txt[i]));
}
if ((bytes_written = send(desc, txt, total, 0)) < 0) {
/////
If MUD server sends 3-symbol echo_on sequence "asc255,asc252,asc1"
(this string _is surely passed_ to send() function), MUD client gets
_nothing_ at all!
If MUD server sends the old 5-symbol echo_on sequence "asc255,asc252,
asc1,asc10,asc13" - MUD client receives this sequence correctly.
So I had to replace new echo_on() with the old one. :(
Is anyone else having this problem?
I think it's winsock bug. :(
Andrey
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/10/01 PDT