PCnet Software Release 3.30 May 5, 1997
---------------------------------------
This is the release notice for the PCnet Family Network Drivers Revision
3.30 software (object code and limited source code). The release is
contained on 6 diskettes labeled 1 through 6 (described below) of
which diskettes 4, 5 and 6 are formatted with UNIX file systems.
Only diskettes 1, 2 and 3 are in DOS FAT format.
PCnet Driver Release 3.30 is a minor release that is intended to fulfill
the following marketing and support requirements:
- Provide latest drivers that resolve a number of problems that have
been found through internal testing and by external customers
- Synch up all OEM/LT customers with the latest drivers
- Release new NDIS 4 miniport driver for Windows NT and Windows 95.
This driver supports AMD's Magic Packet implementation and
operation.
The elements of this release are:
ODI Drivers (DOS, OS/2, Server)
NDIS 2.0.1 Drivers (DOS version 6.x, OS/2 version 3.x and 4.x)
NDIS 3.x Drivers (for WFW 3.11; NT versions 3.5, 3.51, 4.0; Win95)
NDIS 4.x Driver (for Windows NT 4.0 and Windows 95 OSR 2)
SCO UNIX Drivers (SCO ODT 3.0, SCO Open Server 5.0)
Sun Solaris Driver (for v2.4)
Novell UnixWare Drivers (for v1.1 and 2.0)
Packet Driver
Generic BootROM
AMInstall (Generic Installation utility)
DMInstall (DMI Installation utility)
Of these programs, the following have changed since Revision 3.20:
Server ODI and asociated INF files
DOS ODI
NDIS 2.0.1 (OS/2) and associated NIF file for OS/2
NDIS 3.x (Windows 95)
NDIS 3.x (Windows NT 3.51, Windows NT 4.0)
NDIS 4.x Driver (new driver for Windows NT 4.0 and above and
Windows 95 OSR 2 and above)
AMInstall
The Rev 3.30 binary files are distributed among the 6 diskettes as follows:
Disk 1 - NDIS 2, ODI, Packet Driver, NDIS 3.x for WFW 3.11 and
Windows 95, NDIS 4.x for Windows 95 OSR2
Disk 2 - NDIS 2, NDIS 3.x for Windows NT 3.xx, NDIS 4.x for Win NT 4.0
SCO UNIX Open Server 5.0 MDI driver, UnixWare 2.0 DLPI driver
Desktop Management Interface support
Disk 3 - Novell Support files, Packet Driver Source, Generic BootROM
Disk 4 - SCO UNIX ODT 3.0 LLI Driver
Disk 5 - UnixWare 1.1 DLPI Driver
Disk 6 - Sun Solaris Driver
DRIVER CHANGES: Rev 3.20 to Rev 3.30
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. NDIS 2.0.1 (OS/2) Driver, Version 3.21
· Fixed OS/2 Warm boot hangs with AMD PCI device based adapter
cards on certain PC platforms.
2. NetWare Server ODI Driver, Version 3.21
· The Link Speed was hard coded to 10 Mbits/s. The driver now
reports the correct Link Speed at both 10 and 100 Mbps.
· The 32-bit ODI driver was unable to detect the PCnet devices
on Windows NT running Client 32. The problem has been corrected
by modifying the PCNTNW.LAN and OEMSETUP.INF files.
· Support for the BUSTIMER keyword has been added in the OEMSETUP.INF
file.
3. Netware DOS ODI Driver, Version 3.30
· The driver has been recompiled with new include files to be able
to pass new Novell certification test requirements.
4. NDIS 3.1 (Windows NT) Driver, Version 3.23
· Fixed warm boot hangs with AMD PCI device based adapter cards on
certain PC platforms.
· Fixed blue screen problem when doing Net Start and Net Stop in a
DOS box.
5. NDIS 3.1 (Win95) Driver , Version 3.22
· Fixed blue screen on PC systems with power management module when
the Suspend mode is exercised during the Win 95 shutdown process.
6. AMInstall, Version 3.23
· Fixed the problem of system crashes when the Automated Option is
selected in the AMInstal menu.
· Fixed large memory size requirements for AMInstal operation.
AMInstal requires 375 K of memory now - about a 100 K less than
the previous version. This bug was introduced in the previous
release of AMInstal.
· Fixed the problem of AMInstal not reporting a conflict when
one tries to program the I/O address to 360h and a device is
using 376h.
7. NDIS 4.x (Win95 OSR2 and Win NT 4.0) Driver, Version 1.0
· New driver that supports the Microsoft NDIS 4 specification
The new driver supports all existing PCnet ethernet controller
devices in the above mentioned operating system platforms.
· The driver supports a new keyword called MPMODE to enable Magic
Packet support. This keyword can be set using a installation
dialog box check box or by using the Windows Registry. If the
MPMODE is set, the driver will program and modify the CSR
registers appropriately to enable the Magic Packet mode.
DISK LAYOUT CHANGES: Rev 3.20 to Rev 3.30
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Disk 1
- Created new directories Win95\MAC\NDIS3 and
Win95\Miniport\NDIS4. These two directories
will contain the NDIS 3 MAC and NDIS 4 miniport
drivers and associated files respectively.
- Moved DOS and OS/2 NDIS 2.0.1 Driver dirs and
associated files to Disk 2 (mslanman.os2 and
malanman.dos).
2. Disk 2
- Created new directories WinNT\MAC\NDIS3 and
WinNT\Miniport\NDIS4. These two directories
will contain the NDIS 3 MAC and NDIS 4 miniport
drivers and associated files respectively.
- Moved DOS and OS/2 NDIS 2.0.1 Driver dirs and
associated files from Disk 1 (mslanman.os2 and
malanman.dos).
DOCUMENTATION UPDATES
~~~~~~~~~~~~~~~~~~~~~
This release contains an updated version of the frequently asked
questions (FAQ.Doc) document and a test plan and report
(TstReprt.Doc) describing the scope and content of tests that
were conducted with this release of the drivers and AMInstal.
These documents are available in the distribution media
(Docs directory in Disk 3).
KNOWN PROBLEMS IN Rev 3.30
~~~~~~~~~~~~~~~~~~~~~~~~~~
The following are brief descriptions of known problems
in this release. For details, please refer to the PCnet
Driver Rel 3.30 Test Report, which is included in the
distribution media.
AmInstal
--------
1. AMInstal recognizes PCnet-FAST as PCnet-PCI (AM79C970), i.e.,
it has the following problems:
- Device name is shown as PCI instead of PCnet-FAST
- There is no additional option about Full Duplex Mode,
Burst Mode, SRAM, etc.
2. AMInstal Diagnostics features are not functional when used
with PCnet-FAST.
3. If one runs AMInstal with RomShield enabled in the BootROM,
the terminal locks up. AMInstall unmaps the boot ROM
causing the system to lock up.
DOS ODI
-------
1. OS reports error when the DOSODI v3.1 is loaded into
upper memory. When loading the LSL, PCNTNW, IPX
ODI high and then do a soft reboot, himem.sys
loads and then one gets an error message. The error
message states that an area of memory above 1M is not
reliable. The problem occurs in certain PC platforms
only.
2. Link Speed is hardcoded to 10 Mbps in the DOS ODI driver.
All Drivers
-----------
1. All Drivers overwrite LED values in the EEPROM. When
loading any of the drivers, the LED values which
are set in the EEPROM are overwritten by the driver
default values.
The NDIS 4 driver uses the keyword LED to determine
if the driver should use its own hardcoded LED values
or use the ones specified in the INF file. If the LED
keyword is set to 0x10000, the driver uses the LED
values from the INF file, if they are present.
Win 95 NDIS 3
-------------
1. Win 95 NDIS 3 driver loads even though one tries to stop
driver from loading by writing bad data to EEPROM.
2. When the resources button in Device Manager is clicked, it
may take 40 to 90 seconds for Windows 95 to display the
resources. This problem is system specific (i.e.,
does not occur on all systems) and occurs with PCnet
PCI II and PCnet-FAST device based NICs.
Win NT NDIS 3
-------------
1. When on board PCnet-Fast is disabled in the BIOS, system
crashes. Occcurs with NDIS 3 driver in NT 4.0
environment.
DOS NDIS 2
----------
1. NDIS 2 driver fails to load when settings in
netamd.inf are incorrect.
BootROM
-------
1. The PCI data structure entry 'Image Length' at location 2Ch
(offset 10h within the data structure) has a value of
0001h. This would mean the ROM image is only 512 bytes
long. The correct value should be 0020h, since the image
is 16K in size.
SCO UNIX
--------
1. System panics when initstate is changed to 1 after u203
installed. Problem occurs with SCO UnixWare v2.0x
as well as UnixWare v2.1
NDIS 4
------
1. System Crashes when NDIS 4 Driver is in Xmit Rcv Mode and is
simultaneously receiving and transmitting small broadcast
packets with zero delay. Broadcast packets are generated
using test tools on multiple systems in the network.
-----------------------------------------------------------------------------------
The following is information carried over from previous releases.
-----------------------------------------------------------------------------------
DRIVER CHANGES: Rev 3.1 to Rev 3.20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. NDIS 2.0.1 (DOS and OS/2), Version 3.12
- Fixed a driver loading problem in OS/2 when there are four adapters in
the system.
- Fixed MTTOOL certification failure under DOS.
2. NetWare Server ODI Driver, Version 3.20
- Fixed driver interrupt disable bug in PCI interrupt sharing mode.
- Added new keyword "AMDDEV" as an alternative to the "BUSTYPE"
keyword to avoid conflict.
- Upgraded to HSM 3.3 Spec for NetWare "Green River" support.
- Moved Schedule Call Back routine after MSMRegisterMLID in DriverInit
to support NetWare SMP.
- Fixed problem while driver loading on PCnet-ISA, PCnet-ISA+ and
PCnet-ISA II controllers.
3. NDIS 3.1 (Win95 and NT3.51), Version 3.18
- Fixed IPX packet burst issue with PCnet-ISA.
- Fixed issues with PCNFS v 2.0 under Win 95.
- Fixed NDIS certification problem with ISA (B1 and B2).
- Fixed stress test failure with PCnet-ISA adapters.
- Fixed issue with PCnet-PCI II as server trusted card for NDIS
certification i.e. the test reports "unable to start server".
- Fixed LED programming for more than one adapter under Windows NT.
- Fixed stress test throughput reduction with PCnet-PCI on an Intergraph
SMP system.
4. AMInstall, Version 3.20
- Added new media type 10Base5(AUI).
- Added Full Duplex support for 10Base5(AUI).
- Fixed problem with media type selection.
- Fixed problem of setting DMA differently in PCNET.TXT and PNP.DAT .
5. NetWare Server ODI INF file, Version 3.20
- Commented out "SLOT" keyword under the ISA PNP section to allow the
server ODI driver work with AMD's ISA PNP device.
6. NetWare Server ODI LDI file, Version 3.20
- Replaced "BUSTYPE" keyword with "AMDDEV" keyword to avoid the conflict
with the Netware 4.1x's new reserved keyword
7. NDIS 2.0.1(OS2) NIF file, Version 3.20
- Added parameter sections: bustype, txbufs, rxbufs, notxint, fulldup,
led0, led1, led2, tp, and netaddress to allow user modifying these
parameters.
8. NDIS 2.0.1(DOS) DMI instrumentation PCNET.OVL file, Version 3.20
- Recompiled with DMI SDK 1.1 to eliminate the random attribute errors
while running Microsoft Windows DMI Browser.
-----------------------------------------------------------------------------------
DRIVER CHANGES: Rev 3.0 to Rev 3.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. ODI (DOS)
- Minor performance enhancement.
2. NDIS 2.0.1 (DOS and OS/2)
- Removed unnecessary i/o delay macro.
- Resolved PCI bridge and 'split' PCI bridge problems.
3. NDIS 3.1 (Win95 and NT3.51)
- Enhanced small packet performance substantially.
- Resolved PCI bridge and 'split' PCI bridge problems.
- Simultaneously supports more than 3 PCnet devices.
- Supports 32 Bit DMA Addressing for PCI and VL Devices.
- Changed INF file to improve driver upgrade in Windows 95.
4. Packet Driver
- Implemented promiscuous mode.
- Fixed FDUP keyword bugs.
5. UnixWare 2.0
- Removed limitation preventing driver from loading above 16Mb.
6. AMInstall
- Fixed several problems related to memory size, such as system hang
up, system reset, returning to DOS prompt without doing anything.
- AMINSTAL.BAT has been introduced to work around some boundary
condition errors at low memory thresholds. Users should now run
AMINSTAL.BAT instead of AMINSTAL.exe (AMINSTAL.EXE has been renamed
to AMINST.EXE). AMINSTAL.BAT first checks if at least 375K RAM is
left in the system, if so, it invokes AMINST.EXE. Otherwise a message
is displayed on the screen indicating that more free RAM is needed. At
this point, the installation is aborted.
- Add P1/P2 support: users now can program PCnet PCI Devices thru Aminstal.
- Add ISA_Duo support: users can configure ISA-Duo card to legacy mode
by selecting "Manual Mode", or configure it to PnP mode by selecting
"PnP mode" in "Custom" Window.
- The hang up problem when running from a write-protected disk has been
fixed.
- A work around for an AMI Plug-n-Play BIOS bug has been implemented.
- Misleading information of BOOTROM address for ISA+/ISA-II devices has
been fixed.
- BOOTROM information for PCI device has been changed to "Auto" instead
of "Disabled".
- Now restores your previous configuration when you program a
ISA+/ISA-II device to PnP mode and later on you want to change it to
legacy (Manual configuration) mode.
- Fixed RADIO_BUTTON/CHECK_BOX not grayed out problem.
- Built relationship between Media selection button and Full-Duplex
button. Whenever Full-Duplex button is selected, media selection
button will be changed to Auto selected, and whenever BNC media is
selected, Full-Duplex feature will be disabled.
- Keyboard control is now more friendly.
- A hang up problem has been fixed. The problem was that configuring
ISA+/ISA-II device to PnP mode/Manual mode will hang up system after
running Diagnosis and then returning to Custom window via Main window.
- Fixed bug when user changed configuration between "Manual" and "PnP"
mode several times, the last "Manual" configuration would not be
configured successfully ... even when Aminstal took a long time to
complete it and reported success.
- Can now program ISA+/ISA-II/ISA-Duo adapters to have PnP configuration
and to make it come up active (visible) by changing item "PNP_VISIBLE"
in PCNET.TXT.
- Added more shortcuts in CUSTOM/DRIVER screen.
- Fixed display for 5 PCI cards. This problem happened if you had
4 PCI + 1 ISA(+/II/Duo) cards in one system.
- Fixed one PCI diagnostic bug. This problem caused testing failures
on some mahcines
- Screens for ISA, ISA+/ISA-II/ISA-Duo and PCI have been improved.
- Added LEGACY control bit in PCNET.TXT. This bit controls whether
ISA-Duo will be a pure legacy device or a PnP device with one set of
resources described in EEPROM. This change only applies to an ISA-Duo
device which is configured to be in Manual Mode.
- Modified SAFET program :
... fix EEPROM diagnostic problem related to the machine speed.
... reduce memory size.
... add TEST4 result for ISA+/II/Duo devices.
7. DMInstall
- Fixed erratic behavior when 'Tab' key pressed from an active pull
down menu.
- Introduced some changes required for the WOSL.
8. DMI Windows Instrumentation
- Updated to v2.0 DMI SDK.
-----------------------------------------------------------------------------------
DRIVER CHANGES: Rev 2.5 to Rev 3.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. DMI support has been added to the ODI (DOS/OS2), NDIS2 (DOS/OS2), and
WFW NDIS 3 Drivers. The following procedure can be used to manually
install the required DMI files (see item #2 below for a description of
the automated DMI installation utility):
- Install your Pcnet network driver for DOS, OS/2 or Windows using
conventional installation procedures.
- Install the DMI package (SL, browser, etc) for the OS you plan to use.
If you do not have a specific DMI package for your system, one can
be obtained from the Desktop Management Task Force (DMTF). They can
be contacted at:
Desktop Management Task Force
M/S JF2-51
2111 N.E. 25th Avenue
Hillsboro, OR 97124
PHONE:(503) 696-9300
FAX: (503) 696-9027
- From the v3.0 release diskette #6, copy the files required for the
operating system you are using to the corresponding DMI directory.
for OS/2:
copy a:\dmi\pcnet.mif c:\dmi\os2\bin\mifs
copy a:\dmi\pcnet.dll c:\dmi\os2\bin
for DOS and Windows with real mode (ND2/ODI) Pcnet driver installed:
copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
copy a:\dmi\pcnet.ovl c:\dmi\dos\bin
for Windows for Workgroups 3.11 with NDIS 3 driver installed:
copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
copy a:\dmi\pcnet.exe c:\dmi\win16\bin
- Edit the pcnet.mif file's 'Serial Number', 'Installation' and
'Connector Type' fields.
- Install the pcnet.mif file into the SL's database. In the simplest
case, this can be done using the DMTF's browser.
- To verify that the installation was successfull, use your DMI
management application to explore the Pcnet information.
2. The manual procedure above can be effected using the DMINSTL.EXE program
provided on diskette #6 in the A:\DMI subdirectory. It copies the
necessary files. To invoke the program, place a *copy* of diskette #6
into drive A:. Make sure the diskette is *not* write protected. Enter
the following commands:
- C:>A: <Enter>
- A:\>CD \DMI <Enter>
- A:\DMI>DMINSTL <Enter>
When the main panel is displayed, enter the serial number of distribution
package you received (if none is provided, the field can be left blank).
Press the Enter key or the Tab key to advance to the next field.
The Installation Date field displays the current system time by default.
If you wish to change the value of this field, use the left and right
arrow keys to move about the text and type over the old values. Note that
DMINSTL uses the TZ environment variable to determine the offset from
GMT. If this variable is not set, DMINSTL assumes PDT (e.g. an offset
of +480).
Advancing to the Connector Type field, you can change its value by
pressing the Alt-F4 key combination and selecting the connector type in
use on your system. To highlight different values, use the up and down
arrow keys. To select one of the values, press the Enter key. To hide
the pull-down list and leave the selection unchanged, use the Esc key.
Finally, advancing to the Target Driver field, you can inform the
installation utility regarding which drivers you intend to run on the
system. The choices are NDIS 3 for native operation under Windows for
Workgroups v3.11. Or, you can select NDIS 2 / ODI for operation in DOS
or in WFW 3.11 using real mode DOS drivers.
Once the information has been entered, press the F10 key to initiate the
installation. Pressing Alt-F4 anytime prior to pressing F10 will cancel
the installation and return to DOS.
The DMI installation utility will invoke the DMI SL if found to assist
with the installation. If the SL cannot be invoked, DMINSTL will copy
the necessary files into the DMI directory structure -- which it will
create if not already present on drive C:. The next time the SL is
loaded, it will complete the installation on behalf of DMINSTL.
Note that DMINSTL expects to be executed out of the same directory that
contains the files:
PCNET.MIF
PCNET.EXE
PCNET.OVL
*IMPORTANT*
To avoid conflicts with certain TSRs, it is best to run DMINSTL in a
minimally configured system. In other words, booting to a plain vanilla
DOS system (e.g. no CONFIG.SYS and AUTOEXEC.BAT files) is preferred.
3. Modifications to the bootrom are detailed in the README file on disk #5
the directory A:\BOOTROM.
4. Two new Unix drivers have been added to the PCnet family: one for
Unixware 2.0 and one for SCO Unix OpenServer 5.0. Both drivers are
directly supported by the OSs (they appear as selections in the menus).
Please use the OS utilities to install and configure the drivers.
The versions on diskette #6 are updated to support the "pcnet2" keyword.
When this keyword is set to "1" in space.c (for both drivers), it enables
the "don't stop on Underflow" capability of the Pcnet-PCI 2 chip. By
default, this keyword is set to "0". If you wish to upgrade the driver
distributed with the OS, you need to copy some files from diskette #6
and rebuild the the kernel. Follow the procedure outlined below:
for Unixware 2.0:
cd /etc/conf/pack.d/pnt
doscp a:\unixware.20\driver.o Driver.o
doscp a:\unixware.20\space.c Space.c
/etc/conf/bin/idbuild
for SCO Unix OpenServer:
cd /tmp
doscp a:\scounix.50\install install
sh install
5. Two new directories with the NDIS2 DOS driver have been added on diskette
#6 to support DOS client packages for IBM Lan Server 4.0. The first --
\IBMLSP -- should be used as a path for the "Advanced Lan Support
Program". The second -- \IBMADOS -- is for the "Advanced Lan DOS
Services" package.
6. Two new directories with the NDIS3 drivers have been included on diskette
#6 to support Windows 95 and Windows NT v3.51. Note that the NT 3.51
driver is *not* backwards compatible with Windows NT v3.1 or v3.5.
To install the Win95 driver from the floppy diskette, please follow
these instructions:
- Using Network Setup (invoke by selecting the "Settings", "Control
Panel", "Network" icon), remove any previously installed PCnet Win95
driver.
- copy a:\win95\netamd.inf c:\windows\inf
- Then Shutdown and restart the system.
- On system reboot, if the PCnet adapter is detected, then you will be
prompted to install the driver from disk, and the rest of the network
files will be loaded from the MS distribution disks.
- If the system does not detect the PCnet Adapter, then go to the
"Settings", "Control Panel", "New Hardware" icon and choose from
"Network Adapters" the type of PCnet adapter being installed.
- On completion of installation reboot the system.
NOTES
~~~~~
1. When invoking the DMI Service Layer (SL.EXE), set the overlay buffer
size to 13k as follows:
C:\DMI\DOS\BIN> SL o=13 <Enter>
2. The OS/2 NDIS2 driver has been tested with OS/2 Warp 4.0.
3. Formal support for the v1.1 Unixware driver was dropped from PCnet Family drivers.
4. Certain system/floppy diskette drive combinations do not tolerate
the default PCNET-ISA dma mode which limits bus master DMA cycles
by the number of transfers performed. To address the problem, the
default mode for ISA systems has been changed. Although the DMABR
register retains the default values used in v2.0 of the drivers,
the DMABAT register is now enabled and is programmed to a value of
6 microseconds by default. This mode and value is ONLY used on ISA
systems.
Since the exact value for the DMABAT register is system dependent, a
new keyword - BUSTIMER - has been introduced to allow different values
to be selected. Generally speaking, a larger value improves
performance while a smaller value improves compatibility with
sensitive devices that use DMA (e.g. FDD). The valid range for the
BUSTIMER keyword is 5 to 13 inclusive.
At present, there is a known problem with systems designed around
Intel's Aries PCI/ISA bridge. In particular, the default value of
6 microseconds in the DMABAT may cause PCNET-ISA family devices
to experience difficulty when exchanging packets with other network
nodes. This problem can be resolved by increasing the DMABAT value
to 7 microseconds. However, it is possible that programs that use
system DMA heavily or that reprogram the DMA controller for added
performance may encounter difficulty when DMABAT is set to 7
microseconds.
DMABR=Chip Default (16 transfers)
DMABAT=6 micro sec (for ISA systems - not used on PCI or VL).
If BUSTIMER=n given either by command line or system configuration
utility, DMABAT is set to n micro secs.
5. Investigation into an NDIS2-OS/2 problem uncovered a general
situation that affects all drivers under the following circumstances:
* two PCNET-PCI devices are in use
* the two devices are sharing an interrupt
* the two devices are initialized to exchange packets on
the net
* a soft reset occurs
* the OS permits one device to be initialized and used
while the other remains presumably uninitialized (e.g. as
occurs under OS/2).
The problem is that the devices are actually in an operational state
because the soft reset does nothing to disable them save to prevent
DMAs into host memory. This implies that arriving packets will cause
the devices to signal an interrupt by holding the interrupt request
line active low. Assuming that while the system is being reset, both
devices receive packets (possibly broadcasts) they will both signal an
interrupt request. Since the system is being reset, the requests are
ignored. Once the reset completes, the OS loads and the first device is
initialized (thereby destroying its pending interrupt request), it can
now begin to transmit and receive packets. However, since the second
device has not yet been initialized, it is still holding the interrupt
request line low and therefore prevents the first device from
generating interrupts to the system.
To address this problem, the drivers that can exhibit this behavior now
implement an early reset algorithm. When they begin execution, they
reset all of the PCNET-PCI devices that they find. Naturally, early
reset is coordinated so as to prevent a second instance of a driver
from resetting a device that has already been initialized.
6. The Novell Server ODI drivers in this release use the Novell support
files. The following files are required with these drivers.
Module Ver. Size Date Time HSM Spec
MSM.NLM 2.32 20263 08-23-94 2:47P 3.2 CD
MSM31X.NLM 2.32 21303 08-23-94 2:47P 3.2 CD
ETHERTSM.NLM 2.32 9246 08-23-94 3:15P 3.2 CD
The above files are located in the Disk 5 of 5 from AMD. We have also
provided the new monitor programs for 3.1X and 4.X servers. Please make
sure that you use these modules from Novell with Novell HSM compatible
drivers from AMD.
11. Additional details regarding the problems fixed in this release can
be obtained from the Monthly PCnet Problem Report published by IND
Marketing, AMD.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.