Hello Bob.



 ML>  When a user uploads a reply packet to the offline reader (when 
 ML> logged in via  telnet via VModem) it takes Unzip (OS/2) or 
 ML> Maximus/2 almost exactly 1 minute  to process the packet before 
 ML> the Maximus/2 menu returns to the screen.  However if a user is 
 ML> connected via dialup, it only takes a few seconds.

 ML>  Any ideas?

 BJ> I haven't tested timing, but I suspect it is related to how TCP/IP
 BJ> is trying to merge characters into a single packet.  Serial ports
 BJ> were designed for a character at a time.  TCP/IP has a minimum
 BJ> packet size that is a bit larger....  But 1 minute vs a few seconds
 BJ> shouldn't be a difference from that....  Hmmmm.... 

That would seem to be the indication except for one thing.  The
"upload" indicator on the sending program is at 100% sent and
just sits there (MTelnet).  Will try it with ZOC as well.  Looking at the
maximus log file shows the spawn of UnZip and its time lapse of almost 60
seconds on telnet uploaded .rep packets.  The same thing does NOT hold true
for uploaded BlueWave .NEW reply packets - the BW/2 door processes them
instantly.  This is one of the strangest 'quirks' I've run into yet with
Maximus/2!

If there were something wrong with the routine that calls UnZip, you'd
think it would be the same regardless of a telnet connect or dial-up
connect.  They would seem to be not related to the unzipping of files. 
Very odd... 

Still open for suggestions!!

 BJ> Interesting....  Care to see what my telnet stuff is doing for
 BJ> timing?  [ telnet://tophat.darktech.org , running Bink/Max under
 BJ> OS/2 using VModem.] 

I'll have a look!

Best regards,
Marc

--- timEd/2 1.10.y2k+