[comp.protocols.tcp-ip.ibmpc] Ungerman Bass NIUPc and 3c503 packet drivers

black@beno.CSS.GOV (Mike Black) (07/07/90)

I recently have tried to implement the Clarkson packet driver on two different
machines at work.  The drivers include one for the 3c503 card, but only in
shared memory mode.  I can't run in shared memory mode!! cuz' of other cards
already in the machine.  Has any one got a driver for the 3c503 in io--byte
mode?
Then I tried on another machine with an Ungerman-Bass NIUPc card.  There
doesn't seem to be a driver for this.  I DESPERATELY need NCSA Telnet and
ftp on the packet drivers as UB's versions are abhorrently lacking in any
features.  So, any one got a packet driver for the UB cards?  I have over
a 100 of these in my building.
Any help would be greatly appreciated.
Mike...
--
-------------------------------------------------------------------------------
: usenet: black@beno.CSS.GOV   :  land line: 407-494-5853  : I want a computer:
: real home: Melbourne, FL     :  home line: 407-242-8619  : that does it all!:
-------------------------------------------------------------------------------

CSP1DWD@OAC.UCLA.EDU (Denis DeLaRoca 825-4580, 213) (07/08/90)

I think Russ Nelson, the keeper of the Driver Collection, had
expressed the intention to implement an Ungerman Bass driver at
some point. Maybe he'll reply to the list on how he is coming
on that project.

-- Denis

nelson@sun.soe.clarkson.edu (Russ Nelson) (07/08/90)

In article <48967@seismo.CSS.GOV> black@beno.CSS.GOV (Mike Black) writes:

   I recently have tried to implement the Clarkson packet driver on
   two different machines at work.  The drivers include one for the
   3c503 card, but only in shared memory mode.  I can't run in shared
   memory mode!! cuz' of other cards already in the machine.  Has any
   one got a driver for the 3c503 in io--byte mode?

Not that I know of.  However, the ne1000 is also a 8390-based driver, and
it operates in I/O mode.  Perhaps you could bash it and 3c503.asm together
to arrive at a 3c503 I/O based driver?

   Then I tried on another machine with an Ungerman-Bass NIUPc card.

There is no such driver that I know of.  I've got a PC/NIC (the dumb card) 
courtesy of Rutgers, and I'm working on a driver for it.  I don't think
that helps you, however.

--
--russ (nelson@clutx [.bitnet | .clarkson.edu])  Russ.Nelson@$315.268.6667
In Communism's central planning, citizens are told "you will make widgets".
In Capitalism's advertising, citizens are told "you will buy widgets".

jbvb@VAX.FTP.COM ("James B. Van Bokkelen") (07/09/90)

>From: Denis DeLaRoca (213)825-4580 <CSP1DWD@oac.ucla.edu>
>Subject: Re: Ungerman Bass NIUPc and 3c503 packet drivers
>
>I think Russ Nelson, the keeper of the Driver Collection, had
>expressed the intention to implement an Ungerman Bass driver at
>some point. Maybe he'll reply to the list on how he is coming
>on that project.

U-B has two basic kinds of card - the NIC is dumb (having no on-board
processor) and the NIU is smart (on-board 80186).  Doing a Packet
Driver for a dumb board isn't too hard, if you can get the specs from
U-B.  Doing a driver for a smart card is a horse of another color,
given that you need code to load onto the card, a host-resident
loader of some sort, and possibly an in-circuit-emulator to debug it
(3Com's 3C505 is a special case, as it's on-board ROM contains a
basic driver).  U-B definitely has a loader, and might have a
link-layer load module (as opposed to their board-resident TCP). I
can't say whether they would release them into the public domain...

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

nelson@sun.soe.clarkson.edu (Russ Nelson) (08/15/90)

In article <9007080014.aa21002@louie.udel.edu> CSP1DWD@OAC.UCLA.EDU (Denis DeLaRoca 825-4580, 213) writes:

   I think Russ Nelson, the keeper of the Driver Collection, had
   expressed the intention to implement an Ungerman Bass driver at
   some point. Maybe he'll reply to the list on how he is coming
   on that project.

And maybe I won't.  :-)

But seriously, I've implemented a NIC/PC, not a NIU/PC driver.

--
--russ (nelson@clutx [.bitnet | .clarkson.edu])  Russ.Nelson@$315.268.6667
We won the cold war.  The Russians spent trillions defending their stuff,
then they found that they didn't have any stuff.  Will we avoid the same trap?