Madge Token Ring NDIS Miniport Driver Help

This help covers the following Madge Token Ring NDIS Miniport drivers:

MDGMPORT.SYS (NDIS3)	Supports Windows 95, 98, NT3.51 and NT4

MDGNDIS4.SYS (NDIS4)	Supports Windows 95 (OSR 2 only), 98 and NT4

MDGNDIS5.SYS (NDIS5) 	Supports Windows 98, 2000, and XP

Select from the following for further information:

Supported Adapters

Driver Configuration

Advanced Features

Using MDGLOG95 to view adapter status


Supported Adapters

The following adapters are supported by the Madge NDIS Miniport drivers:

Smart MK4 PCI Adapter

Smart MK4 Low Profile PCI Adapter

Smart 16/4 CardBus Mk2 (See note)

Smart 16/4 PCMCIA Mk2

RapidFire 3140 16/4 TR PCI Adapter

RapidFire 3140V2 16/4 TR PCI Adapter

RapidFire 3141 16/4 PCI Fiber Adapter

GoCard Token-Ring C30 PC Card (OC-3221)

Madge Smart 100/16/4 PCI-HS Ringnode

Madge Smart 16/4 PCI Ringnode Mk3

Madge Smart 16/4 PCI Ringnode Mk2

Madge Presto PCI 2000

Madge Presto PCI Plus

Madge Presto PCI

Madge 16/4 CardBus Adapter (See note)

Madge Smart 16/4 PCMCIA Ringnode

Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter

Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter

Olicom Token-Ring PCI/II 16/4 Adapter (OC-3137)

Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card (See note)

Note: CardBus adapters are not supported under Windows 95 (first edition) or Windows NT3.51. To use CardBus adapters under Windows NT4, the NDIS4 Miniport driver (MDGNDIS4.SYS) must be used.

Note: When installing adapters under Windows NT you should select "Madge Automated Installation - RECOMMENDED" rather than the adapter by name from the 'Select OEM Option' window which is displayed during the add adapter process, unless you are installing a CardBus adapter under Windows NT4. The automated installation will detect any supported adapters in the PC, determine their resources and install them automatically.


Driver Configuration

Windows 95/98 Configuration (NDIS 3/4 driver)

Windows 98/2000 Configuration (NDIS 5 driver)

Windows NT 3.51/4 Configuration (NDIS 3/4 driver)


Windows 95/98 Configuration (NDIS 3/4 driver)

To configure the driver once it has been installed, choose the Network option from the Control Panel, highlight the adapter in the components list, select Properties and then Advanced.

The following adapter properties may be configured:

Network address (LAA)

Ring speed

Maximum frame size

Promiscuous mode allowed

Transfer type

Wake-On-LAN

Warn if no lobe cable

Respond to TEST/XID frames

Mac open mode


Windows 98/2000 Configuration (NDIS5 Driver)

To configure the driver once it has been installed 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 following adapter properties may be configured:

Network address (LAA)

Ring speed

Maximum frame size

Promiscuous mode support

Transfer type

Wake-On-LAN

Respond to TEST/XID frames

Mac open mode

Rx pipeline slots

Tx pipeline slots

Ring status mask

Token ring event mask

Additionally, if you are using a version of the NDIS5 Miniport driver (MDGNDIS5.SYS) which supports adapter mirroring with Windows 2000, the following properties may be configured:

Mirroring group

Mirroring single station timeout

Mirroring beacon timeout

Additionally, if you are using a Wake-On-LAN capable adapter with an ACPI-compliant PC, you can configure the adapter to wake the PC (bring it out of standby) when an event occurs by checking the Allow this device to bring the computer out of standby box on the Power Managment tab in the adapter properties window. If you use this feature you do not have to set the Wake-On-LAN advanced adapter property to Enable - the Wake-On-LAN advanced parameter only needs to be used with the NDIS5 driver if the PC is non-ACPI compliant but does support Wake-On-LAN (using the WoL connector) in which case Windows may not display the Power Management tab in the adapter properties window.


Windows NT3.51/4 Configuration (NDIS 3/4 Driver)

To configure the driver once it has been installed, choose the Network option from the Control Panel, highlight the adapter in the components list, then select Properties.

The adapter properties box is displayed from which you may configure the following:

Network address (LAA)

Ring Speed

To configure advanced properties, click on Advanced to display the advanced properties box, from which you can configure the following:

I/O location

PCI device ID

Interrupt number

Memory window

DMA channel

Tx slots

Rx slots

Transfer type

Respond to TEST/XID

Mac open mode

Promiscuous mode

Quiet mode

Maximum frame size

Ring status mask

Token ring event mask

Watchdog timer

Wake-On-LAN

Under Windows NT4 when using the NDIS4 driver with an adapter which supports adapter mirroring, the following adapter mirroring properties may be configured from the advanced properties box:

Slave PCI Device ID

Ring beacon timeout

Single station timeout


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


PCI device ID

This field will only be displayed for PCI adapters. The field specifies the PCI Device ID of the adapter.


Ring speed

This parameter is used to control the ring speed at which the adapter opens and has four possible values:

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


I/O location

This field will only be displayed for PCMCIA and CardBus adapters. The field specifies the I/O address at which the adapter is located.

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.


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 which is used to retrieve configuration information from the adapter.

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

This value is not needed and will be displayed as 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 you can increase this value.


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 receive buffering you can increase this value.


Transfer type

On some adapters there are several 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.)


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 will slightly reduce the driver CPU utilisation.


Mac open mode

All of the adapters supported by this driver can operate in 'classic' or 'full duplex' (DTR) mode. If you leave this parameter as Default / DTR or Classic, the adapter will open in 'full duplex' mode if it is connected to a switch port that supports 'full duplex' operation, otherwise it will open in 'classic' mode. If you wish to force the adapter to open in a particular mode, set this parameter to Force Classic / Classic only or Force Full Duplex / DTR only.


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.


Ring status mask

This parameter is a bitmask which determines the ring status events that are indicated to protocols by the driver. If you are using the standard Microsoft protocols, do NOT change this parameter from its default value of 0x1D60. The following table lists the events and their corresponding mask bits:

Event	Mask Bit
RING_STATUS_RING RECOVERY	0x0020
RING_STATUS_SINGLE STATION	0x0040
RING_STATUS_COUNTER_OVERFLOW	0x0080
RING_STATUS_REMOVE_RECEIVED	0x0100
RING_STATUS_AUTO_REMOVAL	0x0400
RING_STATUS_LOBE_FAULT	0x0800
RING_STATUS_TX_BEACON	0x1000
RING_STATUS_SOFT_ERROR	0x2000
RING_STATUS_HARD_ERROR	0x4000
RING_STATUS_SIGNAL_LOSS	0x8000


Token ring event mask

This parameter is a bitmask which is used to determine what adapter and network status information is recorded by the driver in the event log and can cause MDGLOG95 to generate alerts. Changing this parameter will not affect the network functionality of the driver. To enable the reporting of a particular event by the driver, the corresponding bit must be set in mask. The following table lists the events and their corresponding mask bits:

Event	Mask Bit
ADAPTER_RESET	0x0002
ADAPTER_OPEN_MODE	0x0004
ADAPTER_CLOSED	0x0008
ADAPTER_DEAD	0x0010
RING_STATUS_SINGLE_STATION	0x0040
RING_STATUS_REMOVE_RECEIVED	0x0100
RING_STATUS_AUTO_REMOVAL	0x0400
RING_STATUS_LOBE_FAULT	0x0800
RING_STATUS_TX_BEACON	0x1000
RING_STATUS_HARD_ERROR	0x4000
RING_STATUS_SIGNAL_LOSS	0x8000
By default, the mask is set to 0x001C which means that ADAPTER_OPEN_MODE, ADAPTER_CLOSED and ADAPTER_DEAD events will be recorded in the event log. All other fatal errors will be reported in the event log regardless of the value of this parameter.


Promiscuous mode

All of the adapters supported by this driver except for Presto PCI and Presto PCI Plus can be used in 'Statistics Gathering' 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.


Quiet mode/Warn if no lobe cable

Normally, when using the NDIS3 or 4 drivers, the driver will fail to start if the machine is booted with the network cable unplugged which will result in an error message being logged or displayed and the driver unloaded. Use this parameter with laptop adapters, such as PCMCIA and CardBus adapters to modify this behaviour as follows:

Quiet mode = Disabled / Warn if no lobe cable = Yes

This is the default state and will result in an error being logged if the driver starts with the network cable unplugged.

Quiet mode = Enabled / Warn if no lobe cable = No

This will prevent an error being logged if the driver starts with the network cable unplugged.

Quiet mode = Enabled (reconnect) / Warn if no lobe cable = No (allow reconnect)

This will prevent an error being logged if the driver starts with the network cable unplugged. The network cable may be reconnected at a later time to gain access to the network.

This parameter is not supported by the NDIS5 driver since this driver will always start successfully even if the network cable is unplugged. Windows displays the network cable state (plugged/unplugged) as a taskbar icon.


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


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.

This parameter can be used to enable WoL when using the NDIS 3 or NDIS 4 driver under Windows 95 or 98, where WoL capability is not supported by the operating system. Packet wake-up (of which WoL is a subset) is fully supported by the Windows 98 and 2000 operating systems when using the NDIS 5 driver, hence this parameter doesn't normally need to be used in this case (the exception is if the PC is WoL capable but not fully ACPI compliant in which case the operating system may not permit the Allow this adapter to bring the machine out of standby box in the Power Management section of the adapter properties dialog to be checked).

The following adapters support Wake-On-LAN:

Smart MK4 PCI Adapter

Smart MK4 Low Profile PCI Adapter

RapidFire 3140 16/4 TR PCI Adapter

RapidFire 3140V2 16/4 TR PCI Adapter

Madge Smart 100/16/4 PCI-HS Ringnode

Madge Smart 16/4 PCI Ringnode Mk3

Madge Presto PCI 2000

Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter

Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter

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.

If this parameter is set to Enabled/PME then in addition to asserting the wake-up signal in the Wake-On-LAN cable the adapter will also assert the PCI Bus PME signal.


Slave PCI Device ID

When using the NDIS4 Miniport driver (MDGNDIS4.SYS) under Windows NT4, to enable mirroring for the current master adapter, a suitable slave adapter must be chosen from the list of PCI device IDs provided. The list is compiled automatically when the Madge Advanced Token Ring Adapter Setup window is opened and only contains the PCI device IDs of adapters which are suitable for use as a slave adapter for the current master. The list therefore only contains the PCI device IDs of adapters which are of the same type as the master, are on the same PCI bus and are not already installed.

Mirroring is disabled by selecting Mirroring Disabled from the list. If no suitable slave adapters were located in the machine, this will be the only option in the list.


Ring beacon timeout

This parameter is only used when mirroring has been enabled.

This parameter can be used to force a mirror switch after the adapter has been transmitting beacon frames for the number of seconds given by the timeout value. In the event of a lobe cable fault, the adapter will beacon before eventually closing - the adapter will not close until several seconds after the cable fault in classic mode. By setting the Ring beacon timeout to a small value, a mirror switch will occur before adapter actually closes, therefore reducing the time before the server regains its network connection.


Single station timeout

This parameter is only used when mirroring has been enabled.

If the hub to which the master adapter is connected loses power or the hub port is accidentally disabled, the hub port may wrap causing the adapter to become a single station without the adapter actually closing. To cause the driver to initiate a mirror switch in this case, the Single station timeout value must be set. The timeout value is the number of seconds to wait while in single station mode before a switch is initiated.


Mirroring Group

This parameter is only used by the adapter mirroring-supporting NDIS 5 Miniport (MDGNDIS5.SYS).

The parameter is used to enable mirroring on an adapter. The value of the parameter identifies which mirrored pair of adapters the adapter belongs to. Both master and slave adapters in the same mirrored pair must have the same Mirroring Group value. If multiple mirrored pairs of adapters are installed, each pair must use a different Mirroring Group value.

If this value is not set (by selecting Not Present) then mirroring is disabled on the adapter.


Advanced Features

The following advanced features are supported by the Madge NDIS Miniport drivers:

Adapter Mirroring

Compaq Hot-Plug PCI (Windows NT4 / MDGNDIS4.SYS only)

Windows NT4 CardBus Support (MDGNDIS4.SYS only)

Network Wakeup / Wake-On-LAN


Adapter Mirroring

Introduction

Adapter mirroring is supported in the following driver and operating system combinations:

•	Windows NT 4 using standard NDIS 4 Miniport driver (MDGNDIS4.SYS)

•	Windows 2000 using special mirroring NDIS5 Miniport driver (MDGNDIS5.SYS)

Mirroring (also known as failover) is a way of providing fault tolerance for Madge network adapters running under Windows NT4 and 2000. Mirroring allows a redundant slave adapter to be installed as a standby for a master adapter. In the event of a problem with the master adapter, such as a lobe cable fault, the driver switches immediately to using the slave adapter. This switch is invisible to both the Windows server and any attached clients. After a mirror switch, the master adapter becomes the slave and vice-versa. The server may contain multiple mirrored pairs of adapters.

A mirror switch is initiated in the following circumstances:

•	if the adapter closes (due to a lobe cable fault, for example);

•	if the adapter fails;

•	it the adapter beacons for longer than the Ring Beacon timeout value;

•	if the adapter remains a single station for longer than the Single Station timeout value.

When a mirror switch occurs, details are recorded in the Windows event log.

Supported Adapters

Mirroring is supported when using the following adapters:

Smart MK4 PCI Adapter

Smart MK4 Low Profile PCI Adapter

RapidFire 3141 16/4 TR PCI Fiber Adapter

RapidFire 3140 16/4 TR PCI Adapter

RapidFire 3140V2 16/4 TR PCI Adapter

Madge Smart 100/16/4 PCI-HS Ringnode

Madge Smart 16/4 PCI Ringnode Mk3.

Madge Smart 16/4 PCI Ringnode Mk2;

Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter

Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter

Olicom Token-Ring PCI/II 16/4 Adapter (OC-3137)

Installation

For instructions on installing and configuring adapter mirroring, see:

Adapter mirroring installation under Windows NT4

Adapter mirroring installation under Windows 2000.

Testing Mirroring

After a mirrored pair of adapters has been installed and the system restarted, it is recommended that the mirroring functionality is tested. A simple test is to remove the lobe cable from the master adapter and verify that the slave adapter opens within a few seconds. Normal network operation should be resumed after the switch has occurred. Should mirroring appear to fail, check the Windows event log for any errors and check that the slave adapter is correctly installed and has its lobe cable attached.

It is recommended that the master and slave adapters are attached to separate hubs where possible to provide protection against hub failure. Note that if the master and slave adapters are attached to switch/hub ports on different rings in a source-routing environment, clients may take longer to reconnect after a mirror switch since the route to the server will have changed and the clients will have to discover the new route.


Adapter Mirroring Installation Under Windows NT4

Mirroring requires a slave adapter to be associated with each master adapter in the computer. A slave adapter must therefore be fitted in the computer for each master adapter which is to be mirrored. Note that the master and slave adapters must be of the same type and must be fitted in PCI slots which are attached to the same PCI bus. Install the driver as follows:

•	Install the master adapter in the usual way - i.e. click on Add... from the Adapters tab in the Network dialog. It is recommended that you chose Madge Automated Installation from the Select OEM Option window when installing the master adapter.

•	Once the master adapter is installed, click on Properties... from the Adapters tab in the Network dialog to display the Madge Token Ring Adapter Setup window.

•	A Locally Administered Node Address (LAA) must be set. The reason for this is that both the master and slave adapters must open with the same node address to make a mirror switch invisible to other computers on the network.

•	Click on Advanced to display the Madge Advanced Token Ring Adapter Setup dialog.

•	To enable mirroring for this adapter, a suitable slave adapter must be chosen from the Slave PCI Device ID list provided in the Mirror Slave Adapter box.

•	You may also configure the Ring beacon timeout and Single station timeout values in the Mirror Slave Adapter box at this point if you wish. These parameters cause a mirror switch to be initiated if the corresponding ring condition persists for the specified period of time.


Adapter Mirroring Installation Under Windows 2000

Mirroring requires a slave adapter to be associated with each master adapter in the computer. A slave adapter must therefore be fitted in the computer for each master adapter which is to be mirrored. Install the driver as follows:

•	Ensure that you have a copy of the Madge NDIS5 Miniport driver (MDGNDIS5.SYS) which supports adapter mirroring.

•	Boot Windows 2000. If the adapters you are using are supported by a driver already on the system (e.g a driver supplied on the Windows 2000 CD), the driver will be automatically loaded. In this case you must upgrade this driver to the new driver by clicking on Update Driver... from the Driver tab on the Properties page for each adapter and following the on-screen instructions. If the adapters you are using are not supported by a driver already on the system, Windows will prompt you to provide a new driver, and you should follow the on-screen instructions to complete the installation.

•	Once the driver is installed for both master and slave adapters, you must enable mirroring by setting the Mirroring group property from the Advanced tab on the Properties pages for both master and slave adapters to the same (non-zero) value. If multiple mirrored pairs of adapters are installed, each pair must be identified by a different Mirroring group value.

•	Also from the Advanced tab, you must specify a Locally Administered Node Address (LAA) for both master and slave adapters using the Network Address property. You must specify the same LAA for both master and slave. The reason for this is that both the master and slave adapters must open with the same node address to make a mirror switch invisible to other computers on the network.

•	You may also configure the Ring beacon timeout and Single station timeout values at this point if you wish. These parameters cause a mirror switch to be initiated if the corresponding ring condition persists for the specified period of time.

•	You must ensure that all other properties are set to the same values for both master and slave adapters, particularly the Maximum frame size, Rx pipeline slots and Tx pipeline slots values.

Once mirroring is enabled for a pair of adapters, only one of the mirrored pair will be open at any time (this is the current master adapter). The driver prevents protocols from using the other adapter by telling them that the network cable is unplugged (you will see the network cable unplugged icon in the taskbar to indicate this). No matter which of the adapter pair is the current master, the driver always tells protocols that the same adapter is unplugged to make mirroring transparent. This means that the adapter pair always uses the protocol configuration of the adapter which is not flagged as unplugged. As an optimisation, you can unbind all protocols from the adapter of a mirrored pair which is flagged as unplugged by un-checking the appropriate boxes in the Properties page of the adapter.


Compaq Hot Plug PCI

The NDIS 4 Miniport driver (MDGNDIS4.SYS) includes 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.


Windows NT4 CardBus Support

The NDIS 4 Miniport driver (MDGNDIS4.SYS) includes support for CardBus adapters under Windows NT4.

Windows NT4.0 has no native support for CardBus adapters. To use a CardBus adapter with Windows NT4.0 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.0:

•	Award CardWare for Windows NT

•	SystemSoft CardWizard for Windows NT

•	Softex PC Card Controller for Windows NT

Installation and configuration

•	If you wish to use a third-party Card Services, ensure that it is installed before attempting to install the Madge CardBus adapter.

•	Boot the machine with a Madge Cardbus adapter in one of the machine's CardBus slots. If you have a third-party Card Services installed, the Madge CardBus adapter may be detected and the 'Network' dialog box displayed. Otherwise open the 'Network' dialog box now.

•	Follow the normal instructions for installing a new adapter until you reach the dialog box which asks you to 'Select Network Adapter' to install. DO NOT select 'Madge Automated Installation' since CardBus adapters cannot be automatically detected under NT4.0. Select the CardBus adapter by name and click OK.

•	The Madge adapter installation software will detect any supported Card Services running on the machine and will prompt for an acknowledgement. If no third-party Card Services is detected, the internal CardBus enabler built into MDGNDIS4.SYS will be used.

•	Installation of the driver will now complete and no further configuration is required.

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

 Usage Notes - Third-Party Card Services

•	Madge does not recommend using Madge Cardbus and Madge PCMCIA network adapters simultaneously under NT4.0.

•	If you experience problems with CardBus adapters using DMA transfer mode, try changing the Transfer Mode to '16-Bit PIO' using the Control Panel->Network->Adapters->Properties->Advanced dialog box (Madge 16/4 CardBus Adapter only).

 Usage Notes - Madge CardBus Enabler

•	The internal Madge CardBus enabler is built into MDGNDIS4.SYS and allows Madge CardBus adapters to be used under Windows NT4.0 without the need for a third-party Card Services to be installed. The enabler supports a wide range of common CardBus controllers and includes generic support for unrecognised controllers.

•	If a CardBus adapter fails to work when using the internal enabler, first look for any errors recorded by MDGNDIS4.SYS in the Windows Event Log. Possible problems include:

Resource clashes. If the IO location or interrupt number selected for the adapter are in use by another device in the system the adapter may fail to work. Try changing the IO location and/or interrupt number in the Control Panel->Network->Adapter->Properties->Advanced dialog box and rebooting the machine.

PC Card controller configuration failure. Some machines have a PC Card (PCMCIA/CardBus) configuration option in their BIOS setup screens. This sometimes allows the controller to be configured to 16-Bit (PCMCIA) only mode OR 16-Bit/CardBus mode. Ensure that CardBus mode is enabled.


Network Wakeup / Wake-On-LAN

Network wakeup refers to the ability of a network adapter to power on the PC in which it is installed when a specific event occurs, such as the receipt of a particular frame. In order to do this the adapter stays powered and inserted into the network while the rest of the PC is powered off. The network adapter signals the wake-up event to the PC either through an auxilliary power (Wake-On-LAN) cable attached to the PC motherboard or using the PCI bus PME (Power Management Event) signal.

The following adapters support both the Wake-On-LAN and ACPI remote wake-up strategies:

Smart MK4 PCI Adapter

Smart MK4 Low Profile PCI Adapter

RapidFire 3141 16/4 TR PCI Fiber Adapter

RapidFire 3140 16/4 TR PCI Adapter

RapidFire 3140V2 16/4 TR PCI Adapter

Madge Smart 100/16/4 PCI-HS Ringnode

Madge Smart 16/4 PCI Ringnode Mk3

Madge Presto PCI 2000

Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter

Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter

Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card

Technologies

Wake-On-LAN

Wake-On-LAN is IBM's initial strategy for remotely powering on and configuring a PC through a network management application. Whereas ACPI's remote wake-up capability utilises the PCI bus PME signal to send the wake-up signal from the LAN connection to the PC system, Wake-On-LAN requires a cable connection inside the PC from the network adapter to the motherboard. Some PC's require Wake-On-LAN support to be enabled in the BIOS configuration before it can be used (refer to your PC manufacturer's documentation).

MAGIC PACKET (tm)

MAGIC PACKET (tm) is a protocol devised by Advanced Micro Devices (AMD) to trigger the remote wake-up of the PC via the network connection. Wake-On-LAN's remote wake-up function relies on the MAGIC PACKET (tm) being transmitted over the network connection to initiate the system wake-up sequence; ACPI can also utilise the MAGIC PACKET (tm), as well as other Power Management techniques. The MAGIC PACKET (tm) will typically be transmitted by a management application running on another computer.

OnNow

OnNow is a Microsoft initiative designed to enable the instant availability of the PC, regardless of its current power state. ACPI-compliance in the PC is a requisite capability for OnNow (ACPI is a broad specification covering many aspects of PC configuration and power management). To achieve this functionality in a networked environment, the PC's network adapter must also be ACPI-compliant.

OnNow specifies that the following events can cause a network adapter to trigger a wake-up signal to turn on the PC:

•	Detection of a change in the network link state (cable plugged/unplugged)

•	Receipt of a network wake-up frame

•	Receipt of a MAGIC PACKET (tm)

Examples of network wakeup frames include an ARP request for the PC's IP address, a NetBIOS Name Query/Registration for the PC's computername or an IP frame directed to the adapter's MAC address.

Operating System/Driver Support

Windows 95, NT3.51 and NT4 have no support for the OnNow/ACPI initiative, whereas Windows 98 and 2000 do.

Windows 95, NT3.51 and NT4

If one of these operating systems is installed on a PC which supports Wake-On-LAN (i.e has a motherboard connector for the network adapter's Wake-On-LAN cable), the network adapter can still be used to wake the machine by enabling the Wake-On-LAN parameter in the NDIS 3/4 Miniport driver's properties. When the operating system is shutdown, the network adapter will go into auxilliary power mode rather than powering off and will trigger a wake-up signal if a MAGIC PACKET(tm) is received to wake the machine.

Windows 98 and 2000

To utilise the OnNow capabilities of these operating systems the NDIS 5 Miniport driver (MDGNDIS5.SYS) must be used in conjunction with an ACPI-compliant network adapter. The operating system is able to tell the NDIS 5 driver which of the three OnNow-specified events the network adapter should use to trigger a wake-up signal.

To enable this feature you must check the Allow this adapter to bring the computer out of standby box in the Power Management section of the adapter properties window. To manually put the PC into standby mode you must select Standby rather than Shutdown from the Shutdown function in the Start menu.


Using MDGLOG95

MDGLOG95 is a utility that allows you to monitor the status of your Madge token-ring adapters. MDGLOG95 supports all Windows operating systems.

To install MDGLOG95 on your machine run the SETUPLOG.EXE program.

MDGLOG95 can be run in two modes: as an ordinary Windows program or as a System Tray program. (Please note that System Tray operation is not possible under Windows NT 3.51.)

As an Ordinary Windows Program

MDGLOG95 is run by choosing the Madge Miniport Status Tool option from the Madge Utilities section of your start menu. The Madge Utilities section is created when you install MDGLOG95 with the SETUPLOG.EXE program.

As a System Tray Program

In this mode MDGLOG95 always runs in the background and continuously monitors your Madge token-ring adapters, and can optionally generate a visible and audible alert when certain events occur. When in System Tray mode a Madge icon will appear on the right-hand-side of your System Tray. Double-clicking on this icon will activate the MDGLOG95 window. To enable System Tray mode, run MDGLOG95 as above and then hit the Configure button. A dialogue box will occur will the following controls:

Display icon in system tray

If this box is checked MDGLOG95 will run in System Tray mode.

Alert on adapter events

If this box is checked MDGLOG95 will generate an alert when any enabled token-ring events or mirror switch occurs.

Flash system tray icon on alerts / Activate window on alerts

These radio buttons allow you to choose what should happen when MDGLOG95 generates an alert. The first option is for the Madge icon on the right-hand-side of your System Tray to flash. The second option is for the MDGLOG95 window to be activated automatically.

Generate a sound on alerts

If this box is checked then MDGLOG95 will play the system exclamation sound when an alert occurs.

MDGLOG95.INI

MDGLOG95 stores its configuration in a file called MDGLOG95.INI that resides in your standard Windows directory (e.g. C:\WINDOWS under Windows95 and WindowsNT and C:\WINNT under Windows NT.) This file contains one section called "[MdgLog95]" and the following parameters:

XPos=n

This parameter specifies that MDGLOG95 will start with the left edge of its window at n on the x-axis.

YPos=n

This parameter specifies that MDGLOG95 will start with the top edge of its window at n on the y-axis.

OnTaskBar=n

If n is 1 then MDGLOG95 will run in System-Tray mode. If n is 0 then MDGLOG95 will run as an ordinary Windows program.

CheckForAlerts=n

If n is 1 then MDGLOG95 will check for token-ring events and generate an alert should one occur. If n is 0 then MDGLOG95 will not check for token-ring events.

AlertDialogue=n

If n is 1 then MDGLOG95 will activate the MDGLOG95 window when an alert occurs. If n is 0 then MDGLOG95 will flash its System Tray icon.

AlertNoise=n

If n is 1 then MDGLOG95 will play the system exclamation sound when an alert occurs.