Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!FTP.COM!jbvb
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Packet or NDIS Driver for 3C505 and PC/TCP and CUTCP
Message-ID: <9106271916.AA04010@ftp.com>
Date: 27 Jun 91 19:16:51 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@ftp.com
Organization: The Internet
Lines: 16

Your summary of my previous posting is correct, and represents my best
understanding of the situation.  Our recommendation of the 3Com NDIS
driver for the 3C505 is based on a guess that they would have either
applied workarounds for the ROM bugs or downloaded code to fix them
(possibly the same code as the 3C505-specific version of PC/TCP does,
since we got that via a 3Com engineer who was disappointed in the
performance of our LANWatch product in an early version that used the
on-board ROMs).

If I had to guess why CUTCP worked with the Packet Driver and PC/TCP
failed, I would say 'timing'.  We probably hit a timing window that
CUTCP avoids, either through luck or because the developer of the
3C505 packet driver did more testing with CUTCP than PC/TCP.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901