BJ> In the US, for typing tests, 35 WPM (words per minute) is defined as 
 BJ> 5 characters per word, so that is 175 characters a minute.  If I 
 BJ> remember correct, the test is (usually) 5 minutes, and 35 WPM is 
 BJ> about 1/2 page of type written text when double 
 BS> spaced on standard US 
 BJ> letter paper, with standard margins on a (10? 12? CPI) standard 
 BJ> typewritter....  The test was taken on a PC (in a Word window), but 
 BJ> the source of the text for the test was typed up 
 BS> on a type writer.... 
 BJ>  And on a test like this, each typing mistake stubtracts 1 WPM from 
 BJ> your gross score for your  (normalized?) score.  
 BJ> It is that adjusted score that you have to have above 35 WPM in this 
 BJ> case....

 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?).

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

 BJ> Byte stuffing?  What is performing the byte stuffing?  The telnet 
 BJ> client the user is using?  If so, that is where 
 BJ> the problem is.  Yes, 
 BJ> packet sizes have to be stuffed to meet a minimum packet link for 
 BJ> sending over the TCP/IP connection, but that should be transparently 
 BJ> deleted before the application (Maximus) sees the stream.....  I'm 
 BJ> not understanding where the source of the double 
 BJ> chracters is comming 
 BJ> from.  

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

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

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

Both ends should be doing binary, 8 bit clear channels.  Binary on a 7-bit
channel will have problems.....  I'm not sure what the telnet client does
for binary with a 7-bit channel, but I suspect it uses a flag character,
like the old CDC exted 6/12 bit character code.

Take care......

Bob Jones, 1:343/41



--- Maximus/2 3.01