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

<Enter&gt, Use the, Command to Help Identify the Conflicting, Network Driver

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 36 highlights

DFE-650 Series Fast Ethernet PC Card User's Guide C:\> edit autoexec.bat and find the troublesome line by inspection, and simply delete it. But if you are that clever, then it is very unlikely that you will be reading this. So here is a procedure which will help you to identify the troublesome line of AUTOEXEC.BAT. Use the MEM Command to Help Identify the Conflicting Network Driver At the DOS prompt (here represented by C:\>), type C:\> mem /d | find "Program" exactly as shown here, including the vertical bar (DOS "pipe" symbol, |), then . The resulting display of memory allocation information will be a few rows of tabular data. Here is an example: 0122E 80 Program 01236 2,656 012F8 5,376 0144F 32,994 01718 16,640 01B28 48,688 0270B 29,024 02E2D 27,952 03500 4,144 03610 88,992 (0K) MSDOS System (3K) (5K) (32K) (16K) (48K) (28K) (27K) (4K) (87K) COMMAND LSL DFE650 IPXODI NETX SMARTDRV MSCDEX DOSKEY MEM Program Program Program Program Program Program Program Program Program The next-last column lists the names of certain program modules present in memory. We will disregard all the other columns. 34 Troubleshooting

  • 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
34
Troubleshooting
C:\> edit autoexec.bat
and find the troublesome line by inspection, and simply delete it.
But if you are that clever, then it is very unlikely that you will be
reading this.
So here is a procedure which will help you to identify
the troublesome line of AUTOEXEC.BAT.
Use the
MEM
Command to Help Identify the Conflicting
Network Driver
At the DOS prompt (here represented by C:\
>
), type
C:\> mem /d
|
find "Program"
exactly as shown here, including the vertical bar (DOS "pipe"
symbol,
|
), then
<Enter>
.
The resulting display of memory
allocation information will be a few rows of tabular data.
Here is
an example:
0122E
80
(0K)
MSDOS
System
Program
01236
2,656
(3K)
COMMAND
Program
012F8
5,376
(5K)
LSL
Program
0144F
32,994
(32K)
DFE650
Program
01718
16,640
(16K)
IPXODI
Program
01B28
48,688
(48K)
NETX
Program
0270B
29,024
(28K)
SMARTDRV
Program
02E2D
27,952
(27K)
MSCDEX
Program
03500
4,144
(4K)
DOSKEY
Program
03610
88,992
(87K)
MEM
Program
The next-last column lists the names of certain program modules
present in memory.
We will disregard all the other
columns.