The NDIS4 Miniport Driver
=========================
LSS 7.1(0), September 2000
--------------------------
Contents
--------
(1) Summary
(2) Driver installation
(3) Driver upgrade
(4) Windows 95/98/NT advanced configuration
(5) Troubleshooting
(6) Permanently disabling promiscuous mode
(7) Using CardBus adapters with Windows NT4
(8) Support for adapter mirroring
(9) Support for Compaq Hot-Plug PCI
(1) Summary
-----------
This file describes the NDIS4 miniport driver MDGNDIS4.SYS. The driver can be
used with the following operating systems:
o Windows 95b (OSR2)
o Windows 98
o Windows NT 4
The driver supports the following Madge and Olicom token-ring adapters:
o Madge Smart 100/16/4 PCI-HS Ringnode
o Madge Smart 100/16/4 PCI Ringnode
o Madge Smart 16/4 PCI Ringnode Mk3
o Madge Smart 16/4 PCI Ringnode Mk2
o Madge Presto PCI 2000
o Madge Presto PCI Plus
o Madge Presto PCI
o Madge 16/4 CardBus Adapter Mk2 (*)
o Madge 16/4 CardBus Adapter (*)
o Madge Smart 16/4 PCMCIA Ringnode Mk2
o Madge Smart 16/4 PCMCIA Ringnode
o Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter
o Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter
o Olicom RapidFire 3140 V2 16/4 PCI Adapter
o Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter
o Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter
o Olicom Token-Ring PCI/II 16/4 Adapter (OC-3137)
o Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card (*)
o Olicom GoCard Token-Ring PC Card (OC-3221)
(2) Driver installation
-----------------------
Refer to the section relevant to the operating system you are installing the
driver for. If you encounter any problems after the driver has been installed,
try running the Madge MDGLOG95.EXE program to display the status of the
adapter and driver.
(2.1) Windows 95b (OSR2) installation
-------------------------------------
(2.1.1) Preparation
-------------------
Before installing the driver it is advisable to delete INF files from the
computer which support the same device as the one you are about to install,
otherwise Windows may install an old driver for the device. You can delete
the following files from \WINDOWS\INF : NETMADGE.INF, NETOLI.INF, NETOCT3.INF
and NETOCT34.INF.
(2.1.2) Installation
--------------------
1. Install the adapter into the PC with the power off, then boot the PC
into Windows 95.
2. Windows will automatically detect the new adapter. If there is no INF file
in the WINDOWS\INF directory which supports the new adapter, Windows will
prompt you for the driver location. Check "Driver disk provided by
hardware manufacturer" and click OK.
3. In the "Install from Disk" window, type the path to the driver files, e.g
"A:\" if they are on a floppy disk.
4. Click OK. Windows copies the driver files from the specified location.
5. If prompted, insert the Windows 95 CD-ROM, type the path to the
Windows 95 files (e.g D:\WIN95) and click OK. The required Windows system
files are copied onto the PC.
6. Reboot the PC.
(2.2) Windows 98 installation
-----------------------------
(2.2.1) Preparation
-------------------
Before installing the driver it is advisable to delete INF files from the
computer which support the same device as the one you are about to install,
otherwise Windows may install an old driver for the device. You can delete
the following files from \WINDOWS\INF : NETMADGE.INF, NETOLI.INF, NETOCT3.INF
and NETOCT34.INF. You can also delete these files from \WINDOWS\INF\OTHER
if they exist (in this directory the filenames will be preceded by "Madge",
"Olicom" or "Microsoft", e.g "MicrosoftNETMADGE.INF"). Windows copies an INF
file to the \WINDOWS\INF\OTHER directory when a device supported by the file
is installed.
(2.2.2) Installation
--------------------
1. Install the adapter into the PC with the power off, then boot the PC
into Windows 98.
2. Windows will automatically detect the new adapter and display the "Add New
Hardware Wizard". Click "Next" to allow WIndows to look for a driver for
the device.
3. Check "Search for the best driver for your device" and click "Next".
4. Check "Specify a location" and type the path to the driver files, e.g
"A:\" if they are on a floppy disk.
5. Click "Next" and follow the on-screen instructions.
6. Windows copies the driver files from the specified location.
7. If prompted, insert the Windows 98 CD-ROM, type the path to the
Windows 98 files (e.g D:\WIN98) and click OK. The required Windows system
files are copied onto the PC.
8. Reboot the PC.
(2.3) Windows NT 3.51/4 installation
------------------------------------
* Note that CardBus adapters are not supported under Windows NT 3.51.
1. Install the adapter into the PC with the power off, then boot the PC
into Windows NT.
2. Double-click on the "Network" icon in Control Panel to open the "Network"
window (NT4) or "Network Settings" window (NT3.51)
3. Under NT3.51, click on "Add Adapter".
Under NT4, click on the "Adapters" tab and then click on "Add".
4. Under NT3.51, select "[Other] Requires disk from manufacturer" from the
"Add Network Adapter" window and click "Continue".
Under NT4, click on "Have disk".
5. At the prompt type the path to the driver files, e.g "A:\" if they are
on a floppy disk.
6. Unless you're installing a CardBus adapter, select "Madge Automated
Installation - RECOMMENDED" from the list of adapters and click "OK".
The adapter will be detected and installed.
If you're installing a CardBus adapter, select the adapter from the list
of adapters and click "OK". If a supported 3rd party Card Services is
detected a message to this effect will be displayed, otherwise the
CardBus enabler internal to the driver will be used.
7. If you want to change the LAA, ring speed or any advanced settings click
"Configure" (NT3.51) or "Properties" (NT4).
8. Follow the on-screen instructions to complete the installation.
(3) Driver upgrade
------------------
This section describes how to upgrade from a previously installed driver for
a device.
Refer to the section relevant to the operating system you are installing the
driver for. If you encounter any problems after the driver has been installed,
try running the Madge MDGLOG95.EXE program to display the status of the
adapter and driver.
(3.1) Windows 95b (OSR2) upgrade
--------------------------------
Remove the existing driver, delete the driver's INF file from the WINDOWS\INF
directory (if it exists), reboot the PC and follow the instructions for new
driver installation. Note that any advanced configuration (e.g. LAA) must be
noted before removing the old driver and re-applied after the new driver is
installed.
(3.2) Windows 98 upgrade
------------------------
Either : (a) Remove the existing driver, delete the driver's INF file from
the WINDOWS\INF\OTHER directory (if it exists), reboot the PC
and follow the instructions for new driver installation. Note
that any advanced configuration (e.g. LAA) must be noted
before removing the old driver and re-applied after the new
driver is installed.
or
(c) Use the "Update Driver" button from the adapter properties
windows accesible from the "Device Manager" tab in the "System
Properties" window.
(3.3) Windows NT 3.51/4 upgrade
-------------------------------
Remove the existing driver, reboot the PC and follow the instructions for new
driver installation. Note that any advanced configuration (e.g. LAA) must be
noted before removing the old driver and re-applied after the new driver is
installed.
We recommend that you don't try to upgrade the driver using the "Update"
button in the "Network" window.
(4) Windows 95/98/NT Configuration
----------------------------------
Once the driver has been installed there are a number of adapter configuration
options which can be set. To change configuration options do the following:
Windows 95/98 - Choose the 'Network' option from the Control Panel. Highlight
the Madge adapter in the components list, select 'Properties',
and then 'Advanced'.
Windows NT - Choose the 'Network' option from the Control Panel. Select the
'Adapters' tab, highlight the Madge adapter in the list and
click on 'Properties'. To modify advanced configuration
options (everything except LAA and Ring Speed), click on
'Advanced'.
The configuration options are described below. Note that the default setting
of advanced parameters is normally optimal and should be changed with care.
(4.1) Options common to Windows 95/98 and NT
--------------------------------------------
The following options are common under all Windows versions.
Windows 9x Option : Network Address
Windows NT Option : LAA
-----------------------------------
The LAA is a 12 digit hexadecimal number in the range 400000000000 to
7FFFFFFFFFFF.
Every adapter requires a six-byte node address to identify itself on the
network. This node address is either the unique burned-in address (BIA)
encoded on the adapter, or is a user provided locally administered node
address (LAA). If no LAA is provided, the adapter's BIA is used as the node
address.
The only restrictions on the value chosen for the LAA are that the first digit
of the LAA must be between four and seven inclusive and all LAAs must be
unique within a LAN segment.
Normally an LAA is not specified, unless communications software which
requires an LAA is being used
Windows 9x/NT Option : Ring Speed
---------------------------------
Use this parameter to set the ring speed as follows:
"Default (set at adapter)"
The ring speed will be determined by the configuration information
stored on the adapter. The adapter may have been configured to
100 MBit/s, 16 MBit/s, 4 MBit/s or automatic ring speed detect.
The configuration information stored on the adapter may be changed
using the Madge Assist Utility. This is the default value.
"4 MBit/s"
The adapter will be forced to operate at 4 MBit/s irrespective of
the configuration information stored on the adapter.
"16 MBit/s"
The adapter will be forced to operate at 16 MBit/s irrespective of
the configuration information stored on the adapter.
"100 MBit/s"
The adapter will be forced to operate at 100MBit/s irrespective of
the configuration information stored on the adapter. This option
only applies to adapters which support High Speed Token Ring.
Windows 9x/NT Option : Maximum Frame Size
-----------------------------------------
On a 16Mbps or 100Mbps token-ring network frame sizes up to 17839 bytes are
supported. On a 4Mbps network frame sizes up to 4486 bytes are supported. Many
protocols and applications do not actually use frames this large and setting
the maximum frame size to a value greater than is required wastes memory in
the computer. The default value of 4216 is optimal in most environments.
If the maximum frame size chosen is greater than the media supports, the
driver will automatically truncate it and write an error into the event log
that contains, as one of the data words, the actual maximum frame size used.
Windows 9x Option : Promiscuous mode support
Windows NT Option : Promiscuous mode
--------------------------------------------
All of the Madge adapters supported by this release except Presto PCI and
Presto PCI Plus can be used in 'StatisticsGathering' or 'Promiscuous' mode
whereby all frames on the ring, not justthose directed at the adapter, are
passed up to the protocols. This is disabled by default. Only enable this
option if it is required by an application.
Windows 9x/NT Option : Transfer Type
------------------------------------
On some adapters there are several different ways of transferring data between
the computer and the adapter. This option allows you to override the default
transfer type (normally DMA) and use 16-bit PIO instead. (Note, for some
adapters 16-bit PIO is the default transfer type.)
Windows 9x/NT Option : Wake-On-LAN
----------------------------------
Wake-On-LAN is a feature that allows a network adapter to wake-up a PC that
has been put into auxillary power mode when the adapter receives a MAGIC
PACKET(tm). For this feature to work you must have a PC that supports
Wake-On-LAN, an adapter that supports Wake-On-LAN and the adapter must have
its Wake-On-LAN connector attached to the PC. The following adapters support
Wake-On-LAN:
o Madge Smart 100/16/4 PCI Ringnode
o Madge Smart 100/16/4 PCI-HS Ringnode
o Madge Smart 16/4 PCI Ringnode Mk3
o Madge Presto PCI 2000
o Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter
o Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter
o Olicom RapidFire 3140 V2 16/4 PCI Adapter
o Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter
o Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter
If this parameter is set to Enabled then the adapter will be put into
Wake-On-LAN mode when Windows is shutdown. If a MAGIC PACKET(tm) is then sent
to the adapter it will wake-up the PC. If this parameter is set to Disabled
then the adapter will be closed down in the normal way when Windows is
shutdown and will not respond to MAGIC PACKET(tm)s.
Windows 9x Option : Warn if no lobe cable
Windows NT Option : Quiet Mode
-----------------------------------------
This parameter is designed for use with laptop adapters, such as PCMCIA and
Cardbus, and will prevent the system from producing an error and shutting down
the driver if the network cable is not plugged in.
Windows 9x Option : Respond to TEST/XID Frames
Windows NT Option : Respond to TEST/XID
----------------------------------------------
Some token-ring infrastructure products use Test and XID frames to identify
other devices on the ring. Handling of such frames is optional in this driver,
but is enabled by default. If you do not have any hardware which requires such
frames to be responded to, you can disable this feature, which would slightly
reduce the driver CPU utilisation.
Windows 9x/NT Option : Mac open mode
------------------------------------
Use this parameter to set the MAC open mode as follows:
"DTR or Classic"
The adapter will open in 'full duplex' mode if it is connected to a
port that supports 'full duplex' operation. The adapter will open
in 'classic' mode if it is connected to anything else.
"DTR only"
The adapter will only open in 'full duplex' mode. If the adapter is
connected to a port which doesn't support this mode the adapter will
not open
"Classic only"
The adapter will only open in 'classic' mode.
(4.2) Options Specific to Windows NT
------------------------------------
The following advanced options are specific to Windows NT.
I/O Location
------------
This field will only be displayed if the adapter is a PCMCIA or CardBus
adapter. It lists the possible locations for that type of adapter.
For PCMCIA and CardBus adapters, you must select an I/O location which is free
in your system. If the adapter fails to start after normal installation this
may be due to a resource conflict which can sometimes be resolved by trying
different I/O location, interrupt number and memory window values.
If a CardBus adapter is being used with a third-party Card Services, the
I/O location should be left as 'Automatic' or set to the same value as has
been assigned by the Card Services.
PCI Device ID
-------------
This field will only be displayed for PCI adapters. The field specifies the
PCI Device ID of the adapter.
Interrupt number
----------------
This field specifies the interrupt number used by the adapter. The value can
either be Automatic or a number. Automatic means that the driver determines
the interrupt number being used automatically when it loads. A number means
that the adapter uses the interrupt with that number.
If you choose the Automatic option, the driver reads the interrupt number to
be used from the adapter.
For most adapters, Automatic is the only option available. For PCMCIA
adapters, you must select an interrupt number which is free in your system. If
the PCMCIA adapter fails to start after normal installation this may be due
to a resource conflict which can sometimes be resolved by trying different
I/O location, interrupt number and memory window values.
For CardBus adapters, if the interrupt number is configured to 'Automatic',
the driver will either use the BIOS-assigned interrupt for the CardBus
controller (when available), the interrupt assigned by a third-party Card
Services (if used), or any interrupt which appears to be free. If the internal
CardBus enabler is being used, a specific interrupt number may be chosen if
the 'Automatic' setting fails to work.
Memory window
-------------
This field is only displayed for Olicom 3221 PCMCIA adapters. It specifies
the memory location used by Windows to map in the adapter's CIS.
You must select a memory window which is free in your system. If the PCMCIA
adapter fails to start after normal installation this may be due to a resource
conflict which can sometimes be resolved by trying different I/O location,
interrupt number and memory window values.
DMA channel
-----------
Unused
Tx slots
--------
This parameter sets the number of transmit slots used by the adapter. Under
normal circumstances, the default value will give optimal performance with
minimum use of system resources, but if you need more transmit buffering this
value can be increased.
Rx slots
--------
This parameter sets the number of recieve slots used by the adapter. Under
normal circumstances, the default value will give optimal performance with
minimum use of system resources, but if you need more recieve buffering this
value can be increased.
Ring Status mask
----------------
This parameter is a bitmask which determines the ring status events that are
indicated to the protocols by the driver. If the standard Microsoft protocols
are being used this parameter should NOT be changed from its default value of
0x1D60. The events controlled by this mask and the bits required to enable
them are:
o Ring Recovery 0x0020
o Single Station 0x0040
o Counter Overflow 0x0080
o Remove Received 0x0100
o Auto Removal 0x0400
o Lobe Fault 0x0800
o Tx Beacon 0x1000
o Soft Error 0x2000
o Hard Error 0x4000
o Signal Loss 0x8000
Token Ring event mask
---------------------
The amount information provided about the card by the driver in the event log
can be varied by adjusting this mask. Varying this parameter will not affect
the network functionality of the driver in any way, but this can be adjusted
to provide information about the network. The events that can be reported to
the event log and the bits required to enable it are:
o Adapter Reset 0x0002
o Open Mode 0x0004
o Adapter Closed 0x0008
o Adapter Dead 0x0010
o Ring Status Single Station 0x0040
o Ring Status Remove Received 0x0100
o Ring Status Auto Removal 0x0400
o Ring Status Lobe Fault 0x0800
o Ring Status Tx Beacon 0x1000
o Ring Status Hard Error 0x4000
By default this is set to 0x001c whereby the event log will contain
information on the open mode and if the adapter is closed or dies. All other
fatal errors will be reported in the event log regardless of the value of this
parameter.
Watchdog timer
--------------
If the computer should crash, it is desirable that the token ring adapter is
removed from the ring as soon as possible. To ensure this, the adapter
implements a watchdog timer. If the adapter loses contact with the host
computer for a period greater than the watchdog timeout, the adapter will
assume that the computer has crashed and will de-insert from the ring. The
watchdog timeout is set to 20 seconds by default, but is adjustable to allow
for circumstances where interrupts are disabled for a long time (increase the
timeout) or the adapter needs to be removed quickly (decrease the timeout).
(5) Troubleshooting
-------------------
Under Windows 95/98, if a message appears saying that the Madge adapter is
not working when the machine is booted, the Madge utility MDGLOG95.EXE can
be run to see details of the error. (See MDGLOG.TXT for more information.)
Under Windows NT, if a Madge adapter fails to start the reason for the
failure is written to the Windows NT event log and can be viewed using the
Windows NT Event Viewer.
(6) Permanently disabling promiscuous mode
------------------------------------------
On Smart 16/4 PCI Ringnode Mk3s, Smart 100/16/4 PCI-HS Ringnodes, Smart
100/16/4 PCI Ringnodes and Smart 100 Fiber PCI Ringnodes it is possible to
permanently disable promiscuous mode by using the Kill_PM parameter. To do
this, put the clause
Kill_PM=1
in the adapter's section of the Windows 95/98 or Windows NT registry. Once the
machine has subsequently been restarted and the driver started on the adapter
the adapter will NEVER again support promiscuous mode.
(7) Using CardBus Adapters With Windows NT4
-------------------------------------------
Windows NT4 has no native support for CardBus adapters. To use a Madge CardBus
adapter with Windows NT4 either a third-party Card Services must be installed
or the internal CardBus enabler built into MDGNDIS4.SYS must be used. The
following third-party Card Services can be used to provide support for CardBus
adapters under Windows NT4:
o Award CardWare for Windows NT
o SystemSoft CardWizard for Windows NT
o Softex PC Card Controller for Windows NT
When installing a CardBus adapter under Windows NT4, the 'Madge Automated
Installation - RECOMMENDED' option can't be used since CardBus adapters can't
be auto-detected under NT4. Instead, select the adapter by name from the
'Select OEM Option' dialog.
If you are using the internal Madge CardBus enabler, you may wish to select
which IO location and interrupt number the CardBus adapter will use if the
default settings clash with another device in the system. This may be tried
if the adapter fails to start after successful installation and reboot.
The IO location and interrupt number of the adapter can be configured through
the Control Panel->Network->Adapters->Properties->Advanced dialog box. The
default interrupt number is 'Automatic' which means the enabler will attempt
to find a free interrupt to use. In this case, if the machine's BIOS has
configured the PCI interrupt routing of the CardBus controller, the
BIOS-selected interrupt will be used. If a different interrupt number is
selected, care must be taken to choose one which is not in use by another
device. IO locations in the region 0x8000 and above are generally free and
should be tried first.
(8) Support for adapter mirroring
---------------------------------
Madge adapter mirroring is a fault-tolerant failover solution for Windows NT4
and is supported by this driver. Mirroring uses a redundant pair of adapters,
with one adapter taking over from the other in the event of a failure.
For more information see the MIRROR.TXT file.
(9) Support for Compaq Hot-Plug PCI
-----------------------------------
This driver contains support for Compaq Hot-Plug PCI under Windows NT4.
Hot Plug PCI is an industry standard scheme to allow standard PCI adapters to
be added and removed (hot- plugged) without powering off the computer. Hot
Plug PCI is aimed at mission-critical servers and allows you to add, remove
and replace PCI adapters without disrupting server availability.
Hot Plug PCI compliant computers contain special hardware enabling individual
PCI slots to be powered on and off independently, allowing you to add or
remove PCI adapters safely with the computer powered on.
Hot Plug PCI can be used in conjunction with Madge adapter mirroring for a
complete fault-tolerant solution.
Hot-Plug PCI support requires that the appropriate vendor (Compaq) supplied
support software is installed on the PC. Refer to the vendor documentation
for more details.
**** End of MDGNDIS4.TXT ****
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.