Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!FRSAC11.BITNET!NETWORK
From: NETWORK@FRSAC11.BITNET
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: 3c503 Packet driver, a follow up.
Message-ID: <8911280724.aa04885@louie.udel.edu>
Date: 28 Nov 89 13:14:02 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 36

Date: 28 November 1989, 13:02:30 GMT
From: NETWORK  at FRSAC11
To:   pcip@udel.edu

Following my posting related to the 3C503 packet driver :

I am using packet driver version 3.1, June 1989, on a AT, with a nice
blue drop cable to a transceiver drilling into a bright yellow cable.
My 3C501 card is nicely driven by the version 3.0 of the same mine.

1. Others wrote to me telling they where not able to use 3C503.

2. Somebody told me a trick : The 3.1 version is hard-assembled for
   the thin Ethernet output, tough luck, I am using Thick Yellow tubing,
   and it was not documented.
   A mod in the source an re-assembly should do the trick, but I dont
   have assembler...
   I gave a shot at a binary patch, with some progress, but no real
   success. (Message telling me there is already someone with this
   IP address, given by NCSA 2.2tn)

3. There should be a new version by now, with a command line argument
   to switch the kind of output.
   Where can I get hold of it ?
   What version is that ? (So I can be sure to get the right stuff)

Thank you all folks, specially the one that spend time writing
code, and answering my almost dumb questions.

Regards,

Jean-Pierre H. Dumas

network@frsac11 (bitnet)
network%frsac11.bitnet@cunyvm.cuny.edu (arpanet)
dumas@sumex-aim.stanford.edu (arpanet)