G'day Mr. Jones,

[typing test]

 BS> OH It's only ~ 2 lines on a monitor.. I can do that on 
 BS> a minute I guess. Does it mean anything that you aren't 
 BS> using a standalized system for typing (like with all 10 fingers?).

 BJ> Actually just over two lines (at 80 characters a line). 
 BJ>  While you might get comments about a different style, 
 BJ> if you get 35 WPM with acuracy, that would qualify you 
 BJ> for the requirement.  The full time positions are in 
 BJ> the 55 to 65 WPM, which I believe I also passed (what 
 BJ> ever the lower to mid-level full time requirements 
 BJ> were).

Okay, well I can't calculate it on me, while I'm writing this message,
because english isn't my native langauge, so I gotta translate in my head
while I'm wiritng.

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


[Our _dear_ filetransfer problem]

 BS> The telnet client is doing it, like my these.. 

 BJ> Ok.  Then the problem is on the telnet client end, or 
 BJ> in how the TCP/IP connection is setup.....  So this 
 BJ> might *not* be a Maximus problem, but could be.

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

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

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

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

 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.

Indeed, it'll.. 

Regards,
Bo




--- Maximus/UNIX 3.03b