D-Link DFE-650 Series User Manual page 43

Now we can cull that list of program names, by disregarding any
item which is obviously not the name of a network driver. You
might notice that some of the items (as in the example above) are
names of DOS commands.
whether any item is the name of a DOS command is to search for
that name in the alphabetical index of DOS commands which
appears when you type "
example, we have a list of ten names, and we can
disregard MSDOS, because it is the "System Program," and
thus is not a network driver
disregard
alphabetical list of DOS commands
disregard SMARTDRV,
alphabetical list of DOS commands
disregard MSCDEX, because it appears in the alphabetical
list of DOS commands
disregard DOSKEY, because it appears in the alphabetical
list of DOS commands
disregard MEM, because it appears in the alphabetical list of
DOS commands
This leaves us to deal with just four possibilities as to the name of
the network driver which is conflicting with our Quick Install:
Let's call this list the "short list." One of the items in the short list
is certain to be the conflicting driver.
Now It's Trial-and-Error Time
It is good news that the short list is short. The bad news is that
there is only one method guaranteed to determine which of the
Troubleshooting
DFE-650 Series Fast Ethernet PC Card User's Guide
help"
COMMAND,
LSL, DFE650, IPXODI, and NETX
(A convenient way to determine
at the DOS prompt.) Thus, in our
because it
because it
appears in
appears in
the
the
35