BS> BTW Do you know what that  issue about MaxEd there 
 BS> is listed in TODO is about? I've been writing several 
 BS> messages using fullscreen editor in Maximus with no 
 BS> problems.

 BJ> Hmmmm....   issue?  You mean the one about  to 
 BJ> be accepted as  pair?  Based on what I'm seeing 
 BJ> in the TODO file, I'm sure that was a note by Wes to 
 BJ> support Unix style end of lines along with DOS based end of lines.....  

Hmm, No afaik is maximus doing the job fine about only setting a Carrige
Return by every new line, in the message...

So I really don't see there is a issue..

 BS> [Our _dear_ filetransfer problem]

 BS> Not I don't believe it's the core of maximus, more the 
 BS> comdll, but It's definately a problem related to 
 BS> maximus, because the telnet clients I've used for 
 BS> testing is working very greate with other Telnet based 
 BS> boards.

 BS> The client is doing binary, but I the "server" does.. (Maximus)..

 BJ> Both ends should be doing binary, 8 bit clear channels. 

Exactly, should the "server" push the client into binary. So
afaik is the session working in ASCII until it needs to send/recieve files,
it go into binary or did I misunderstood something?

 BS> Maybe the "server" doesn't, it was what I was trying to write ;)

 BJ> Ok.  And I would not be suprised about that.  If you 
 BJ> are seeing double of characters on the receiving end, 
 BJ> that can also be a different problem (local echo turned 
 BJ> on in the telnet client, as well as Max providing 
 BJ> echo)....  But that wouldn't be a CRC problem for the 
 BJ> (binary) file upload and downloads....

Hmm.. Maybe the CRC tab is wrong or so.. I really can't do anything more,
I've used 2 days of my holiday about find a solution.. But with no luck.
And it such problems we need to handle before doing anything else.

 BJ>  Binary on a 7-bit channel will have problems.....  I'm 
 BJ> not sure what the telnet client does for binary with a 
 BJ> 7-bit channel, but I suspect it uses a flag character, 
 BJ> like the old CDC exted 6/12 bit character code.

 BS> Indeed, it'll.. 

 BJ> I'm expecting to find that we didn't set a flag (or a 
 BJ> set of flags) for IOCTL on the TCP/IP session that is 
 BJ> causing either character interpretation, 7 bit (vs 8 
 BJ> bit clear) channel, or something similar.  

Okay. I don't know mutch about telnet, so it might be therefore I couldn't
find the situation.

 BJ> I may have to dig out an old program that allows one to 
 BJ> hook a TCP/IP port for testing.  It's been years since 
 BJ> I've played at this level.

Oh okay, enjoy :)

Regards,
Bo


--- Maximus/UNIX 3.03b