From: medici@dorm.rutgers.edu (Mark Medici)
Newsgroups: bit.listserv.novell
Subject: Re: Western Digital Drivers? -- HELP!!
Date: 1 Sep 92 18:58:01 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

SLQY8@USU.BITNET (The Blizzard) writes:
>Machine configuration:

>486 clone
>Western Digital ethernet card
>other stuff....
>(We are running TWO monitors on this system.)

>I am not sure whether the two monitors are causing the problem or not, but
>I cannot even get the packet driver to load where it is supposed to, which
>in turn causes IPX to not be able to find it.

>We are using BYU's packet driver software, version a.5c (that is what it
>says when I try to load the driver).
>The version of IPX that we are using is 3.01, Rev. A.  When IPX is loaded
>correctly, it also tells me that my packet driver is versopm 2.01.  (I got
>this from another machine that works properly...)

When troubleshooting and system configuration, always get to the
simplest configuration and work up:

   1.  Test the network cabling.  85% of all our network problems
       are caused by bad or poor cabling or connectors.  With coax
       Ethernet, you can perform basic tests with an Ohm-meter.  With
       terminators on each end and all devices on the net powered-
       down, you should measure 25 Ohms (+/- 2 Ohms) between the
       center conductor and outside shield.  Inexpensive devices are
       available to perform go/no-go tests on 10Base-T.  Testing
       AUI cables and thick-net transceivers requires more expensive
       equipment, so its usually easier to swap with known good
       transceivers and cables.
   2.  Remove all non-essential hardware from the system, including
       the secondary display.  All that should be left is the disk
       controller, network card, video card (1 only) and memory card
       (if there is a memory card).
   3.  Boot off a clean DOS floppy disk, with only the bare essential
       device drivers needed to be able to access the system's
       display, disk drives and network card.  Use no memory
       management or enhancement drivers or TSRs.
   4.  Attempt to connect to the server via traditional methods (e.g.,
       WSGEN or SHGEN a dedicated IPX.COM, using ECONFIG if necessary
       to set for Ethernet_II packets if your server is set-up that
       way; then load this IPX.COM and NETX.COM).  If this doesn't
       work, your network card is incorrectly configured for the
       motherboard or is dead.
   5.  Once you can get to the server this way, then go to work on
       getting the packet drivers and PDIPX to work.
   6.  If this succeeds, then re-install removed hardware into the
       system, checking that the system can still get to the server
       after each individual component is reinstalled.  If the problem
       returns, check the hardware settings of the component that
       caused the problem, and change this component's settings, or
       the network board's settings, to resolve the conflict.
   7.  After getting all the hardware back in, follow the same
       process with drivers and TSRs.  When using memory managment
       utilities, (e.g, EMM386.EXE, QEMM, 386MAX, etc), make certain
       that you exclude the RAM range for the network card in the
       emm driver's load command.  If the system fails to get to the
       server at any point, you have discovered (one of?) the
       problems.  



-- 
_________________________________________________________________________
RUCS     | Mark A. Medici, Systems Programmer III, User Services Division
User     | Rutgers University Computing Services, New Brunswick, NJ 08903
Services | [medici@gandalf.rutgers.edu]                    [908-932-2412]
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU