Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!ken
From: ken@cs.rochester.edu (Ken Yap)
Newsgroups: comp.protocols.appletalk
Subject: Stanford MacIP bug?
Message-ID: <1990Apr13.044704.27811@cs.rochester.edu>
Date: 13 Apr 90 04:47:04 GMT
Reply-To: ken@cs.rochester.edu
Organization: University of Rochester Computer Science Department
Lines: 21
Address: Rochester, NY 14627, (716) 275-1448

Probably asked the wrong audience in comp.sys.mac, nobody knew
anything.

I was using Stanford's MacIP ftp to transfer Macbinary files generated
with mcvert from a Sun to a Mac and noticed that it rejected a file
because of CRC mismatch. Upon investigation, I found that a file I'd
sent the other direction had zero in the CRC field. Too much of a
coincidence. So I zeroed the CRC field on the Unix file and bingo it
came across ok.

So my question is: is this a known bug in SU MacIP? (I should have
noted the version, but I think it is the previous one--3.0.) Or is this
an old spec? Should I tell the Mac owners to upgrade to a more recent
MacIP? Or get a better networking package?

Thanks in advance for email replies, I'll summarize upon request and
all that.

	Ken
	ken@cs.rochester.edu
	..!rochester!ken