Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!ucsd!ucbvax!NMS.HLS.COM!kzm
From: kzm@NMS.HLS.COM (Keith McCloghrie)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: FTP Problem: PS/2-to-Spartacus
Message-ID: <9005301903.AA08140@nms.>
Date: 30 May 90 19:03:39 GMT
References: <9005291405.AA01736@vax.ftp.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34

> I suspect that Hughes version numbers map 1:1 to ours, thus
> 2.02 was current q2 1988 to q4 1988, 2.03 from q4 1988 to q4 1989, and
> 2.04 from q4 1989 to the present.  If they lag behind us a quarter or
> so it isn't their fault - the kit they get isn't ready to go when we
> start shipping ourselves.

James is correct.  Our 2.02 release incorporated FTP Software's 2.02
release, our 2.03 incorporates their 2.03.  We've only recently 
received 2.04 from them, so it's not incorporated into our product
at this time.
 
We strongly recommend that you upgrade to 2.03.  In this era of 
fast-paced advances in technology, any software which was written 
almost 3 years ago, starts to seem really creaky/cranky compared 
to today's.

> You don't say what is happening to the TCP window on the data
> connection, but IBM mainframes tend to offer very large values, and
> change them in arbitrary ways.  This could be what is confusing the
> TCP, in which case you need an upgrade to the TCP/IP TSR module
> (I don't know what Hughes calls it - we call it the kernel).

Yes, we call it the kernel, too. (We're not that imaginative !!).
 
> Alternatively, the large data packet we send could be confusing the
> PS/2's hardware driver, and when we get repeated errors we give up.

Yes, there's a known bug in the driver for the Western Digital
MCA board (which I suspect you're running), which sometimes occurs 
when sending large packets.  You can get the fix through
contacting your local sales office.

Keith McCloghrie
Hughes LAN Systems