ME> Another possibility is that EleBBS could be sending out an ASCII
 ME> character
 ME> # 255 (0FFh) by mistake, which is the start of a telnet command.
 ME> Depending
 ME> on what characters follow, this could be causing some telnet
 ME> clients to
 ME> misbehave, but not others.  This would not have any effect on local
 ME> mode or
 ME> modem connections.

Well... it seems that some people have the problem with different clients,
and others don;t with the exact same clients... I'm absolutely no expert on
these things, but being as how XP had the wrong ANSI registries and it
required a fix to make the colors right, I think it -could- be something XP
is reading and misinterpreting even with the fix applied.

I know myself and the other two locals here are using XP and it happened...
What Mike ROberts is using, I don't know (Mike?)...

Those who -never- had the problems, what OS's are you guys using... I think
it could be an XP thing (???) ... seems MicroShaft likes to make anything
DOS harder and harder with each release, and even though this is happening
with Win32 EleBBS I would bet MS views ANSI in as much regard as they do
anything DOS... they have been continuously trying to kill the "old
school" stuff without making it "obvious" IMO.

 ME> If someone has a BBS up which causes the issue, I could log on
 ME> using a
 ME> tool that captures data in binary mode, so we can isolate the
 ME> cause.

 ME> It could be something as simple as an unwanted 0FFh in one of the
 ME> language
 ME> file prompts.

Well... just checked and it looks like Rick is rebuilding his BBS again,
and he hasn't put the external headers in yet...

telnet://dept47.dtdns.net

Note that when at the blank screen you can use the prompt keys... I back
out with "S" every time rather than just disconnect from the BBS.

Phil

--- FMail/Win32 1.60
Netwo (1:267/169)