[comp.protocols.tcp-ip.ibmpc] 3c523 cards and Packet Drivers

troch@pilot.njin.net (Rod Troch) (11/01/90)

I have followed the recent thread on the problems with packet drivers
from clarkson for the 3com 3c523 cards to no avail.  I am still having
problems getting this working.

Let me explain what I have done.
I have gen'd the proper shells for Novell Netware 2.15.  These shells
work fine, I can login to the server and run applications.
I have ftp'd the 3c523 packet drivers from Clarkson (vers 7).  I load
the Novell shell then the packet driver and login to the network.  I
then attempt to run a FTP product and it fails.  With version 7 of the
packet driver I get a Initialization failed..timeout error, which was
discussed in the recent thread, I then attempted the same thing with
one change, I load a Clarkson packet driver version 5, then TERMINate
it and then load the packet driver version 7.  This too fails when I
attempt to run a FTP product.  But this time I do not get the
initialization failed error instead the computer locks-up and the
screen flashes all different colors and characters.

Has anyone else come across these problems?  I am hoping someone can
give me some new information as to what I am doing wrong.

Thanks,
Rod
-- 
-----------
If you yell try : Rod Troch
internet        : troch@pilot.njin.net     :     troch@luau.kean.edu   
                : troch@bart.kean.edu <--> NeXT Mail (Lip Service)
compuserve      : 75335.544@compuserve.com
               | Friends don't let friends Beer Goggle |

jbvb@FTP.COM ("James B. Van Bokkelen") (11/03/90)

    I have gen'd the proper shells for Novell Netware 2.15.  These shells
    work fine, I can login to the server and run applications.
    I have ftp'd the 3c523 packet drivers from Clarkson (vers 7).  I load
    the Novell shell then the packet driver and login to the network.  I
    then attempt to run a FTP product and it fails.

If this is in fact what you have done, the error is simple:  If your Netware
shell can run by itself, without loading the Packet Driver first, then it
has its own built-in hardware driver.  When you load the Packet Driver later,
both pieces of software are trying to talk to the same hardware, and you
get a crash.

What you need to do is build a Netware shell which doesn't have its own
hardware driver, instead depending on the Packet Driver (which must be
loaded before IPX.COM).  If you have our PC-210 distribution, you'll find
the BYU SHELLDRV.OBJ file on the 4th or 5th disk, along with directions
on how to link it into a new IPX.COM.

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