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

So which line of AUTOEXEC.BAT do we need to delete?

Page 35 highlights

DFE-650 Series Fast Ethernet PC Card User's Guide will cause unloading of the same driver (if it is in fact already loaded). But such unloading is only possible under special circumstances. So, as a practical matter, what we really must do is avoid loading of the conflicting driver upon startup of the notebook PC. A software installation procedure (such as "Quick Install 16-bit Driver for DOS NetWare Client") copies the necessary drivers and related modules from the supplied DFE-650 Series Fast Ethernet PC Card Driver diskette, into the target directory of the notebook PC's hard drive or other storage. The installation program also adds commands to the computer's AUTOEXEC.BAT file, so that each time the computer is subsequently booted up (and you then make certain choices in the startup menus, if any), the drivers and related modules are automatically loaded into memory. The "conflicting driver" problem now at hand arises because certain commands already present in your notebook PC's AUTOEXEC.BAT file are being executed during bootup, and are causing some kind of previously installed network driver module to be loaded into memory. The presence of that network driver in memory is now making it impossible to load the DFE-650 network driver software (16-bit driver for DOS NetWare client). So the fix is to delete from AUTOEXEC.BAT the line which is causing the conflicting driver to be loaded. Thus we will avoid loading of the conflicting driver when we next restart the notebook PC. And the trick is to delete that line from AUTOEXEC.BAT without deleting or changing anything which needs to remain unchanged in AUTOEXEC.BAT (so that your notebook PC will behave as you expect it to after each startup). So which line of AUTOEXEC.BAT do we need to delete? Now there is a really good question! It gets right to the heart of the problem. If you are savvy enough about such matters, then you may be able to go directly into DOS Edit, Troubleshooting 33

  • 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
33
will cause unloading of the same driver (if it is in fact already
loaded).
But such unloading is only possible under special
circumstances.
So, as a practical matter, what we really must do is
avoid loading of the conflicting driver
upon startup of the notebook
PC.
A software installation procedure (such as "Quick Install 16-bit
Driver for DOS NetWare Client") copies the necessary drivers and
related modules from the supplied DFE-650 Series Fast Ethernet
PC Card Driver diskette, into the target directory of the notebook
PC's hard drive or other storage.
The installation program also adds
commands to the computer's AUTOEXEC.BAT file, so that each
time the computer is subsequently booted up (and you then make
certain choices in the startup menus, if any), the drivers and related
modules are automatically loaded into memory.
The "conflicting driver" problem now at hand arises because certain
commands
already
present
in
your
notebook
PC's
AUTOEXEC.BAT file are being executed during bootup, and are
causing some kind of previously installed network driver module to
be loaded into memory.
The presence of that network driver in
memory is now making it impossible to load the DFE-650 network
driver software (16-bit driver for DOS NetWare client).
So the fix is to delete from AUTOEXEC.BAT the line which is
causing the conflicting driver to be loaded.
Thus we will
avoid
loading of the conflicting driver
when we next restart the notebook
PC.
And the trick is to delete that line from AUTOEXEC.BAT
without deleting or changing anything which needs to remain
unchanged in AUTOEXEC.BAT (so that your notebook PC will
behave as you expect it to after each startup).
So which line of AUTOEXEC.BAT do we need to delete?
Now there is a really good question!
It gets right to the heart of the
problem.
If you are savvy enough about such matters, then you
may be able to go directly into DOS Edit,