MDGNDIS5.TXT Driver File Contents (olicom.zip)

The NDIS5 Miniport Driver
=========================
                                                    LSS 7.1(0), September 2000
                                                    --------------------------

Contents
--------

(1) Summary
(2) Driver installation
(3) Driver upgrade
(4) Windows 98/2000 advanced configuration
(5) Troubleshooting
(6) Permanently disabling promiscuous mode
(7) Power management and machine wakeup
(8) Support for adapter mirroring


1) Summary
----------

This file describes the NDIS5 miniport driver MDGNDIS5.SYS. The driver can be
used with the following operating systems:

    o Windows 98
    o Windows 2000

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 2000 installation
-------------------------------
1. Install the adapter into the PC with the power off, then boot the PC
   into Windows 2000.

2. Windows will automatically detect the new adapter and, since all adapters
   in this release are also supported by a driver shipping on the Windows
   2000 CD, will automatically install and start driver for the device.

   To install a new driver the automatically-installed driver must be
   upgraded. See section 3.1 for details.

(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.


(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 2000 upgrade
--------------------------
1. Double-click on the "Network and Dial-up Connections" icon in Control
   Panel

2. Double click on the "Local Area Connection <n>" icon, where <n> is the
   number of the adapter to upgrade.

3. From the "Local Area Connection <n> Status" window, click on "Properties".

4. From the "Local Area Connection <n> Properties" window, click on
   "Configure".

5. Select the "Driver" tab and click on "Update Driver". This will launch the
   "Upgrade Device Driver Wizard". Click "Next" to continue.

6. Check "Search for a suitable driver for my device (recommended)" and click
   on "Next".

7. Check "Specify a location" and click on "Next".

8. At the prompt, type the path to the driver files, e.g "A:\" if they are on
   a floppy disk.
   
9. On the "Driver Files Search Results" page check "Install one of the other
   drivers" and click on "Next".
   
10. On the "Driver Files Found" page, a list of suitable drivers is given.
    Highlight the driver whose location is "a:\netmadge.inf" and click on
    "Next".
    
    If no driver is listed with location "a:\netmadge.inf" but one is listed
    with location "c:\winnt\inf\oem<n>.inf", where <n> is a number, this
    indicates that an upgraded driver has previously been installed. Click
    on the "Back" button multiple times until you get back to stage 6. Delete
    the winnt\inf\oem<n>.inf file and continue from stage 6.

11. If the driver is provided without a digital signature, Windows will
    display a warning. Click on "Yes" to continue.
    
12. Windows will now copy the driver files onto the PC and start the
    driver. Click on "Finish" to complete the upgrade. There is no need to
    reboot.


(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.


(4) Windows 98/2000 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 98   - Choose the 'Network' option from the Control Panel. Highlight
               the Madge adapter in the components list, select 'Properties',
               and then 'Advanced'.

Windows 2000 - Double-click on the "Network and Dial-up Connections" icon in
               Control Panel. Double click on the "Local Area Connection <n>"
               icon, where <n> is the number of adapter to configure. From the
               "Local Area Connection <n> Status" window, click on
               "Properties". From the "Local Area Connection <n> Properties"
               window, click on "Configure". Click on the "Advanced" tab.

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

Network address
---------------
The network address 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

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.

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.

Promiscuous mode support
------------------------
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 just those 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.

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.)

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.

* Note : Since NDIS5 drivers have support for power management and wakeup
  controlled by the OS, this parameter only needs to be used if you wish to
  use Wake-On-LAN functionality on a non-ACPI machine.

Respond to TEST/XID frames
--------------------------
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.

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.

Tx pipeline 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 pipeline 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.

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.

(5) Troubleshooting
-------------------

Under Windows 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 2000, if a Madge adapter fails to start the reason for the
failure is written to the Windows event log and can be viewed using the
Windows Event Viewer. MDGLOG95.EXE can also be used. If the lobe cable is
disconnected, Windows indicates this using an icon on the taskbar.


(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 98 or Windows 2000 registry. Once the
machine has subsequently been restarted and the driver started on the adapter
the adapter will NEVER again support promiscuous mode.

(7) Power management and machine wakeup
---------------------------------------

NDIS5 Miniport drivers have the ability to power manage devices and also
include support for adapters capable of waking the PC from standby when
certain events occur, such a special frame being received. NDIS3 and NDIS4
Miniport drivers do not have this capability, although many implement
MAGIC PACKET(tm) Wake-On-LAN in a proprietary way.

To use the power managment and wakeup features of the NDIS5 Miniport, an
ACPI-compliant PC and suitable adapter are required. The following adapters
are suitable:

    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 Madge 16/4 CardBus Adapter Mk2
    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 GoCard 3250 Token-Ring 16/4 CardBus PC Card

On an ACPI-compliant PC the adapter is able to wake the PC from a standby
state using the PME signal on the PCI bus or using the Wake-On-LAN
connector (optional).

(7.1) NDIS5 wakeup features in detail
-------------------------------------
Windows may ask an NDIS5 Miniport to wake the PC from standby as a result
of any of the following conditions:

    o The lobe cable is disconnected or re-connected.
    o A MAGIC PACKET(tm) frame is received.
    o A network wake-up frame is received.

A "network wake-up" frame is any frame which matches a template passed to the
Miniport by Windows. A template describes data at specific locations in a
frame which must be matched for the adapter to wake the PC. Windows may pass
multiple frame templates to the Miniport. Here are some examples of frame
templates which Windows uses:

    o Any frame addressed to the adapter's node address.
    o Any ARP request frame for the adapter's IP address.
    o Any NBT Name Query/Registration frame for the PC's computer name.

(7.2) Enabling power management and machine wakeup features.
------------------------------------------------------------

Windows 2000 :

1. Double-click on the "Network and Dial-up Connections" icon in Control
   Panel.

2. Double click on the "Local Area Connection <n>" icon, where <n> is the
   number of the adapter to configure.

3. From the "Local Area Connection <n> Status" window, click on "Properties".

4. From the "Local Area Connection <n> Properties" window, click on
   "Configure".

5. Click on the "Power Management" tab. To enable machine wakeup, check the
   box labelled "Allow this device to bring the computer out of standby". To
   enable power management, check the box labelled "Allow the computer to
   turn off this device to save power. Click "OK" to finish.

Windows 98 :

1. Double-click on the "System" icon in Control Panel to open the "System
   Properties" window.

2. Click on the "Device Manager" tab and highlight the adapter in the
   "Network adapters" section.

3. Click on "Properties".

4. Click on the "Power Management" tab. To enable machine wakeup, check the
   box labelled "Allow this device to bring the computer out of standby". To
   enable power management, check the box labelled "Allow the computer to
   turn off this device to save power. Click "OK" to finish.

(8) Support for adapter mirroring
---------------------------------

Madge adapter mirroring is a fault-tolerant failover solution for Windows
2000. Mirroring uses a redundant pair of adapters, with one adapter taking
over from the other in the event of a failure.

This release contains two NDIS5 miniport drivers, one with adapter mirroring
support and one without. Ensure that you install the mirroring NDIS5 miniport
driver if you wish to use this feature.

For more information see the MIRROR.TXT file.


**** End of MDGNDIS5.TXT ****
Download Driver Pack

How To Update Drivers Manually

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.

server: ftp, load: 1.03