D-Link DFE-650TX Product Manual - Page 37

Now It's Trial-and-Error Time, LSL, DFE650, IPXODI, and NETX

Get D-Link DFE-650TX PDF manuals and user guides View all D-Link DFE-650TX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

DFE-650 Series Fast Ethernet PC Card User's Guide 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. (A convenient way to determine 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 "help" at the DOS prompt.) Thus, in our 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 COMMAND, because it appears in the alphabetical list of DOS commands disregard SMARTDRV, because it appears in the 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: LSL, DFE650, IPXODI, and NETX 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 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
DFE-650 Series Fast Ethernet PC Card User's Guide
Troubleshooting
35
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.
(A convenient way to determine
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 "
help"
at the DOS prompt.)
Thus, in our
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
COMMAND,
because
it
appears
in
the
alphabetical list of DOS commands
disregard
SMARTDRV,
because
it
appears
in
the
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:
LSL, DFE650, IPXODI, and NETX
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