Copyright: Copyright 1994,1995 Olicom A/S


Windows for Workgroups Version 3.1
Windows for Workgroups Version 3.1.

This file describes the procedure for installing the Driver Disk in Windows For Workgroups Version 3.1.

The installation is done in 4 steps:

1.	Removing any existing Additional Network Support currently running on the network card.

2.	Removing the existing network driver.

3.	Adding the driver from the Driver Disk.

4.	Re-adding any Additional Network Support that will run on the card.


Windows for Workgroups 3.1, Removing Existing Network Support
Windows for Workgroups 3.1, Removing Support for an Additional Network

Perform the following steps if you are using any additional network support besides the basic Windows for Workgroups networking support (such as Novell NetWare or Microsoft LAN Manager).

This step does not delete the network drivers from your hard disk. If you decide to use the network again, you can re-add it.

To remove support for an Additional Network:

1.	In the Control Panel window select the Network icon.

2.	In the Network Settings dialog box select the Networks button.

3.	From the Other-Networks-In-Use list, drag the network type you want to remove into the Available Network Types list. Alternatively, select the network then select the Remove button.

4.	Select the OK button.

5.	A message informing you that the CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI files has been changed, Press the OK button.

6.	In the Network Settings dialog box select the OK button. A message appears asking you to restart your computer. Select the Continue button instead.

For help with the Network Settings and Compatible Networks dialog boxes, select the Help button or press F1 while using the dialog boxes.


Windows for Workgroups 3.1, Removing Card Driver
Windows for Workgroups 3.1, Removing a Network Card Driver

This step does not delete the drivers from your hard disk. If you decide to use the network card later, you can easily re-add the driver.

To remove a network-card driver:

1.	In the Control Panel window select the Network icon.

2.	In the Network Settings dialog box select the Adapters button.

3.	In the Network Adapters dialog box, select the network adapter driver with the driver you want to remove.

4.	Select the Remove button. A dialog box appears asking you to confirm your decision to remove the network-adapter driver. Select the Yes button.

5.	Select the Close button.

6.	A message informing you that Windows for Workgroups will not provide work groups features without a network adapter installed will appear: select the Yes button.

7.	A message appears informing you that the CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI files have been changed. Press the OK button.

8.	**IMPORTANT**: In the Network Settings dialog box, select the OK button. If you do not do this, you cannot be sure that the driver to be added will be read properly from the Driver Disk if you are upgrading an existing Network Driver!!

9.	A message appears prompting you to restart your computer. Select the Continue button instead.

For help with the Network Settings and Network Adapters dialog boxes, select the Help button or press F1 while using the dialog boxes.


Windows for Workgroups 3.1, Adding a Network Card Driver

To add a Network Card driver:

1.	In the Control Panel window select the Network icon.

2.	In the Network Settings dialog box select the Adapters button.

3.	In the Network Adapters dialog box select the Add button.

4.	From the list of network adapters select Unlisted Or Updated Network Adapter, and then select the OK button.

5.	Insert the Driver Disk in drive A, change the path to "a:\" and then select the OK button.

6.	If prompted for the directory where the OCE20ND2.DOS driver is located, enter "A:\MSLANMAN.DOS\DRIVERS\ETHERNET\OCE20" or use the "Browse" function to select this directory. Select "OK". A dialog box appears listing the supported network cards on the disk. Select the "Olicom Ethernet PCMCIA Card" and then select the OK button.

7.	If the list of Network Adapters to Install is empty, it is probably because the network card on the diskette is already installed on the hard disk, and you can select it from the list of network adapters in step 4.

8.	However, if you are upgrading the network adapter driver, you must locate and delete the OEM?.INF file for the network adapter (use a DOS BOX or the File Manager, the file is typically "c:\WINDOWS\SYSTEM\OEM0.INF"). When locating the OEM?.INF file you can use the \MICROSOF\OEMSETUP.INF file on the driver diskette for reference. Before deleting the OEM?.INF (e.g. OEM0.INF) file you must close the Control Panel. Start from step 1 again.

In the settings dialog box for the "Olicom Ethernet PCMCIA Card", all the basic options are set automatically, and cannot be changed.

To change the advanced configuration settings for the network card, select Advanced and then complete the dialog boxes. See "Configuring the NDIS 2.0 MAC Driver" for information regarding setting of the advanced configuration parameters.

However, if you choose to set the Node Address parameter from the dialog box, note that the address must be submitted in the form:

"020001230ABC"

Important:

The quotation marks are essential and must be typed !!!

Also note that if you wish to change the Node Address parameter later on, Windows for Workgroups will have removed the quotation marks, and you must repenter them manually.

9.	In the settings dialog box for your network card, select the OK button.

10.	In the Network Adapters dialog box select the Close button.

11.	A message informing you that the CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI files has been changed, Press the OK button.

12.	In the Network Settings dialog box select the OK button. A message appears prompting you to restart your computer. Select the Continue button instead.

For help with the dialog boxes, choose the Help button or press F1 while using the dialog boxes.


Windows for Workgroups 3.1, (Re)-Adding Support for an Additional Network

If support for an Additional Network (such as Novell NetWare or Microsoft LAN Manager), has been removed, the Windows for Workgroups driver(s) must be installed again for the network.

To add support for an additional network:

1.	In the Control Panel window, select the Network icon.

2.	In the Network Settings dialog box, select the Networks button.

3.	From the Available Network Types list, drag the network type you want to use into the Other-Networks-In-Use list. Alternatively select the network type, then select Add. A dialog box appears, inquiring whether you want to install a new network driver or reuse the one already on your disk. Select the No button to confirm that you do not want to update the driver.

4.	In the Compatible Networks dialog box, select the OK button.

5.	A message informing you that the CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI files has been changed, Press the OK button.

6.	In the Network Settings dialog box, select the OK button. A message appears asking you to restart your computer.

7.	For your changes to take effect, remove any diskette from drive A, and choose the Restart Computer button.

For help with the Network Settings and Compatible Networks dialog boxes, choose the Help button or press F1 while using the dialog boxes.


Installing Multiple Cards
Installing Multiple Network Cards

If you are installing multiple Ethernet Cards in the same computer, remember that the Network Driver must be installed for each card.

If difficulties are encountered, check the settings in the PROTOCOL.INI file for any inconsistencies using a simple text editor like Windows Notepad. If multiple OCE20 drivers are loaded, check that the "IOBASE=" settings are as expected and that the names are OCE20$, OCE202$, OCE203$ etc.


Microsoft Windows for Workgroups 3.11 Overview

Suggested Installation Method

Windows for Workgroups native installation procedure.

Prerequisites

*	Windows for Workgroups 3.11 must be installed on your

computer.

*	The Driver disk must be available.

Driver Installation

With Windows for Workgroups 3.11, use one of the following configurations:

NDIS driver (either version 2.0, 3.0, or both)

ODI driver

NDIS drivers are available in both versions 2.0 and 3.0. NDIS 3.0 drivers run in enhanced mode and are preferable to NDIS 2.0 drivers because they save conventional memory and are faster.

If you need access to a Novell NetWare server you cannot use the NDIS 3.0 driver. Select the ODI driver above.

Configurable Parameters

Configurable parameters for the NDIS driver are found in the PROTOCOL.INI file.

Configurable parameters for the ODI driver are found in the NET.CFG file.

Technical Information

Driver type:  	NDIS 2.0

Driver name:	OCE20ND2.DOS

Driver type:  	NDIS 3.0

Driver name:	OCE2XND3.386

Driver type:  	ODI

Driver name:	OCE2XODI.COM

Error Codes

Error information is available for

PC Card Diagnostics

DOS ODI Driver

Microsoft/IBM NDIS 2.0 MAC Driver

NDIS 20 Driver

NDIS 3.0 Miniport Driver

PCMCIA Card Enabler


Microsoft Windows for Workgroups 3.11 NDIS Installation

The installation is done by adding the drivers from the Driver Disk. You can choose between NDIS 2.0 and NDIS 3.0 drivers.

1.	Open the "Network" window by double-clicking the Network icon.

2.	Select the "Network Setup" icon.

3.	In the "Network Setup" panel click the "Networks..." button.

4.	Select "Install Microsoft Windows Network" and make sure the "No additional network" radio button is selected.

5.	Click the "OK" button or press Enter.

6.	Click the "Drivers..." button.

7.	In the "Network Drivers" panel click the "Add Adapter..." button.

8.	Highlight the "Unlisted or Updated Network Adapter" choice and click the "OK" button.

9.	The setup program prompts you for a vendor-provided network driver disk. Change the path specified to "A:\NDIS30". Insert the Driver Disk in drive A: and click "OK". If the Driver Diskette is located in another directory or another drive, enter the correct path or use the "Browse" function.

10. In the "Unlisted or Updated Network Adapter" panel, select the "Olicom Ethernet OC-2220 PCMCIA Card" and click "OK".

11. If you need to change any driver parameters, highlight the "Olicom Ethernet OC-2220 PCMCIA Card" and click the "Setup..." button in the "Network Drivers" panel.

12. In the "Olicom Ethernet OC-2220 PCMCIA Card" panel you may specify which NDIS driver to use in the "Driver Type" box. Select "Real Mode and Enhanced Mode NDIS Driver" to let Windows for Workgroups 3.11 automatically choose the NDIS driver that matches your configuration and needs.

13. If you want to change any of the parameters for the NDIS drivers, click the "Advanced..." button.

a)	Highlight the parameter you wish to change and enter a value in the box below the parameters or select the "Not present" radio button if the parameter should be omitted from PROTOCOL.INI.

b)	Click the "Set" button when the parameter is correct.

c)	Click the "OK" button when all parameters have been set correctly.

14. You may add additional network drivers and/or protocols in the "Network Drivers" panel.

15. Click the "Close" button when done.

16. If you need to share files and/or printers, change the settings in the "Sharing" panel by clicking the "Sharing..." button. Click "OK" to return from the "Sharing" panel.

17. Click the "OK" button when done.

18. If you installed the network for the first time, you must enter a user name, work group name and a computer name.  Make sure the computer name is unique throughout the network. Click "OK" when done.

19. Setup may require some additional files from your Windows for Workgroups 3.11 distribution disks. Insert these when prompted.

20. Windows for Workgroups 3.11 automatically changes your CONFIG.SYS, AUTOEXEC.BAT, SYSTEM.INI and PROTOCOL.INI files if necessary. Click "OK" to confirm these changes.

21. Select "Restart Computer" to make the changes take effect. Remember to save any unsaved information before restarting the system.

Adapter Parameters

To view or change the adapter parameter settings for the Olicom driver, do the following:

1.	Select the "Network Setup" icon from the Network Window.

2.	Select the "Drivers..." button.

3.	Highlight the adapter you wish to review.

4.	Click the "Setup..." button.

5.	Click the "Advanced..." button.

6.	Highlight the adapter parameter you wish to review.  The value is displayed in the box below the "Advanced Network Adapter Settings" box.

7.	If you need to change a setting, enter the new value in the "Value" field for the proper parameter.

8.	Click the "Set" button to accept the setting.

9.	When all parameters have been set correctly, click the "OK" button. Click the "OK" button in the "Olicom Ethernet OC-2220 PCMCIA Card" panel to return to the "Network Drivers" panel.

10. Click "Close" to exit the drivers panel.

11. Selecting "OK" in the "Network Setup" panel will create a new set of network files, that is, PROTOCOL.INI, SYSTEM.INI, etc. Click "OK". The changes will take effect when you restart your computer.


Microsoft Windows for Workgroups 3.11 ODI Installation

Installing an ODI driver is done in 3 stages:

 -	Removing any existing network from the Windows for Workgroups 3.11 configuration.

 -	Installing the DOS ODI driver

 -	Adding NetWare support in Windows for Workgroups 3.11.

The details are given below.

Removing existing network

From within Windows for Workgroups 3.11 do the following:

1.	Select the "Network Setup" icon in the "Network" window.

2.	Click the "Networks..." button in the "Network Setup" panel.

3.	Click the "No Windows support for networks" button.

4.	Click the "OK" button.

5.	Click the "OK" button in the "Network Setup" panel.

6.	Confirm changes made to AUTOEXEC.BAT, SYSTEM.INI and PROTOCOL.INI, by clicking the "OK" button.

7.	Restart the computer.

Installing the DOS ODI Driver

1.	From within DOS install the OCE2XODI DOS ODI driver as described in the "NetWare DOS Client" section.

2.	Restart your computer.

3.	Make sure you can login to your Novell server.

4.	Start Windows for Workgroups 3.11.

Adding NetWare Support in Windows for Workgroups 3.11

From within Windows for Workgroups 3.11 do the following:

1.	Select the "Network Setup" icon from the Network Window.

2.	In the "Network Setup" panel click the "Networks..." button.

3.	Select "Install Microsoft Windows Network".

4.	Select the "Other" button.

5.	Highlight "Novell NetWare (Workstation Shell 3.x)" or "Novell NetWare (Workstation Shell 4.0 or above)" depending on your NetWare version.

6.	Click the "OK" button.

7.	If the "Novell NetWare" panel is displayed, select "IPXODI.COM and LSL.COM (recommended)".

8.	Click the "OK" button.

9.	Click the "Drivers..." button.

10. In the "Network Drivers" panel click the "Add Adapter..." button.

11. Highlight the "Unlisted or Updated Network Adapter" choice and click the "OK" button.

12. The setup program prompts you for a vendor-provided network driver disk. Change the path specified to"A:\NDIS30". Insert the Driver Disk into drive A: and click "OK". If the Driver Diskette is located in another directory or another drive, enter the correct path or use the "Browse" function.

13. In the "Unlisted or Updated Network Adapter" panel, select the "Olicom Ethernet OC-2220 PCMCIA Card" and click "OK".

14. In the "Network Drivers" panel click the "Close" button.

15. If you need to share files and/or printers, change the settings in the "Sharing" panel by clicking the "Sharing..." button. Click "OK" to return from the "Sharing" panel.

16. Click the "OK" button when done.

17. If you installed the network for the first time, you must enter a user name, work group name and a computer name.  Make sure the computer name is unique throughout the network.  Click "OK" when done.

18. Setup may require some additional files from your Windows for Workgroups 3.11 distribution disks. Insert these when prompted.

19. Windows for Workgroups 3.11 automatically changes your CONFIG.SYS, AUTOEXEC.BAT, WIN.INI, SYSTEM.INI and PROTOCOL.INI if necessary. Click "OK" to confirm these changes.

20. Remove the Driver Disk from drive A:.

21. Select "Restart Computer" to make the changes take effect. Remember to save any unsaved information before restarting the system.

After finishing the installation you may want to inspect the changes made to the system files. Below is shown a simple example of CONFIG.SYS and AUTOEXEC.BAT after the installation described above.

Notice that Windows Network Setup has entered "Lastdrive=z" into the CONFIG.SYS file. If you experience problems logging in to your NetWare server, replace the "Lastdrive=z" entry with it's original value or remove it completely.

Sample CONFIG.SYS :

device=c:\octenabl.dos

DEVICE=HIMEM.SYS

device=emm386.exe NOEMS RAM

dos=high,umb

SHELL=COMMAND.COM /E:1024 /P

files=40

buffers=20

LASTDRIVE=Z

device=c:\windows\ifshlp.sys

Sample AUTOEXEC.BAT :

c:\windows\smartdrv.exe

C:\WINDOWS\net start

PATH c:\;c:\TOOLS;c:\DOS;c:\windows

prompt $p$g

c:\ws\lsl

c:\ws\oce2xodi

c:\ws\ipxodi

C:\WINDOWS\odihlp.exe

c:\ws\netx


The NET.CFG File

Novell NetWare uses a file called NET.CFG to hold certain configuration parameters. A thorough description of these is found in the Novell documentation.

You may wish to set parameters for the Olicom Ethernet GoCard OC-2220.

Below are two sample NET.CFG files:

# Start of NET.CFG

# Two adapters, with both SNAP and 802.2 support

# and with locally assigned node addresses:

Link driver OCE2XODI

   Port 300

   Node address 060011110002

   Frame Ethernet_802.2

   Frame Ethernet_SNAP

Link driver OCE2XODI

   Port 320

   Node address 020011110001

   Frame Ethernet_802.2

   Frame Ethernet_SNAP

# End of NET.CFG

The line "Link driver..." must begin in the first column. Parameters that follow must be indented.


Configuring the NDIS Driver

For an overall introduction to configuring Microsoft's LAN Manager drivers, refer to "Microsoft LAN Manager, Network Device Driver Guide".

For an overall introduction to configuring IBM LAN Server drivers, refer to the IBM publications "LAN Adapter and Protocol Support Configuration Guide" and "IBM LAN Support Program User's Guide".

This file includes information related to managing the OC-2220-related section of the PROTOCOL.INI file.

Required entry:

Drivername = OCE20$ or OCE20<n>$ where <n> is a number from 2 to 9.

Entries in the OC-2220-related section represent the following:

IoBase (OPTIONAL)

Indicate the current I/O address configuration of the Olicom Card Enabler. This setting must match the I/O base address setting of the card. This parameter is used to identify a specific card in a PC configuration with several OC-2220 cards.

Possible values are: 0x200, 0x220, ..., 0x3E0

Interrupt (OPTIONAL)

If present the Adapter is configured by the driver to run with this interrupt. If NOT present the driver will read the interrupt from the Adapter.

Possible values are: 3, 5, 7, 9(2), 10, 11, 14, 15.

Drivername

Identifies the network device driver.  The name should be in uppercase. The possible names are OCE20$, OCE202$, OCE203$, .. OCE209$. The first device driver loaded adopts the name OCE20$, the second loaded adopts the name OCE202$ and so forth.

Netaddress (OPTIONAL)

If present, this value is used as network address instead of the universal address stored on the adapter. The value entered must be unique throughout the LAN and must be a valid locally administered address, for example, "020001230ABC".


Novell SNMP Installation

If you install the NetWare client for DOS/Windows software, you may choose to enable the SNMP module that comes with this package. To do so, select the "Novell SNMP" check box on the Utility Installation dialog.

For proper operation of the SNMP module, configure the following items:

System name

This is a unique name identifying your PC

System location

This is a text describing the location of the PC

System contact person

Your name and contact information, e.g. phone number

Optionally, the following items may be configured by clicking the "Advanced" button:

Monitor community

SNMP monitor community

Control community

SNMP Control community

Enable traps

Enables the transmission of traps

If traps are enabled, you should also configure

Trap Community

SNMP Trap community

Trap address

The IPX address where traps are being sent to. The IPX address consists of the IPX network number and the node address, separated with a colon, for example. "00000001:000083703728". The NetWare command "USERLIST /A" may be used to determine the IPX address for a given user.

For more information about the meaning of the Advanced settings, consult your Novell documentation.


Power Management
Power Management of Olicom GoCards.

The help below applies only to the DOS platform.

DOS only

The Olicom Card enabler OCTENABL.DOS supports power management of the Olicom Ethernet GoCard. The Power Management feature is activated either directly from configuration or in response to a prompt during boot. For DOS-based systems, the Power Management may be extended to include conditional load of network drivers/programs..

The Olicom Card Enabler must be installed to use the power management features. Two drivers, IFOCP.DOS and ENDIFOCP.DOS, and a program, OCPOWER.COM are required. These files prevent the loading of network drivers in CONFIG.SYS, and the starting of network programs in AUTOEXEC.BAT if it has been decided during boot not to power the Olicom GoCard.

Use the following syntax if you have used default installation options. If the destination directory is other than C:\OCUTIL, modify the statements accordingly:

In CONFIG.SYS:

  .

  DEVICE=C:\OCUTIL\IFOCP.DOS

  .

  . All lines placed here will only be executed if the

    adapter is powered.

  .

  DEVICE=C:\OCUTIL\ENDIFOCP.DOS

  .

In AUTOEXEC.BAT:  .

  .

  C:\OCUTIL\OCPOWER

  if ERRORLEVEL 1 GOTO NONET

  .

  . All lines placed here will only be executed if the

    adapter is powered.

  .

  :NONET

DR DOS

The IFOCP.DOS driver does not function in DR DOS versions. It is, however, possible to achieve the same functionality by using the branching facility for CONFIG.SYS. In the branch where the network is not started, insert the line:

DEVICE={path}OCTENABL.DOS AU=4

which will cause a forced power-down of the Olicom GoCard.

In the branch that starts the network you must have the normal load of OCTENABL.DOS. Place the branch that starts the network before the branch that does not start the network otherwise OCCARDCF is unable to configure the PC Card. Do not use this facility to configure the Network Usage with this configuration.


AST PowerExec 3/25SL

Do not configure your Token-Ring GoCard to use interrupt level 7.

Configuration of the Token-Ring GoCard with Phoenix Card Services 1.00 does not work.

Use the Olicom Card Enabler alone or with Socket Services in order to configure the controller, that is, do not load Card Services.


CardWare by Award 2.10 version 1.00

The enabler functions with CardWare if it is installed after PCENABLE.EXE in CONFIG.SYS, as this is the program that supplies resources to Card Services. It is necessary to add Port resources to the CARDWARE.INI file.

If you place the card at address 300h, add the line:

I/O=0x300,0x20,E,10

to the [Resources] part of the CARDWARE.INI file.


Chicony SubNote 486

This notebook uses the TCIC-2/N PCMCIA controller.

Configuration of the Token-Ring GoCard with the Card and Socket Services delivered with the machine does not work. Use the Olicom Card Enabler alone to configure the controller, that is, DO NOT load Card and Socket Services.

Consult the manuals that came with the your notebook for the exact statements to remove.


Compaq Concerto

Do not configure your Token-Ring GoCard to use interrupt level 9.


IBM Port Replicator 1

If IBM Card and Socket Services are not used, the CtrlBase parameter for the Olicom Card Enabler must be specified to 3E2.

To do this, select "Configuration", and press the "Advanced" button. In the text entry field labeled "Controller Base", enter:

3E2

See Configuration for the Card Enabler.


Installation with IBM OS/2 PCMCIA Card Services

By default the NDIS MAC driver for the Olicom Token-Ring GoCard is configured for use with IBM OS/2 Card Services (PCMCIA="Yes" in PROTOCOL.INI).

The OS/2 device driver statements in CONFIG.SYS are important for the GoCard. The correct order is:

Statements	Comments

-----------------------------------------------------------------------------------------------------------------------------------------------------------

DEVICE=C:\OS2\PCMCIA.SYS	Card Services device driver

(or

BASEDEV=PCMCIA.SYS)

.

.

DEVICE=C:\IBMCOM\MACS\OLITOK16.OS2	NDIS MAC driver

.

.

DEVICE=C:\IBM2SS0?.SYS	Socket Services device driver

(or

BASEDEV=IBM2SS0?.SYS)

DEVICE=C:\ICRMU0?.SYS	PCMCIA resource manager

(or

DEVICE=D:\OS2\BOOT\AUTODRV2.SYS  D:\OS2\AUTODRV2.INI	IBM auto configurator

RUN=C:\IBMCOM\MACS\OLITOKD.EXE	NDIS MAC driver demon

NOTE:

Depending on the versions of your operating system, hardware and Card Services, the above statements may vary slightly.

The OLITOKD.EXE NDIS MAC driver demon is a program that must be run, when IBM OS/2 Card Services is being used. It ensures that the Olicom Token-Ring GoCard is operational again after the user has removed and reinserted the GoCard.

Use a text editor (e.g. E.EXE) to ensure the correct driver order in CONFIG.SYS and insert the statement:

RUN=D:\IBMCOM\MACS\OLITOKD.EXE


Installation with Olicom PCMCIA Card Enabler
Installation with Olicom PCMCIA Card Enabler in OS/2

When using the Card Enabler in OS/2, you must configure the NDIS MAC driver for the Olicom Token-Ring GoCard not to use PCMCIA Card Services. Use for instance the LAPS utility to edit the Olicom Token-Ring GoCard parameter "Use PCMCIA Card Services" to "No" or omit the value (PCMCIA="No" in PROTOCOL.INI).

The OS/2 device driver statements in CONFIG.SYS are important for the GoCard. The order must be:

Statement	Comment

-------------------------------------------------------------------------------------------------------------------------------------------

rem DEVICE=C:\OS2\PCMCIA.SYS	Card Services device driver

(or

rem BASEDEV=PCMCIA.SYS)

.

DEVICE=C:\OCTENABL.OS2	Olicom PC Card Enabler

DEVICE=C:\IBMCOM\MACS\OLITOK16.OS2	NDIS MAC driver

.

.

rem DEVICE=C:\IBM2SS0?.SYS	Socket Services device driver

(or

rem BASEDEV=IBM2SS0?.SYS)

rem DEVICE=C:\ICRMU0?.SYS	PCMCIA resource manager

(or

DEVICE=D:\OS2\BOOT\AUTODRV2.SYS  D:\OS2\AUTODRV2.INI	IBM auto configurator

rem RUN=C:\IBMCOM\MACS\OLITOKD.EXE	NDIS MAC driver demon

You must use a text editor (e.g. E.EXE) to ensure the driver order in CONFIG.SYS and insert the "DEVICE=d:\OCTENABL.OS2" statement. Note that no IBM OS/2 PCMCIA drivers are allowed in CONFIG.SYS.

The GoCard will become active when the system is rebooted.


Notebooks - Special Cases

Click on the "hot spots" below for installation instructions for specific brands and models of notebooks as well as for specific brands and versions of Card and Socket Services.

If neither your notebook nor the Card and Socket services you use are listed, use the recommended installation methods in Driver Installation.

Notebooks

AST PowerExec 3/25SL

Chicony SubNote 486

Compaq Concerto

IBM Port Replicator 1

Twinhead SubNote 486SLC

Notebooks with PCMCIA controller (TCIC-2/N) from DataBook

Card and Socket Services

SystemSoft Card Services 2.01 version 4.12

CardWare by Award 2.10 version 1.00


Notebooks using TCIC-2/N PCMCIA Controller
Notebooks using the TCIC-2/N PCMCIA Controller

The Card Interrupt Level must not be set to any of the following values: 9, 11 or 15, as these levels are not supported by the TCIC-2/N PCMCIA (DB86082) controller.


SystemSoft Card Services 2.01 version 4.12

The Olicom Card enabler has been tested with SystemSoft Card Services. The enabler must be installed in CONFIG.SYS after the SystemSoft-supplied resource-table initializer.


Twinhead SubNote 486SLC

This notebook uses the TCIC-2/N PCMCIA controller. Configuration of the Token-Ring GoCard with Award Card Services 1.0 does not work. Use the Olicom Card Enabler alone or with Socket Services in order to configure the controller, that is, do not load Card Services.

The Twinhead SubNote memory window should be set to d0 or d8 for the Olicom Card Enabler:

To do this, select "Configuration", and then press the "Advanced" button. Select "D0" or "D8" from the "Memory Window" list box.

See Configuration, Advanced Enabler Configuration.


Microsoft LAN Manager 2.X (DOS & OS/2)
Installation of Microsoft LAN manager 2.X

The installation is identical for DOS and OS/2.

Install the MAC driver either during or after LAN Manager Installation.

The Olicom Card Enabler must be installed when using the NDIS 2.0 driver for OS/2.

Installing During LAN Manager 2.x Installation

Installing After LAN Manager 2.x Installation

Installing After LAN Manager 2.0 Installation

During installation of the MAC driver, have the following documentation at hand.

   *	MS-DOS User's Guide

   *	Microsoft LAN Manager 2.x Installation Guide

   *	Microsoft LAN Manager 2.x Network Device Drivers Guide


Installing MAC driver During LAN Manager Installation
Installing During LAN Manager Installation (2.X)

1.	Start installation of the LAN Manager and follow the instructions.

2.	When the LAN Manager Setup program has read the standard driver diskettes, you will be prompted for additional diskettes. Select "YES", insert the Driver disk when requested and press <Enter>.

3.	Select "Olicom Ethernet PCMCIA Card" from the menu that appears and press <Enter>.

4.	The MAC driver will then be installed, and can be selected from the driver menu during the subsequent hardware-selection phase.


Installing After LAN Manager 2.x Installation
Installing After LAN Manager Installation (2.X)

1.	Install the LAN Manager and reactivate the Setup program from the LAN Manager directory (for example c:\LANMAN.DOS)

2.	Select "CONFIGURATION" from the system menu and "NETWORK DRIVERS" , "ADD NEW CONFIG" and "OTHER DRIVER" from the pull-down menus.

3.	Insert the Driver disk when requested to insert the network driver diskette, and press <Enter>.

4.	Select "Olicom Ethernet PCMCIA Card" from the menu that appears and press <Enter>. Follow the guidelines in the LAN Manager manuals to complete the installation.

5.	Select the "SAVE" function to update the CONFIG.SYS file with the new driver.


Installing After LAN Manager Installation (2.0)

1.	Install the LAN Manager and reactivate the Setup program from the LAN Manager directory (for example c:\LANMAN.DOS)

2.	Select "ACTIONS" from the menu and "IMPORT NETWORK DRIVERS" from the pull-down menu.

3.	Insert the Driver disk when requested and press <Enter>.

4.	Select "Olicom Ethernet PCMCIA Card" from the menu that appears and press <Enter>.

5.	After the MAC driver has been copied to your hard disk, select "ACTIONS" again and "VIEW/MODIFY" from the pull-down menu.

6.	Select "Olicom Ethernet PCMCIA Card" from the menu during the hardware selection phase and return to the "ACTIONS" menu.

7.	Select the "SAVE" function to update the CONFIG.SYS file with the new driver.


Microsoft Windows 95

Suggested Installation Method

Windows 95 native installation procedure

Prerequisites

  *	Olicom Driver Disk

  *	Windows 95 must be installed

  *	PCMCIA Socket must be installed and enabled (use Device Manager

to verify this)

  *	Windows 95 installation diskettes

Configurable Parameters

Configurable parameters for the NDIS 3.0 Miniport driver are found below.

Technical Information

Driver type:	 	NDIS 3.0 - Miniport

Driver name:	OCE2XM.SYS

Error Messages

Error information is available for:

NDIS 3.0 Miniport driver

Driver Installation

1.	Insert the Olicom Ethernet GoCard in a free PC Card slot.

2.	A "New Hardware Found" window will appear notifying that Windows 95 has found a new network adapter.

The network driver for the Ethernet GoCard is not included in all Windows 95 packages. This gives two possibilities.

2a.	If the network driver is included in the Windows 95 package, Windows 95 will automatically install the network driver.

Restart Windows 95 for the changes to take effect.

If you want to update the driver with the one on the Driver Disk, proceed to the Driver Update section below.

2b.	If the network driver is not included in the Windows 95 package, select "Driver from disk provided by hardware manufacturer" and press <OK>.

Insert the Olicom Driver Disk and press <OK>. If the Driver Disk is located in another directory or drive, enter the correct path.

Follow the Window 95 guidelines to complete the installation.

Restart Windows 95 for the changes to take effect.

Driver Update

If the Olicom Ethernet GoCard driver is included in Windows 95 package, and you want to use the latest enhancements of the Olicom driver, update the network driver with the one on the Olicom Driver Disk.

You may perform a driver update using the Olicom Install Program or the Windows 95 update procedure.

Update using the Olicom Install Program

1.	Run the Olicom Install Program from the Install Disk.

2.	Click the Windows 95 upgrade button and insert the Driver Disk when requested.

3.	Restart Windows 95 for the changes to take effect.

Update using the Windows 95 update procedure

1.	From the "Start" menu, select "Settings", "Control Panel" and "Add/Remove Programs".

2.	Select the Windows "Setup" tab and click the "Have Disk" button.

3.	Insert the Driver Disk in drive A: and press <OK>.

4.	In the "Components" window, select the "Update Miniport Driver" and press the "Install" button.

5.	Press the <OK> button.

6.	Restart Windows 95 for the changes to take effect.

Adapter Parameters

To configure the GoCard, open "Network" in the Control Panel, select "Olicom Ethernet GoCard" and click the "Properties" button.

Click the "Advanced" tab to set the GoCard parameters.

Network address

Use the network address field if you do not want to use the GoCard's burned-in Ethernet address. The value must be a locally administered address, that is of the format X*XXXXXXXXXX.

"X" is any hexadecimal digit, and "*" is either 2, 6, A or E.

If the NDIS 3.0 driver encounters an invalid network address, the invalid address error message is posted.


NDIS 3.0 Miniport Driver Error Messages

The NDIS 3.0 error messages reported under Microsoft Windows for Workgroups 3.11, Microsoft Windows 95 and Microsoft Windows NT are identical. However, the way the errors are reported to the user differs.

Windows for Workgroups 3.11

If you experience any problems with the network or an error occurs while loading the driver, check if any error messages or warnings are posted by the MAC driver by viewing the NDISLOG.TXT file located in the Windows directory. All error messages and/or warnings posted by the Olicom NDIS driver start with "OCE2XM".

Error messages familiar to the system are displayed as:

MS$OCE2XM, Adapter Not Found, 0X00000010, 0X00000000, 0X80405AC0, 0X00000000

These messages are displayed in clear text and are listed below.

If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows for Workgroups 3.11.

Windows 95

In Windows 95 error codes reported by NDIS 3.0 drivers are written to the NDISLOG.TXT file located in your Windows directory.

An example of an error message reported by the NDIS driver could be:

Olicom Ethernet GoCard (0000). Error Code=0XC000138B, 0X00000011, 0X00000000, 0XC0FDA528, 0X00000000

The text "0XC000138B" describes the error and refers to a specific error code, listed below. Ignore the leading "0XC000" (resulting in error code 138B for the example above - Adapter not found).

If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows 95

Windows NT

When running Windows NT, NDIS 3.0 errors are reported using the Event Log. This log can be examined using the Event Viewer located in the Administrative Tools window.

If you experience any problems with the network, check if any error messages or warnings are posted by the driver by using the Event Viewer found in the Administrative Tools window. All error messages and/or warnings posted by the Olicom driver have the Source field set to O100. System error messages, related to the Olicom driver, may occur with different source names, for example "Service Control Manager".

The messages are listed according to Event field and are described below in Event number order. Display the message description by highlighting the message and press enter.

If you experience any problems, write down the "Event ID", "Source", "Description" and "Data" fields in the "Event Detail" window.

NDIS 3.0 Error Messages

For each error message below the first line contains the error code used by Windows 95 and the error message used by Windows for Workgroups 3.11.

The second line contains the "Event ID" and "Data" fields used by Windows NT.

Code  Description

1388  Resource Conflict

5000  OCE2XM: Has encountered a conflict in resources and could not load.

Action: Check the resources used by the network adapter(s) to ensure, that no conflicts exists.

1389  Out of Resources

5001  OCE2XM: Could not allocate the resources necessary for operation

Action: The driver failed to load, because it tried to allocate too many resources. Decrease the number of receive and/or transmit buffers and retry the operation.

138A  Hardware Failure

5002  OCE2XM: Has determined that the adapter is not functioning properly.

Action: The adapter could not be found or is not working properly. Check I/O base settings and retry the operation.

138B  Adapter Not Found

5003  OCE2XM: Could not find an adapter.

Action: The adapter could not be found by the MAC driver. Check I/O base settings and retry the operation. If more than one adapter is used check the EID-parameter.

138C  Interrupt Connect

5004  OCE2XM: Could not connect to the interrupt number supplied.

Action: The interrupt is already used by another device. Change the adapter interrupt number and retry the operation.

138D  Driver Failure

5005  OCE2XM: Has encountered an internal error and has failed.

Action: An internal error has been discovered. Contact your place of purchase.

138E  Bad Version

5006  OCE2XM: The version number is incorrect for this driver.

Action: The driver version is incorrect. Contact your place of purchase.

138F  Time out

5007  OCE2XM: Timed out during an operation.

Action: A time-out error occurred. Contact your place of purchase.

1390  Network Address

5008  OCE2XM: Has encountered an invalid network address.

Action: An invalid network address was specified. Change the locally administered network address and restart your system. The driver uses the burned-in address when loading.

1393  Missing Configuration Parameter

5011  OCE2XM: A required parameter is missing from the Registry.

Action: A parameter necessary for operation has been omitted in the registry. Use the Network Setup to set proper parameters.

1396  Adapter Disabled

5014  OCE2XM: The adapter is disabled. The driver cannot open the adapter.

Action: Make sure the Olicom adapter driver is properly installed. Remove the adapter and install it again using the method described in this help file.

See also the troubleshooting section for further information on how to enable the adapter.

1397  I/O Port Conflict

5015  OCE2XM: There is an I/O port conflict.

Action: The ports used by the MAC driver is already in use by another device. Change the I/O address for the adapter.

1398  Port or DMA Conflict

5016  OCE2XM: There is an I/O port or DMA channel conflict.

Action: Check the I/O address and DMA usage by the adapter to ensure that there is no resource conflicts.

139A  Interrupt Conflict

5018  OCE2XM: There is a interrupt conflict at interrupt number XX.

Action: Change the interrupt selection on the adapter and retry the operation.


Late-Breaking News

Mouse Appearance

When running under DOS with an MS Mouse driver v 8.21 the mouse cursor may not look like a proper arrow. Performance is not affected.

LSP & Windows 3.1

The system may become unstable when the NDIS 2.0 driver is used with the IBM LAN Support Program by an application running in a DOS box under Windows 3.10.

To remove the instability, either execute DOS applications in full-screen mode or execute the application under Windows for Workgroups 3.11.

Changes to the Printed Manual

The following topics will be added to the next release of "Ethernet GoCard" Guide to Operations, OC-2950/2.1, P/N 710001246.

****************************************************************************************

Microsoft Windows 95 Installation

Have the following items and documentation at hand prior to the installation and make sure that the stated installation conditions are met.

*	Olicom Driver Disk

*	Windows 95 must be installed

*	PCMCIA Socket must be installed and enabled (use

Device Manager to verify this)

*	Windows 95 installation diskettes

Driver Installation

1.	Insert the Olicom Ethernet GoCard in a free PC Card slot.

2.	A "New Hardware Found" window will appear notifying that Windows 95 has found a new network adapter.

The network driver for the Ethernet GoCard is not included in all Windows 95 packages. This gives two possibilities.

2a. If the network driver is included in the Windows 95 package, Windows 95 will automatically install the network driver.

Restart Windows 95 for the changes to take effect.

If you want to update the driver with the one on the Driver Disk, proceed to the Driver Update section below.

2b. If the network driver is not included in the Windows 95 package, select "Driver from disk provided by hardware manufacturer" and press <OK>.

Insert the Olicom Driver Disk and press <OK>. If the Driver Disk is located in another directory or drive, enter the correct path.

Follow the Window 95 guidelines to complete the installation.

Restart Windows 95 for the changes to take effect.

Driver Update

If the Olicom Ethernet GoCard driver is included in Windows 95 package, and you want to use the latest enhancements of the Olicom driver, update the network driver with the one on the Olicom Driver Disk.

You may perform a driver update using the Olicom Install Program or the Windows 95 update procedure.

Update using the Olicom Install Program

1.	Run the Olicom Install Program from the Install Disk.

2.	Click the Windows 95 upgrade button and insert the Driver Disk when requested.

3.	Restart Windows 95 for the changes to take effect.

Update using the Windows 95 update procedure

1.	From the "Start" menu, select "Settings", "Control Panel" and "Add/Remove Programs".

2.	Select the Windows "Setup" tab and click the "Have Disk" button.

3.	Insert the Driver Disk in drive A: and press <OK>.

4.	In the "Components" window, select the "Update Miniport Driver" and press the "Install" button.

5.	Press the <OK> button.

6.	Restart Windows 95 for the changes to take effect.

Configuring the NDIS 3.0 Miniport Driver

To configure the GoCard, open "Network" in the Control Panel, select "Olicom Ethernet GoCard" and click the "Properties" button.

Click the "Advanced" tab to set the GoCard parameters.

Network address

Use the network address field if you do not want to use the GoCard's burned-in Ethernet address. The value must be a locally administered address, that is of the format X*XXXXXXXXXX.

"X" is any hexadecimal digit, and "*" is either 2, 6, A or E.

If the NDIS 3.0 driver encounters an invalid network address, the invalid address error message is posted.

NDIS 3.0 Error Messages

In Windows 95 error codes reported by NDIS 3.0 drivers are written to the NDISLOG.TXT file located in your Windows directory.

An example of an error message reported by the NDIS driver could be:

Olicom Ethernet GoCard (0000). Error Code=0XC000138B, 0X00000011, 0X00000000, 0XC0FDA528, 0X00000000

The text "0XC000138B" describes the error and refers to a specific error code, listed below. Ignore the leading "0XC000" (resulting in error code 138B for the example above - Adapter not found).

If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows 95.

See appendix B, Microsoft NDIS 3.0 MAC Driver for a description of the error messages and suggested action.

****************************************************************************************


IBM Card Drivers
IBM Drivers

The IBM Ethernet PCMCIA Drivers are listed below.

LAN Support Program

DOS LAN Services

IBM NTS/2 and IBM  Extended Services

IBM LAN Server


IBM DOS LAN Services

This section describes the procedure for installing the Olicom MAC Driver (NDIS) in IBM DOS LAN Services with the IBM Install Program. The MAC driver for the OC-2220 GoCard can be installed during DOS LAN Services Installation or after DOS LAN Services installation. Olicom recommends that you install DOS LAN Services first and then add the Olicom Ethernet GoCard driver afterwards.

MAC Driver Installation after DOS LAN Services Installation

1.	Start the installation as described by IBM, for example, C:\NET\INSTALL.

2.	Select "Network Card" and press <Enter> to continue.

3.	Select "Change driver for network card" and press <Enter> to continue.

4.	Select "Network card not shown in list below" and press <Enter> to continue.

5.	Insert the Driver diskette in drive A: and specify the location of the OEMSETUP.INF file to be:

A:\IBM\NDIS.DOS

6.	Press Enter to continue.

7.	Select "Olicom Ethernet PCMCIA Card" and - if required - change the default settings for the card by selecting "Edit settings for network card driver".

8.	Select "Driver configuration is correct" and press Enter to continue.

9.	If the install program prompts for "DOS LAN SERVICES DISK 1" to be inserted in drive A:, do not insert the disk. Just press <Enter> to ensure that the correct driver from the Driver diskette is installed.

10. Follow the guidelines given by IBM to complete the installation.

11. The configuration becomes active when the system is rebooted.

MAC DRIVER INSTALLATION DURING DOS LAN SERVICES INSTALLATION

1.	Start the installation as described by IBM, that is, type:

A:\INSTALL

and press <Enter>.

2.	When prompted for the type of network card used, select "Network card not shown in list below" and press <Enter> to continue.

3.	Insert the Drivers Disk in drive A: and specify the location of the OEMSETUP.INF file to be

A:\IBM\NDIS.DOS

4.	Select "Olicom Ethernet PCMCIA Card" and change - if required - the default settings for the adapter by selecting "Edit settings for network card driver".

5.	Select "Driver configuration is correct" and press <Enter> to continue.

6.	Follow the guidelines given by IBM to proceed with the installation.

7.	When the "Installation Complete" screen appears, press <F3> to exit without rebooting.

8.	Copy the driver from the Adapter Driver Diskette to your default DOS Lan Services (e.g. C:\NET) directory by inserting the Drivers disk into drive A: and entering:

COPY A:\IBM\NDIS.DOS\OCE20ND2.DOS C:\NET

9.	Press <Enter> to continue.

10. Reboot your PC to start DOS Lan Services.


IBM LAN Server Overview

Suggested Installation Method

LAN Server native installation procedure.

Prerequisites

*	LAN Server must be installed on your computer. With LAN Server 3.0, this is the IBM LAN Adapter and Protocol Support program (LAPS); with LAN Server 4.0, this is the Multi-Protocol Transport Services (MPTS).

*	Drivers Disk.

Driver Installation

Click on the relevant environment for details of driver installation

LAN Server 2.0

LAN Server 3.0 (LAPS)

LAN Server 4.0 (MPTS)

Configurable Parameters

Configurable parameters are found in the PROTOCOL.INI file.

Technical Information

Driver type:  	NDIS 2.0

Driver name:	OCE20ND2.OS2

Error Codes

See NDIS 2.0 Driver Error Codes for error code information.


IBM LAN Server 2.0 Installation

This section describes how to install the MAC driver for the Olicom GoCard with LAN Server 2.0.

1.	Select "LAN Services Installation/Configuration".

2.	When prompted for "Basic" or "Advanced" installation, select "Advanced".

3.	Select "Install and Configure this Workstation", "Configure a component", "LAN Adapter" and "Protocol Support".

4.	Select "Copy additional network adapter drivers", insert the Drivers disk, and when you are requested to do so, enter the following path to the driver:

A:\IBM\NDIS.OS2

5.	When the network card driver has been copied, select "Configure workstation" and configure your workstation in accordance with your requirements (see the IBM documentation).  See Configuring the NDIS Driver if you want more information about the parameters which may be used for configuring your network driver.

6.	When you have completed the installation and configuration, the following files will have been copied to the \IBMCOM\MACS directory:

OCE20ND2.OS2	driver

OCE20.NIF	network interface file (used by configuration utility)


IBM LAN Server 3.0 (LAPS) Installation

You may choose between installing the Olicom driver while installing LAN Adapter and Protocol Support (LAPS) or after installing LAPS.


Installing Driver while Installing LAPS

Install LAN Adapter and Protocol Support (LAPS) by doing the following:

1.	Insert the "IBM Network Transport Services/2, LAN Adapter and Protocol Support" diskette in drive A, and run the LAPS-program (i.e., A:\LAPS).

2.	Select "Install" in the LAPS program main menu. The program will now install LAPS on your hard disk.

3.	During the installation, the LAPS program main menu will appear again, but with the "Install", "Configure", "Remove", "Exit" and "Help" options selectable.

4.	Proceed with the installation as described in step 2 of Installing the Driver after Installing LAPS.


Installing Driver after Installing LAPS

1.	To run the 'LAN Adapter and Protocol Support' (LAPS) program, make \IBMCOM your current directory and run the LAPS program from that directory.

2.	Select 'Install' in the LAPS program main menu.

3.	A dialog box labeled 'Install Additional Network Drivers' appears, prompting you for a source path. Insert the Driver disk in drive A and type:

A:\IBM\NDIS.OS2

4.	Select OK.

5.	When the 'Installation Complete' message appears on-screen, select OK again.

6.	Select 'Configure' from the LAPS program main menu.

7.	Select 'Configure LAN Transport' in the Configuration dialog box and select Continue.

8.	Select 'Olicom Ethernet PCMCIA Card' under 'Network Adapters' and add it to the 'Current Configuration' by pressing 'Add'.

9.	To edit the adapter parameters select 'Olicom Ethernet PCMCIA Card' in the current configuration list and press 'Edit'.

IMPORTANT:

If you have more than one GoCard in your system, you MUST edit the parameters for the card installed. Edit the "I/O Address" parameter to the value that corresponds to the I/O address of your adapter.

10. Select OK when the parameters for the adapter are correct.

11. Add and configure protocols to suit your requirements.

12. Select OK when the configuration of the LAN transports is complete.

13. Select 'Exit' in the LAPS main menu. Let LAPS update CONFIG.SYS and PROTOCOL.INI on your boot drive by selecting 'Continue'.

14. Follow instructions given by LAPS to complete the installation.

The Card is activated on reboot.


IBM LAN Server 4.0 (MPTS) Installation

You may choose between installing the Olicom driver while installing Multi-Protocol Transport Services (MPTS) or after installing MPTS.


Installing Driver While Installing MPTS

1.	Install MPTS as described by IBM.

2.	At a point during the installation MPTS main menu will appear again, but with the "Exit", "Configure", "Install", "Remove", and "Help" options selectable.

3 	Proceed with the installation as described in step 2 under Installing Driver After Installing MPTS.


Installing Driver After Installing MPTS

1.	Run the "Multi-Protocol Transport Services" (MPTS) program. Make \IBMCOM your current directory (by typing "CD \IBMCOM") and type "MPTS".

2.	Select the "Configure" option in the MPTS main menu.

3.	Select "LAN Adapters and Protocols" and then "Configure".

You are now in the "LAPS Configuration".

You have two options:

a)	Make update with the drivers from your Olicom Driver Diskette.

b)	Use a previously installed "Olicom Ethernet PCMCIA Card".

How to update with driver from Olicom Driver Diskette:

4.	Push the "Other Adapters..." button.

5.	Insert the Olicom Driver Diskette in drive A, enter the path "A:\IBM\NDIS.OS2" and press OK.

How to use a previously-installed adapter:

6.	Select "Olicom Ethernet PCMCIA Card" as your network card, by adding it to the "Current Configuration".

7.	Edit the parameters of the Olicom Ethernet GoCard by first selecting "Olicom Ethernet PCMCIA Card" in the current configuration list and then selecting "Edit".

NOTE:

If you have more than one Ethernet GoCard in your system, set the "I/O Address" parameter for the "Olicom Ethernet PCMCIA Card".

8.	Add and configure protocols to suit your requirements.

9.	Select OK when the configuration of the LAPS configuration complete and select "Close" to end configuration.

10. Select "Exit" in the MPTS main menu and let MPTS update your CONFIG.SYS on your boot drive by selecting "Continue".

11. Follow instructions given by MPTS to complete the installation. The Olicom Ethernet GoCard will become active when the system is rebooted.


IBM LAN Support Program for DOS
IBM LAN Support Program (DOS)

This help section describes the procedure for installing the Olicom MAC Driver (NDIS) in the IBM LAN Support Program with the IBM Installation Aid.

The MAC driver for the NDIS 2.0 environment is exactly the same as that used in the Microsoft Lan Manager environment. Click here for information on driver messages.

Installing the NDIS 2.0 in LAN Support Program - Using IBM Installation Aid

1.	Follow the guidelines described by IBM for "Installing the LAN Support Program" with the Installation Aid, and run the Installation Aid program:

DXMAID

2.	When prompted for possible changes to the "Setup Screen", select YES in the field that asks if you have a driver diskette, and continue the installation.

3.	In the "Process driver" window, you are prompted to "Type changes needed to the drive and directory for DOS NDIS files".

4.	Insert the Driver Disk in drive A: and type:

A:\IBM\NDIS.DOS

5.	In the "Primary Adapter" window select "Ethernet PCMCIA Card"

6.	Press <F5> if you want to change the NDIS driver parameters from default values.

7.	Follow the IBM guidelines to complete the installation.

The MAC driver for your GoCard is now installed in your LSP configuration.

To install the IBM DOS LAN Requester, follow the guidelines given by IBM.


IBM NTS/2 and IBM Extended Services
IBM NTS/2 and IBM Extended Services Overview

Suggested Installation Method

IBM NTS/2 native installation procedure.

Prerequisites

*	IBM NTS/2 (Extended Services) must be installed on your PC.

*	Driver disk.

Driver Installation

See IBM NTS/2 Installation for details about driver installation.

Configurable Parameters

Configurable parameters are found in the PROTOCOL.INI file.

Technical Information

Driver type:  	NDIS 2.0

Driver name:	OCE20ND2.OS2

Error Codes

See NDIS 2.0 Driver Error Codes for error code information.


IBM NTS/2 Installation

This section describes how to install the MAC driver for the adapter with IBM NTS/2 (and IBM Extended Services).

1.	Start the Communication Manager and select "Advanced", "Configuration" and "LAN Adapter and Protocol Support".

2.	Select "Copy additional network adapter drivers".

3.	Insert the Driver disk, and when you are requested to do so, enter the following path to the driver:

A:\IBM\NDIS.OS2

4.	When the network driver has been copied, select "Configure workstation" and configure your workstation in accordance with your requirements (refer the IBM documentation). See Configuring the NDIS Driver if you want more information about the parameters which may be used for configuring your network driver.

5.	When you have completed the installation, the following files have been copied to the \IBMCOM\MACS directory:

OCE20ND2.OS2	driver

OCE20.NIF  	network interface file (used by configuration utility)


Error  Messages

The Error Message help is divided into four sections each describing error messages and return codes that may appear during installation and operation of the Ethernet PCMCIA card and the network operating system or support program. Click on the relevant hot spot for further information on that topic:

PC Card Diagnostics

DOS ODI Driver

OS/2 ODI Driver

Microsoft/IBM NDIS 2.0 MAC Driver

NDIS 20 Driver Error Codes

NDIS 3.0 Driver Error Codes

PCMCIA Card Enabler


PC Card Diagnostics
PC Card Diagnostic Error Messages

Message format:

 12:15:32,0,E, 18 Data Bus Test failed.

where:	12:15:32 is the time

0 is the card number (0 = first card, 1 = second

and so on)

E indicates that it is an error, I for Information

can also appear here

16 is the message number

09 CIS Test	The CIS (Card Information Structure)

of the PCMCIA Card is corrupted.

The Card is faulty.

Contact your place of purchase.

11 CIS Test	The CIS (Card Information Structure)

of the PCMCIA Card didn't contain correct

information.

The Card is faulty.

Contact your place of purchase.

15 TxChip Test. The PCMCIA Card was not able to

perform 16-bit read & write operation.

The Card is faulty.

Contact your place of purchase.

16 TxChip Test. The PCMCIA Card was not able to

perform 32-bit read & write operation.

The Card is faulty.

Contact your place of purchase.

17  82595Tx Chip Test. The PCMCIA Card was not

able to perform initial setup.

The Card is faulty.

Contact your place of purchase.

18  Data Bus Test. (err. no=xxxx) The PCMCIA Card

was not able to read and write all values

(0 - 0xffff) across the data bus.

The data bit has failed: the card is faulty.

Contact your place of purchase.

22  Random Memory Test. (errno=xxxx) The PCMCIA

Card was not able to write and read a

random test-pattern to/from the on-board RAM.

Address data mismatch: the card is faulty.

Contact your place of purchase.

30 IRQ Test. (errno=xxxx)

The PCMCIA Card was not able to generate

interrupt. The test is executed with the card in

'Internal Loop-Back mode'.

0030 Transmit Interrupt missing

0031 (as 0030)

0032 (as 0030)

0033 Rx Interrupt missing

0034 (as 0033)

Possible bad connections.

Check that the network is properly connected.


DOS ODI Driver - Error Messages
DOS ODI Driver Error Messages

The OCE2XODI DOS ODI Driver may generate the following error

messages:

OCE2XODI-DOS-1 The LSL is not loaded.

See the Novell NetWare documentation.

OCE2XODI-DOS-2  The LSL has no more room for a board

using Frame<frame>.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-3  Could not find OCE2XODI driver to unload.

See the Novell NetWare documentation.

OCE2XODI-DOS-4  A TSR is loaded above the OCE2XODI driver.

IPXODI, NETX or VLM are probably loaded. Unload these programs before unloading OCE2XODI. See the Novell NetWare documentation.

OCE2XODI-DOS-5  OCE2XODI MLID could not be unloaded; the

operation was aborted.

As stated.

OCE2XODI-DOS-6  The adapter did not initialize. OCE2XODI

did not load.

Check that the Ethernet GoCard is properly inserted in the socket. If this does not solve the problem, check that all software components are properly installed. Then run the

OC-2220 DIAG program. Consult your place of purchase if the error condition persists.

OCE2XODI-DOS-7  You need another Driver Section Heading in

the NET.CFG file in order to load the LAN driver again.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-8  A NET.CFG is required to load the driver

again.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation  and the Novell NetWare documentation.

OCE2XODI-DOS-9  The following configuration

file entry <entry> was ignored.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-11  The driver does not support frame <frame>.

The protocol keyword has been ignored. Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-12 The protocol keyword must have a frame type.

Entry ignored.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-13 The driver could not register Protocol ID

<ID> for protocol stack <stack> for frame type <frame>.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-14 This version of the LSL is not supported.

As stated.

OCE2XODI-DOS-15 The frame type is already activated

for frame<frame>.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-16 The node address was incorrectly

specified in NET.CFG.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-17 An invalid keyword was specified in

NET.CFG on line <LINE>.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-18 The frame type specified in the NET.CFG

is not supported.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-19 An invalid Ethernet node address is

specified in NET.CFG. The DRIVER modified the incorrect address

bits.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-20 This version of the statistics table is

not supported.

See the Novell NetWare documentation.

OCE2XODI-DOS-21 A program hooked Int 2F after the OCE2XODI

driver.

IPXODI, NETX or VLM are probably loaded. Unload these programs before unloading OCE2XODI.

OCE2XODI-DOS-27 This driver requires LSL version 2.11 or higher.

As stated.

OCE2XODI-DOS-29 The driver did not load.

As stated.

OCE2XODI-DOS-31 A missing or invalid value was specified in the line <LINE>.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-52 Adapter not found.

Check that the Ethernet GoCard is properly inserted in the socket. If this does not solve the problem, check that all software components are properly installed. Then run the

OC-2220 DIAG program. Contact your place of purchase if the error condition persists.

OCE2XODI-DOS-53 Error accessing RAM on PCMCIA Card.

The driver has located an Ethernet GoCard in the system but cannot access its RAM. Check that the Card is properly inserted in the socket. If this does not solve the problem, check that all software components are properly installed. Then run the OC-2220 DIAG program. Contact your place of purchase if the error condition persists.

OCE2XODI-DOS-57 Invalid Burned In Address or checksum.

Run the OC-2220 DIAG program.

Contact your place of purchase if the error condition persists.

OCE2XODI-DOS-59 I/O port address in NET.CFG is invalid.

Locate and fix the error in NET.CFG. See NetWare DOS ODI Installation and the Novell NetWare documentation.

OCE2XODI-DOS-65 Error resetting PCMCIA Card.

The driver has located an Ethernet GoCard in the system but cannot access its control registers.

Check that the Card is properly inserted in the socket. If

this does not work, check that all software components are

properly installed, then run the OC-2220 DIAG Program.

Contact your place of purchase if the error condition persists.

OCE2XODI-DOS-70 INT parameter in NET.CFG not supported

when using Olicom Enabler.

Locate and fix the error in NET.CFG.  See  NetWare DOS ODI Installation  and the Novell NetWare documentation.

OCE2XODI-DOS-71 INT parameter in NET.CFG is invalid.

Locate and fix the error in NET.CFG.  See NetWare DOS ODI Installation and the Novell NetWare documentation.


OS/2 ODI Driver - Error Messages
OS/2 ODI Driver Messages

Adapter not found.

As stated

Error accessing RAM on PCMCIA Card.

As stated

Error accessing RAM on Network Interface Card.

As stated

Adapter must be inserted in a 16 bit slot.

As stated

Invalid Burned In Address or checksum.

As stated

Error resetting PCMCIA Card.

As stated

Error resetting Network Interface Card.

As stated

Error reading serial EEPROM.

As stated

INT parameter in NET.CFG not supported when using Olicom Enabler.

Do not specify any INT when using Olicom Enabler.

INT parameter in NET.CFG is invalid.

The INT parameter must be one supported by OC-2220 series adapter.

INT parameter read from adapter is invalid.

As stated

Error installing interrupt handler.

Change INT settings in NET.CFG file.

I/O port address in NET.CFG is invalid.

The I/O port address must be one supported by OC-2220 series adapter.

This PC has ISA-incompatible IOCHRDY timing.

The adapter cannot be used in this PC. Contact your place of purchase.


Microsoft/IBM NDIS 2.0 MAC Driver Error Messages
Microsoft/IBM NDIS 2.0 MAC Driver

This help describes error messages which may be displayed by the NDIS 2.0 driver, OCE20ND2.DOS, during driver initialization of the Ethernet PCMCIA adapter.

When using the NDIS 2.0 MAC driver with Card and Socket Services alone, that is, when the Olicom Card Enabler is not used, the driver may display messages, which are similar to those used by the enabler. If an error message is not described in this section, see Card Enabler Error Messages.

When you boot your system, a number of messages may be displayed on the screen. Some messages are for information only and some are information about errors.

During driver load, the text:

DOS NDIS 2.0: MAC driver for the Ethernet network, version x.xx, yymmdd.

Copyright 1994-59 Olicom A/S. All Rights Reserved.

is displayed.

The following messages may be displayed by the driver:

OC-2220	MAC driver installed. Using I/O address xxxxx-xxxxx

The driver has been loaded successfully. The I/O addresses used are displayed by the driver, where xxxxx-xxxxx is the I/O address used, for example, 0x300-0x30F.

Failure: Protocol.ini does not have a valid DRIVERNAME

PROTOCOL.INI file is either missing an entry for DRIVERNAME or the DRIVERNAME parameter is not correct in the Ethernet section.

Verify that the line

DRIVERNAME = OCE20$

is present in your PROTOCOL.INI file. See the PROTOCOL.INI file located in the \MSLANMAN.DOS\DRIVERS\ETHERNET\OCE20 directory on the Driver disk.

Failure: Could not find adapter at specified IOBASE.

If the IOBASE keyword is present in the OCE20 section in the PROTOCOL.INI file, the driver will only search for an adapter at the specified I/O address.

If using the Olicom Card Enabler to configure the I/O address used, this value must match the IoBase parameter specified when loading the Enabler.

If using Card and Socket Services without the Enabler, this value is used to specify the I/O address to be used by the PCMCIA card.

If you have more than one OC-2220 GoCard in your machine, you must specify a value for the IOBASE parameter.

Failure: No adapters found.

The NDIS 2.0 MAC driver searches for an adapter at all valid I/O addresses, when no IOBASE parameter is present in PROTOCOL.INI. If no adapters are found at any of the valid I/O addresses, this message is displayed. Verify that you have either Card and Socket services and/or the Olicom Card Enabler installed. Install the Olicom Card Enabler.

Failure: Invalid IOBASE specified in Protocol.ini.

An invalid IOBASE parameter is specified in PROTOCOL.INI. Remove the IOBASE entry in PROTOCOL.INI or change the IOBASE parameter to a legal value. Refer to the

"Failure: Could not find adapter at specified IOBASE"

error message description when inserting the IOBASE parameter in the PROTOCOL.INI file.

Failure: Invalid INTERRUPT specified in Protocol.ini.

An invalid INTERRUPT parameter is specified in PROTOCOL.INI. Remove the INTERRUPT entry in PROTOCOL.INI or change the INTERRUPT parameter to a legal value.

If you are using the Olicom Card Enabler to configure the interrupt used, this parameter should be omitted. If you are using Card and Socket Services without the Enabler, this value is used to specify the interrupt to be used by the PCMCIA card.

The NDIS 2.0 driver for DOS and the Olicom Card Enabler uses several common error messages. If an error message is displayed while the NDIS 2.0 driver is loaded, see the error messages for the Olicom Card Enabler and follow the proposed action.


PCMCIA Card Enabler
Card Enabler Error Messages

Card Service usage error.

Disable the Card Services device statements in CONFIG.SYS and run only the Olicom Enabler. Contact Olicom Support if the error condition persists. This message can only appear under DOS.

Socket Services usage error.

Disable the Socket Services device statements in CONFIG.SYS and run only the Olicom Enabler. Contact Olicom Support if the error condition persists. This message can only appear under DOS.

Unsupported Card Services found.

Disable the Card Services device statements in CONFIG.SYS and run only the Olicom Enabler. Contact Olicom Support if the error condition persists. This message can only appear under DOS.

Unsupported Socket Services found.

Disable the Socket Services device statements in CONFIG.SYS and run only the Olicom Enabler. Contact Olicom Support if the error condition persists. This message can only appear under DOS.

Unsupported ExCA Socket Services found.

Disable the Socket Services device statements in CONFIG.SYS and run only the Olicom Enabler. Contact Olicom Support if the error condition persists. This message can only appear under DOS.

Error getting valid base I/O value.

Make sure that the card configuration does not conflict with other installed devices.

Error setting specified base I/O value.

Make sure that the card configuration does not conflict with other installed devices.

Error setting specified interrupt level.

Make sure that the card configuration does not conflict with other installed devices. No cards found.

WARNING: No card present in slot: X

Specify a different socket (slot) for the Enabler or move the card to another socket.

No known PCMCIA controller found at current controller I/O base.

Contact Olicom Support.

WARNING: MemWindow changed from A0 to D0.

This warning indicates that you may experience problems by using this MemWindow. No further action is required.


Card Enabler

The Olicom Card Enabler is a program that configures the Olicom GoCard and provides access to configuration information.

The PCMCIA standard defines two software components: Socket Services and Card Services.

Socket Services

The Socket Services component provides a standardized interface to the configurable resources of the circuitry (PCMCIA controller) that connects a card to the rest of the system.

Card Services

The Card Services component provides a higher-level, hardware independent, interface for configuration utilities, driver programs, etc.

Both of these components usually come bundled with portable systems. Alternatively generic versions supporting a range of PCMCIA controller hardware can be obtained from independent vendors.

So far, general configuration utilities using Card and Socket Services have presented compatibility problems and have consequently not prevailed. Olicom therefore provides its Card Enabler that can be used until these compatibility issues have been resolved.

The Olicom Card Enabler can be used:

  -	as a stand-alone without Card Services or Socket Services. Most PCMCIA controllers are supported in this configuration and the memory requirements are minimal.

When the Card Enabler is installed alone, it interacts directly with the hardware of your computer.

  -	together with Socket Services v1.x or v.2.x.  PCMCIA controllers not supported by the stand-alone Card Enabler is supported in this configuration.

  -	together with Card  Services and Socket Services.

  -	together with Socket Services, Card Services and a general configuration utility (sometimes called a super client) which configures the card. In this configuration, the Card Enabler does not attempt to configure the card but only provides access to the configuration information.

Installation

DOS/Windows Environment

The Olicom Enabler must always be installed in the DOS environment (Express Installation or manual reconfiguration automatically installs the Card Enabler). Use the Enabler Installation option in the INSTALL program for automatic installation. If you want to make a manual installation proceed with this section.

1.	Insert the Installation disk in one of your floppy drives and copy the file OCTENABL.DOS to your system disk.

Example 1:   If you want to copy the Enabler program to the root of your C: drive, and have inserted the Installation diskette in floppy drive b: enter the following command at the DOS prompt:

COPY  B:\OCTENABL.DOS  C:\

Example 2:   If you want to copy the Card Enabler to a new directory named PCMCIASW on your d: drive and have inserted the Installation disk in floppy drive a: enter the following commands at the DOS prompt:

MD  D:\PCMCIASW

COPY  A:\OCTENABL.DOS  D:\PCMCIASW

2.	Insert the following statement in the CONFIG.SYS file located in the root directory of your system disk (examples are the same as step 1. above).

Example 1:

DEVICE=C:\OCTENABL.DOS

Example 2:

DEVICE=D:\PCMCIASW\OCTENABL.DOS

The statement must be placed after any Card and Socket Service statements and before any Olicom driver statement. If you do not have any Card and Socket Service statements, it is recommended that you insert the statement  before any memory manager statement, as the enabler uses high memory only during initialization.

3.	Boot your machine in order for the installation to take effect. If successfully installed the Enabler will display the socket (A,B, ..,H), the IO address, and the interrupt level and ring speed used by the inserted card. The Enabler will further inform you if the interrupt level used differs from the default value.

Note the socket and interrupt level, since you may need this information later. If the Enabler displays an error message, see Error Messages.

4.	The Enabler will have tried to allocate resources (for example interrupt level) after preference (defaults). If you are not satisfied with the Card Enablers choice, you may force it to use resources after your choice. See Enabler Configuration Parameters for details.

You may now proceed to Card Diagnostics to make sure that your GoCard is functional and not damaged during shipment.

OS/2 Environment

From an OS/2 command line prompt follow the instructions for the DOS/Windows environment, but replace all references to the file OCTENABL.DOS with OCTENABL.OS2.

The OS/2 Enabler cannot be used together with Card and Socket Services. See Installation with Olicom PCMCIA Card Enabler for details.

You may now proceed to Card Diagnostics to make sure that your GoCard is functional and not damaged during shipment.

Enabler Configuration Parameters

The Enabler configuration parameters may be used if you cannot/will not use the Card and Socket Services utility to configure the card.

The Enabler configuration parameters (in the OCTENABL.DOS and OCTENABL.OS2 "device=  " statements in CONFIG.SYS) are selected for a card in a specific socket. Use the socket letter A - H instead of [n] (as used in the table and parameter description) on the command line.

Parameter	Short	Valid Entries	Default

--------------------------------------------------------------------------

AskUser=	AU=	0, 1, 2, 3, 4	0

TimeOut=	TM=	number of seconds	0

IoBase[n]=	B[n]=	200, 220, 240, 260,	A00

300, 320, 340, 360,

A00, A20, A40, A80,

AC0, B00, B40, B80

Irq[n]=	I[n]=	3, 5, 9, 10, 11, 14, 15	5

MemWindow=	MW=	A0, A4, ..., FF	A0

CtrlBase=	CB=	-	3E0

RingSpeed=	RS=	4, 16	on-board

WaitState=	WS=	0, 1, 2, ..., 15	1

DataSize=	DS=	8, 16	16

KeepMem=	KM=	0, 1	0

Example (Configure the card in socket "A" to use I/O base address A40 and interrupt level 3. Prompt the user at boot time for whether he wants to start the network. Wait for five seconds - and if no interaction - continue to boot):

DEVICE=C:\OCTENABL.DOS  BA=A40  IA=3  AU=1  TM=5

Boot Time Parameters

AskUser=

Purpose:  This parameter affects boot events. Valid values are:

0	Card(s) are powered and use configured ring speed.

1	Enabler asks user whether to start network (power cards).

2	Enabler asks user at which ring speed to start network.

3	Enabler asks user whether to start network and at which ring speed.

4	Card(s) not powered, network cannot be used.

Default is 0.

TimeOut=

Purpose:  When AskUser= is set to "1", this parameter is used to specify a maximum number of seconds to wait for the user to press a key. If the user does not act, the network is started.

If the TimeOut= parameter is omitted, no timeout occurs (zero seconds).

Card Configuration Parameters

IoBase[n]=

Purpose:  The I/O port base specifies where the card will be placed. The card will use 32 I/O ports starting at this address.

If the IoBase[n] parameter is not used, the I/O base will be selected in the following order: A00, A40, A80, AC0, B00, B40, B80, A20, 300, 320, 340,360, 200, 220, 240, 260.

Irq[n]=

Purpose:  Specifies the interrupt level used by card.

If the Irq[n] parameter is not used, the interrupt level will be selected in the following order: 5, 3, 10, 11, 9, 14, 15, 7.

Enabler Configuration Parameters

MemWindow=

Purpose:  Unless operating with Card Services the Enabler uses a 4Kbyte memory window during initialization. The MW parameter specifies the location of this window. Valid values are A0-FF for addresses A0000-FF000.

Default is A0 - which is almost never used at boot time.

See also the KeepMem= parameter.

CtrlBase=

Purpose:  This parameter is used when the Enabler configures the PCMCIA controller without Card Services or Socket Services. The parameter specifies the base I/O address of the PCMCIA controller in the system.

Default is 3E0.

RingSpeed=

Purpose: This parameter is used to override the default ring speed set on the card (factory set or set with the SetSpeed utility.

Note:  The ASKUSER parameter can still be used.

WaitState=

Purpose: This parameter is used for setting the hardware wait states on I/O to the GoCard. The parameter is ignored when the enabler is using Socket and Card Services. Use this parameter only if the network drivers or the diagnostics program report errors.

The actual number of wait states depends on the PCMCIA controller in the computer.

DataSize=

Purpose: This parameter is used for setting the I/O data path size to the GoCard.

Use this parameter only if the network drivers or the diagnostics program report errors.

KeepMem=

Purpose: This parameter specifies a 4 Kbyte memory window which is required when you want to change the default (factory set) ring speed on the GoCard using the SetSpeed utility.

Valid values are "0", memory use is disabled, and "1", a 4 Kbyte memory window at default memory address D000 - D0FF is enabled.

The default memory address can be changed, for example "KeepMem=D8".

The "KeepMem=1" definition is only required when changing the ring speed using the SetSpeed program - it can be omitted in all other cases.

When you use the "KeepMem=1" definition, you MUST use the memory manager control to exclude the 4 Kbyte memory window, for example "DEVICE=EMM386.EXE  X=D000-D0FF".


Enabler Installation

The INSTALL program's Enabler Installation option copies the required file(s) and inserts the corresponding statement(s) in the CONFIG.SYS file. The Olicom Card Enabler is required in all DOS and Window environments and in many OS/2 configurations.

See Card Enabler for detailed information about the Olicom Card Enabler and its use.


Configuration

Install's Configuration utility can be used to change the GoCard's default configuration.

Olicom's Card Enabler (configurator) can change parameters from its "Basic" and "Advanced" enabler configuration options.

Basic Configuration covers:

I/O address

Interrupt

Power-on

Ring speed

Advanced Configuration covers:

Memory window

Waitstates

Data size

Controller base

Keep memory window

Other command line options

Basic Configuration

I/O address

The I/O address specifies where the GoCard will be placed. The card will use 32 I/O ports starting at this address. If the I/O address parameter is not specified (default), the I/O base address will be selected in the following order: A00, A40, A80, AC0, B00, B40, B80, A20, 300, 320, 340,360, 200, 220, 240, 260.

Interrupt

Interrupt specifies the interrupt level used by GoCard. If the parameter is not specified (default), the interrupt level will be selected in the following order: 5, 3, 10, 11, 9, 14, 15, 7.

Power-on

The Power-on parameter affects the boot events (the startup sequence). Three options are available:

Yes   The GoCard is powered and you are automatically connected to the network using the configured ring speed.

No    The GoCard is not powered and the network cannot be accessed.

Ask   The Ask parameter is used to specify a maximum number of seconds within which you can stop the boot procedure. If you do not act within this period, you are automatically connected to the network.

Ring speed

The ring speed parameter is used to override the default ring speed set on the card (factory set or set with the RingSpeed utility).

Advanced Configuration

The "Advanced" enabler configuration option adds a number of compatibility parameters:

Memory window

Unless operating with Card Services, the Card Enabler uses a 4Kbyte memory window during initialization. The memory window parameter specifies the location of this window. Valid values are A0 - FF for addresses A0000-FF000.

Default is A0 - an address which is rarely used at boot time.

Waitstates

The waitstate parameter is used for setting the hardware waitstates on I/O to the GoCard. The parameter is ignored when the enabler is using Socket and Card Services.

Use this parameter only if the network drivers or the diagnostics program report errors.

The actual number of waitstates depends on the computer's PCMCIA controller.

Data size

The data size parameter is used for setting the I/O data path size to the GoCard. Use this parameter only if the network drivers or the diagnostics program report errors.

Controller base

Specification of the controller base is used when the Card Enabler configures the PCMCIA controller without Card Services or Socket Services. The parameter specifies the base I/O address of the PCMCIA controller in the system. Default is 3E0.

Keep memory window

This parameter specifies a 4 Kbyte memory window which is required when you want to change the default (factory set) ring speed on the GoCard using the SetSpeed program.

Valid values are "0", memory use is disabled, and "1", a 4 Kbyte memory window at default memory address D000 - D0FF is enabled.

The default memory address can be changed, for example "KeepMem=D8".

The "KeepMem=1" definition is only required when changing the ring speed using the SetSpeed program - it can be omitted in all other cases.

When you use the "KeepMem=1" definition, you MUST use the memory manager control to exclude the 4 Kbyte memory window, enter for example in the CONFIG.SYS file: DEVICE=EMM386.EXE  X=D000-D0FF.

Other command line options

This option is for future use. If for example a new Card Enabler is loaded - with configuration options NOT supported by the present graphical interface - the "Other command line options" field can be used for this purpose.


Where to put the Enabler in CONFIG.SYS

If your computer supports the PCMCIA Card Services specification by loading a driver in CONFIG.SYS, load the Olicom Enabler after the Card Services driver.

If this is not the case, load the Olicom Enabler as early as possible in CONFIG.SYS - before any memory managers (HIMEM.SYS, EMM386.EXE, QEMM386.SYS) - as it uses a modest amount of upper memory for initialization.

The Olicom Card Installation program automatically suggests an appropriate placing for the Enabler line, when the Enabler is installed in CONFIG.SYS.


GoCard Driver Installation

Use the supplied driver installation utilities for alien drivers and Network Interface Cards that come with the network operating system, where possible. However, if no such procedures are available or manual installation is desired, follow the directions in this help to install the driver.

IBM

Novell NetWare Workstations

Microsoft-based Systems

Configuring the MAC Driver

MAC Driver Messages (NDIS 2.0)


Microsoft-based Systems

Whenever possible, use the driver installation utility that came with your Network Operating System. Consult your Network Operating System documentation while using this help on driver installation as a rough guide.

For information about how to install network drivers in a Microsoft environment, select one of the following:

LAN Manager 2.x for DOS

LAN Manager 2.x for OS/2

Windows for Workgroups 3.1

Windows for Workgroups 3.11

Windows 95

Windows NT

Click here for information on NDIS 2.0 MAC Driver Messages


Configuring the MAC Driver (NDIS 2.0)

For an introduction to configuring the LAN Manager Network Drivers, see Microsoft LAN Manager, Network Device Driver Guide.

This help describes how to configure the MAC driver via the PROTOCOL.INI file. The Ethernet GoCard MAC driver, OCE20ND2, is delivered with a PROTOCOL.INI file. During installation this file has been installed in the LAN Manager's DRIVERS directory in a sub-directory called ETHERNET\OCE20.  If the Ethernet GoCard was installed with default configuration and parameters for  NETBEUI or DLC have not been changed, it is not necessary to alter the installed PROTOCOL.INI file.

The PROTOCOL.INI section for OCE20ND2 has one required entry:

drivername = OCE20$

The entries in the OCE20 section as well as the syntax are:

IOBase = [hex value]

NetAddress = "[12 hexadecimal digits]"

Interrupt = [Value]

Valid configuration parameters are:

DriverName

Minimum value: 1 character + $

Maximum value: 7 chars. + $

Default value: OCE20$

I/O Base

Minimum value: 0x200

Maximum value: 0x3E0

Default value: None

NetAddress

Default value: On-card burn-in address

Interrupt

Minimum value: 3

Maximum value: 15

Default value: None


Drivername Parameter
Drivername  =

Purpose: identifies the network driver. The MAC driver name is OCE20$. If installing multiple Olicom Ethernet GoCards, the first network driver must be called OCE20$, the second OCE202$, the third OCE203$ and so forth.


IOBase Parameter
IoBase =

Purpose: Selects the card to be accessed by the  driver module.  This parameter is used if more than one GoCard is installed in the system. If this parameter is omitted the MAC driver will search the I/O range for a card.

If using the Olicom Card Enabler, this value must match the value specified as the IObase parameter for the Enabler.


Interrupt
Interrupt =

Purpose: Selects the interrupt level used by the NDIS 2.0 driver. This parameter is only relevant if  Card and Socket Services are used to configure the card, that is, if the Olicom Card Enabler is not used. This parameter then specifies the interrupt level to use.

If no parameter is specified, the driver will try all valid interrupt levels until an available interrupt is detected.


NetAddress
NetAddress =

Purpose: If this entry is specified, the specified value will be used in place of the universal burned-in node address on the Ethernet GoCard. Note that the entered address must be a valid address (the eleventh (11th) digit from the right must be 2, 6, A or E), for example: NetAddress=021122334455.


MAC Driver  Messages (NDIS2.0)

When the GoCard(s) with MAC driver(s) are installed, a number of messages may be displayed during system initialization. Some messages are for information and some indicate warning conditions or errors.

If an error message is displayed during initialization, see Error Messages and take the suggested action accompanying the message. If the same error message is displayed again, write down the exact wording of the message and contact your place of purchase.

During driver load, one of the following messages is displayed:-

DOS NDIS 2.0: MAC Driver for the Ethernet network, version x.xx, YYMMDD.

Copyright 1994-95 Olicom A/S.  All Rights Reserved.

  or

OS/2 NDIS 2.0: MAC Driver for the Ethernet network, version x.xx, YYMMDD.

Copyright 1994-95 Olicom A/S.  All Rights Reserved.

- depending on the operating system.

If the message

OC-2220 MAC driver installed.  Using I/O address xxxxx-xxxxx.

is displayed, the driver has been loaded successfully. The I/O addresses used are displayed by the driver, where xxxxx-xxxxx are the I/O addresses used, for example, 0x300-0x30F.

If using Card and Socket services directly, that is, if the Olicom Card Enabler is not used, the message line

Using Card and Socket Services.

is displayed immediately following the line above. Note that the Olicom Card Enabler must be used with the OS/2 NDIS 2.0 driver.

If any other message is displayed, it indicates an error condition. See Error Messages for suggested action.


Windows NT Overview
Microsoft Windows NT Overview

Suggested Installation Method

Windows NT native installation procedure.

Prerequisites

*	Olicom Driver Disk

*	Windows NT installation diskettes/CD-ROM

Driver Installation

You can choose to install the adapter driver while you are installing Windows NT or after you have installed  Windows NT. See Microsoft Windows NT Installation for details.

Technical Information

Driver type:  	NDIS 3.0 - Miniport

Driver name:	OCE2XM.SYS

Error Codes

See NDIS 3.0 Miniport Driver Error Messages for error information.


Microsoft Windows NT Installation

The installation procedure for Microsoft Windows NT(TM) and Windows NT(TM) Advanced Server operating systems are the same. Both operating systems will hereafter be referred to as "Windows NT".

During installation of the NDIS 3.0 MAC driver, you may find it convenient to have the Windows NT System Guide at hand. Review the "Configuring the Network" section in chapter 5 and chapter 19, "Installing Windows NT" prior to installation.

The NDIS 3.0 MAC installation procedure described below will copy all necessary set-up files to your Windows NT "System32" directory and the driver to your "System32\Drivers" directory. In addition, several changes will be made to your registry. Do not try to manually change entries in the registry. All MAC driver parameters can be set from the Network control panel.

Installation Procedure

The installation procedure for the NDIS 3.0 MAC driver allows installation either during the initial Windows NT installation or after Windows NT has been installed on your computer. If you have already installed Windows NT on your computer, refer to the "Adding adapter" section.

MAC Installation During Windows NT Installation

1.	Follow the instructions in the Windows NT System Guide to begin Windows NT installation.

2.	If you have selected custom set-up, select "Do Not Detect" when the "Network Adapter Card Detection" window displays, as there is no network card detection module included with the Olicom MAC drivers.

3.	When the message "Set-up did not detect a network card" displays, select "Continue" to go to the adapter card set-up phase.

4	Continue with step 4 in the Adding Adapter section.


Adding Adapter - Windows NT Installation

If you are installing a GoCard after Windows NT has been successfully installed on your system, you must be logged on with administrative rights. This is necessary in order to be able to add, configure and remove network adapters in Windows NT.

1.	Select the Control Panel in the Main window.

2.	Select the Network icon.

3.	In the Network Settings panel, choose the "Add adapter" button.

4.	In the list of Network Adapter Cards, select "<Other> Requires disk from manufacturer" and press the "Continue" button.

5.	Enter the full path to the setup files for the desired adapter type. If you are installing from the setup diskette, enter "A:\".

6.	Confirm choice, by selecting proper adapter type and press the "OK" button.

The setup program now copies installation files to your hard disk.

7.	In the adapter configuration dialogue box, select proper values for adapter settings. Refer to the "Adapter parameters" section below for further details.

8.	Press the "OK" button when all parameters have been set correctly.

The setup program now copies the NDIS 3.0 MAC driver to your hard disk.

9.	You may wish to review the binding settings by selecting the "Bindings" button. Press "OK" to return from the Network Bindings windows.

10.	Select the "OK" button in the Network control panel, when all adapters have been added.

11.	The settings will not take effect, until the system is restarted. If Windows NT is installed on your system, system restart can be initiated by selecting the "Yes" option in the dialogue box shown when you exit the Network Control Panel.

Adapter Parameters

When configuring the Ethernet GoCard, the following parameters can be modified:

*	PC Card I/O Base Address

*	Memory Window

*	Interrupt

*	Bus Number

*	Network Address

Some PCs require additional hardware dependent settings in order to work properly. These parameters are changed using the PC Card Advanced Settings.

PC Card controllers supported are:

PCIC or compatible (for example, Intel)

TCIC or compatible (for example, Databook)

PC Card I/O Base Address

The I/O base address specifies where the PC Card network adapter's I/O ports are located.

Memory Window

During initialization of the PC Card controller, the driver needs a 4 kByte memory window. This parameter specifies the location of the memory window.

Interrupt

This parameter specifies the interrupt level used by the PC Card adapter. For notebooks using the TCIC-2/N PC Card Controller the interrupt level must not be set to any of the values 9, 11 or 15, as these levels are not supported by the TCIC-2/N PC Card (DB86082) controller.

Bus Number

Identifies the bus number, the adapter has been plugged into. For single-bus architectures, this value must be 0 (zero).

Network Address

Use the Network address field if you do not want to use the GoCard's burned-in Ethernet address. The value entered must be a locally administered address, that is of the format "X*XXXXXXXXXX" where "X" is any hexadecimal digit and "*" is either 2, 6, A or E.

If the NDIS 3 driver encounters an invalid network address, the invalid network address error message is posted.

The value entered is verified by the setup program when you click "OK" in the setup dialog box.

For the advanced settings, see the Advanced Settings section


Advanced Settings - Windows NT Installation

The parameters in this section only need to be changed if you experience driver initialization errors even if there are no resource conflicts. The following parameters can be changed:

PC Card Controller I/O Base

Additional Waitstates

Datasize

Any difficulties at this point may be due to your specific type of notebook. See the on-line documentation topic, Notebooks - Special Cases. To disable the PC Card facilities, see the PC Card Controller I/O Base settings.

PC Card Controller I/O Base

In certain notebook configurations it is required to define a special I/O base address for the PC Card controller. an example is the IBM Port Replicator 1 used with an IBM Thinkpad notebook. In this case the PC Card Controller I/O Base must be set to 3E2h. Default PC Card Controller I/O Base is 3E0h for PCIC compatible controllers and 240h for TCIC compatible controllers.

Additional Waitstates

This parameter is used for setting the hardware wait states on I/O to the PC Card. The default value is 0. Change this parameter only if the network driver reports errors. The actual number of wait states depends on the PC Card controller in the computer.

Datasize

This parameter is used for setting the I/O data path size to the PC Card. The default value is 16 bit. Change this parameter only if the network driver reports errors.


Novell NetWare Workstations
NetWare Workstations

Olicom supports two drivers for use in Novell NetWare workstations: one for the NetWare OS/2 Requester (OS/2 ODI driver) and one for NetWare DOS Workstations.

If the Novell NetWare version provides installation support for alien Cards and drivers, use the native NOS installation utility. Otherwise, proceed with the relevant installation.

NetWare DOS ODI Workstation

NetWare OS/2 Requester


NetWare DOS ODI Workstations
NetWare DOS ODI Workstation

Setting up a DOS ODI Workstation can be done with the Express Install procedure.

See VLM Installation for NetWare 3.12 and 4.x workstations.

For other NetWare versions see NETX Installation.


NetWare OS/2 Requester

Important:

The Olicom Enabler must be installed. The OS/2 ODI driver does not work with Card and Socket Services.

The installation procedure for the NetWare OS/2 Requester requires the following software and related documentation:

  *	Novell NetWare Requester for OS/2 v. 1.1 or higher

  *	Olicom Driver Disk

  *	OS/2 v. 1.1 or higher

1.	Install the NetWare Requester for OS/2 on the OS/2 workstation. Refer to "NOVELL NetWare Requester for OS/2 Supplement".

Note:

Steps 2 and 3 need not be taken if OCE2XODI (a "third party" driver) can be installed using the Novell Requester Installation Program. Some versions of the OS/2 Requester Installation Program require that one of the Novell-supplied drivers is loaded. If so, simply choose one at random, and then replace it with the Olicom driver in step 3.

2.	Copy the OCE2XODI.SYS driver to the OS/2 workstation directory that contains the NetWare device drivers:

COPY A:\OS2\OCE2XODI.SYS C:\<path>

(<path> was chosen during NetWare Requester installation)

3.	Insert the following line in CONFIG.SYS to load OCE2XODI.SYS:

DEVICE=C:\<path>\OCE2XODI.SYS

The line must be inserted where the driver (which was inserted during the installation of the OS/2 Requester) is placed. Insert an "rem" in front of the driver supplied by the OS/2 Requester to disable it.

Click here for supplementary information about the NET.CFG file:


Supplementary Information on NET.CFG
Supplementary Information on NET.CFG file

In the OS/2 environment the NetWare modules are configured via the NET.CFG text file. The following information describes the valid configuration options for the OCE2XODI.SYS driver.

The options must be placed under the line that contains the card driver (OCE2XODI):

Link Driver OCE2XODI

options ..

options ..

The first line (Link Driver OCE2XODI) must not have any preceding spaces on the line, whereas the options must be indented one or more spaces.

Sample NET.CFG:

Link Support

Buffers 10 1514

Link Driver OCE2XODI

Frame ETHERNET_802.2

Frame ETHERNET_SNAP

Protocol IPX E0 ETHERNET_802.2

Valid options for the driver are:

Node Address

Frame

Port


VLM Installation
VLM installation (for NetWare 3.12 and 4.x workstations)

The directions below describe how to start the Novell NetWare Install program.

The Install program will:

 *	Create a directory on your computer hard disk

 *	Copy relevant files to that directory

 *	Create a STARTNET.BAT file

 *	Edit the AUTOEXEC.BAT and CONFIG.SYS files as

necessary

1.	Insert the Novell NetWare Client diskette for DOS and type:

A:

INSTALL

2.	You are now prompted to:-

 *	Select a directory in which to install the client files.

Press <Enter> to select the default directory or type the desired directory name.

 *	Let the install utility change the CONFIG.SYS and AUTOEXEC.BAT files as required.

Respond yes when prompted.

 *	Select Windows support if desired

If yes is entered, you are prompted for the Novell WSWIN_1 disk provided by Novell.

 *	Install the driver for the card.

Insert the Driver disk that came with your card

Press <Enter> to copy the Olicom driver

Press <Enter> to select the Olicom OC-2220 Ethernet Card

Option

Press <ESC> to select default settings for the OC-2220 Ethernet card or select a parameter to configure and press <Enter>

 *	Complete the installation by pressing <Enter>.

The program now copies all relevant files and makes appropriate changes to the AUTOEXEC.BAT and CONFIG.SYS files.

The following lines will have been added to the AUTOEXEC.BAT file on the root directory of the C:\ drive.

@CALL C:\NWCLIENT\STARTNET

PATH C:\NWCLIENT\

C:\NET.CFG should be similar to the following:

Link Driver OCE2XODI

NetWare DOS Requester

FIRST NETWORK DRIVE = F

See the Novell documentation provided with the ODI Shell for general information about the NET.CFG file.

C:\NWCLIENT\STARTNET.BAT has been created and contains the following:

@ECHO OFF

C:

CD \NWCLIENT

SET NWLANGUAGE=ENGLISH

LSL

OCE2XODI

IPXODI

VLM

CD \


Keywords recognized by OCE2XODI

The following keywords are recognized by the OCE2XODI DOS ODI driver in the NET.CFG file:

Node Address

Frame

Port

Socket

NoLink

Sample NET.CFG:

Link Support

Buffers 10 1514

Link Driver OCE2XODI

Frame ETHERNET_802.2

Frame ETHERNET_SNAP

Protocol IPX E0 ETHERNET_802.2


Node Address

The network address of the card. Overrides burned-in-address.

When specified, the address must be locally administered, that is, the eleventh (11th) digit from the right must be 2,6, A or E.


Frame

The link level frame type. Supported values are:

Ethernet_802.2 (Default)

Ethernet_802.3

Ethernet_II

Ethernet_SNAP

More than one frame type can be enabled by repeating the parameter on separate lines.


Port
Port  (corresponds to IOBase of Card Enabler)

This is the IO base for the card.

 In the vast majority of cases, this parameter need not be specified as the system allocates an appropriate IO base for the card.  It is only if two or more PCMCIA cards are used with the Olicom Card Enabler that this parameter must be included in every "Link Driver OCE2XODI" entry in NET.CFG where each port parameter in NET.CFG must match an IO Base parameter for the Olicom Card Enabler.  Valid values for the port parameter are the same as for the IO Base for the Olicom Card Enabler.


Socket

This is the only PCMCIA socket to be accepted for the card.

Note that the OS/2 driver does not support the Socket parameter.

In the vast majority of cases this parameter need not be specified, as the driver may accept an Ethernet GoCard inserted into any socket. In some very special cases the user may want to force the driver to only accept an Ethernet GoCard inserted into a specific socket. This could be the case when 2 or more Ethernet GoCards are used in the same PC or if some other application can only run on a subset of the sockets. Valid values for the Socket parameter are the same as for the [n] value for the Olicom Card Enabler, that is a letter from A to H.


NoLink

When this entry is found in NET.CFG the Olicom Ethernet GoCard disables Link integrity Checking and Generation. This may be needed in very special cases when communicating with older, non-standard Ethernet equipment.


NETX Installation
NETX Installation (for NetWare 3.11 Workstations)

This installation requires the following software and related documentation:

  *	Novell NetWare DOS ODI support programs

  *	The Driver disk that came with your Ethernet GoCard

1.	Create a directory on the computer. For example,

MD C:\NET

2.	Copy the following Novell files to the new directory.

LSL.COM

IPXODI.COM

NET3.COM, NET4.COM, NETX.COM or NETX.EXE

With the exception of NETX, these files are located on the Novell WSGEN diskette. NETX is available directly from Novell. Use NET3 with DOS 3.x, NET4 with DOS 4.x and NETX with later versions of DOS. Below, reference is made exclusively to NETX.

3.	Insert the Driver disk in drive A: and copy the OCE2XODI driver to the same directory:

COPY A:\DOS\OCE2XODI.COM C:\NET

4.	Insert the following lines in the AUTOEXEC.BAT file:

CD \NET

LSL

OCE2XODI

IPXODI

NETX

It is important that OCE2XODI is loaded after LSL, but before any protocol stacks (IPXODI, for example).

Other protocol stacks and requesters are possible. See Novell NetWare documentation.

Create a NET.CFG file and enter the desired configuration of the workstation. See the Novell documentation provided with the ODI Shell for general information about the NET.CFG file.

An empty NET.CFG file will work in most cases, yielding the following default values:

One adapter is present, supporting the 802.2 frame type and using the default (burned-in) address.

Click key words for a list of key words recognized by OCE2XODI.


Diagnostics

The diagnostic program (DIAG) is on the Diagnostics diskette. The program can be used with any of the Olicom GoCards.

Use the diagnostics program to:

*   View the current configuration of your GoCard

*   Check the GoCard(s) and the cable(s)

The diagnostics consist of a series of tests that are executed in sequence. It is possible to select specific tests in isolation and alter the test conditions (e.g., the number of test iterations).

Select the tests via menus using either the keyboard or a mouse. The test results are then displayed or optionally written to a file.

Execute the diagnostic program in the following situations:

*   After initial installation

*   After repairs

*   When you suspect a problem

Starting the Diagnostic Program

1.	Make sure that memory managers and Olicom card drivers are NOT loaded when executing the diagnostic program.

2.	Boot the system under DOS. The Enabler driver OCTENABL.DOS must have been installed. See Card Enabler for further information on installation of the Card Enabler.

3.	Insert the Diagnostics disk in the diskette drive.

4.	Make the drive the active drive (here A:) by typing:

A:

and press <Enter>

5.	At the system prompt, type:

DIAG

and press <Enter>.

These steps load and initiate the diagnostic program. First the company logo is displayed, and then the top level menu, the main menu, appears on the screen.

Exiting the Diagnostic Program

You exit from DIAG by selecting "Exit" from the Main Menu.

Interfacing to the Diagnostic Program

The diagnostic program supports both mouse and keyboard operation.

The frame with "Diagnostic Program (Version n.nn)" at the top and the HELP panel at the bottom is displayed while DIAG is active.  Various menus and pop-up windows appear within this frame as you work with DIAG.

HELP Panel

Press <F1> for help on the current option.

Press <ESC> to return to the previous menu.

Press <Enter> to select the highlighted option.

Menus

Use the menus to navigate through DIAG and issue the commands you want DIAG to execute.

The menus consist of lists of commands or options which you can select either by clicking the mouse or by using the arrow keys. The currently selected command/option is highlighted.

Pop-up Windows

DIAG uses pop-up windows to relay information to you. If, for instance, you press <F1> (Help), the help available in the current context is displayed in a pop-up window.

If appropriate, the bottom line in a pop-up window indicates which key to press to make the window disappear.

Running the Diagnostic Program

The main menu has three main options:

Run card Diagnostics

Change Diagnostic Options

View card Configuration

Exit

Run Card Diagnostics

To view a list of the diagnostic tests before you run them, take the following steps.

1.	Use the arrow keys to highlight "Run Card Diagnostics" and press <F1>.

The display appears with a list of the available card diagnostic tests.

2.	To run the diagnostic tests, press <ESC>. This will return you to the main menu with the "Run Card Diagnostics" selection highlighted.

3.	Press <Enter> and a screen with options appears.

To run the whole range of available diagnostic tests, select "Continue with Card Tests" and press <Enter>.

To select individual tests, choose "Change Diagnostic Options" in the main menu.

When you press <Enter>, the diagnostic program lists the installed Olicom GoCard(s) which you can test.  The card(s) can, however, only be detected if the card-enable driver (OCTENABL.DOS) has been installed.

The tests can only be run if the card is enabled, in which case, the Card Configuration Menu has "Card Powered" set to "Yes".

"PCMCIA card is not powered can't be tested" is displayed if the card is disabled and you try to execute the diagnostic program.

4.	Press <Enter> if only one card is found. Otherwise, highlight the card you want to test and press <Enter>.

The diagnostic menu is displayed and the tests to be run are highlighted with "SELECTED".  As the testing progresses, "SELECTED" is replaced by "EXECUTING" while the test is being performed, and finally replaced by "PASSED" if the test has terminated successfully.

If a test fails, the test program stops and an error message appears. Write down the full error message and follow the suggested actions in Error Messages.

Alternatively, you can run the test once again with the option "Diagnostic Log" enabled, and then print out the resulting log file.

Change Diagnostic Options

If you wish to change any of the diagnostic test options, proceed as follows.

1.	Select "Change Diagnostic Options" from the main menu and press <Enter>.

2.	Select "Select/Deselect card tests" if you want to change the existing test sequence.

The tests can be selected and de-selected as required. Use the arrow keys to select the desired test and press <Enter> to toggle between SELECTED and DESELECTED.

Some tests may have an impact on other tests. Therefore, if you deselect one test, other tests may also automatically be deselected. Select "Back" or press <ESC> to return to the "Diagnostic Options" menu.

3.	Select "Enable/Disable diagnostic log"  and use <Enter> to toggle between ON and OFF.

When you select ON, the test results are stored in a text file named DIAGLOG.TXT in your current working directory. Read this file using the next option, "Display log file contents".

Use a standard DOS editor or the "Type" command to view DIAGLOG.TXT.

Select "Back" or press <ESC> to return to "Diagnostic Options".

4.	Select "Number of Open retries". The open retry count determines how many times DIAG will execute the Open Card test. If your network is heavily loaded, or a transient error is present, the Open Card test may fail.

The default value of 4 retries should be sufficient in most environments. If you have difficulties opening the card, you can try to toggle the wrap bit in Open (see step 5).

Select "Back" or press <ESC> to return to the "Diagnostic Options" menu.

5.	Selecting "Set/Reset wrap bit in Open" and use the <Enter> key to toggle between ON and OFF.

When the wrap bit is ON, the card is tested without being electrically inserted into the ring.

When the wrap bit is ON and you are using STP media cabling, the card cable shall only be disconnected at the attachment unit . If you are using UTP media cabling, the card cable must be connected at both ends.

When the wrap bit is OFF, the card cable must be connected to both the card end and to the access unit end. If this is not done, the test responds with an error message.

Select "Back" or press <ESC> to return to the "Diagnostic Options" menu.

6.	Select "Number of test iterations" to enter the number of test rounds you want to execute, and the tests specified as selected in "Diagnostic Options" will be executed in sequence the specified number of times.

Select "Back" or press <ESC> to return to the "Diagnostic Options" menu.

View Card Configuration

Check the card configuration before and after running the diagnostic program.

1.	Highlight the "View Card Configuration" option in the main menu and press <Enter>. The screen then displays the configuration parameters for your card.

2.	Press <Enter> or click on "OK" to return to the main menu.

Exit

Highlight the "Exit" option using the arrow keys and press <Enter>. The diagnostic program is exited and you are returned to the DOS prompt.

This concludes the Card Diagnostics. If you are performing the initial installation and configuration, proceed to Driver Installation.


Adapter Information for Windows (AIW)
Adapter Information for Windows

The Adapter Information for Windows program (AIW) on the Installation diskette displays information about the Olicom adapter itself and the driver currently running. The following information is available:

  *	Adapter type, version, serial number and configuration data

  *	Driver type, version and configuration data

  *	Driver statistics in numeric form

  *	System files

  *	Network traffic in graphic form

  *	How to contact Olicom Support and Sales Division

  *	Other Olicom products

The information is displayed on the screen and can - except for the traffic graph, product information and addresses - be saved in a file.

System Requirements

  *	Microsoft Windows v. 3.1 or higher

  *	An Olicom DMI enabled driver:

OCTOK16.COM (DOS ODI driver) or

OLITOK16.DOS (NDIS 2.0 DOS driver) or

OCTK16.386 (NDIS 3.0 DOS driver)

Installation

Note:	De-activate any Visual Basic program before starting the installation. Once the AIW program is installed, the required Visual Basic programs may be re-activated.

Note:	You may also install AIW by selecting it on the Utility Installation menu

1.	Start Windows by entering:

WIN

2.	Insert the Installation disk and activate Windows’ Program Manager.

3.	Select "Run" from the "File" menu and enter:

A:\AIW\SETUP

4.	Follow the instructions to complete the installation.

The installation process will create a new program group in Windows Program Manager in which the AIW icon is located.

Activation

1.	Double-click on the AIW icon to activate the AIW program. Six large buttons are displayed.

2.	Click on any of the buttons labeled "Hardware", "Software", "System Files", "Statistics", "Adapter Traffic" and "Olicom" to retrieve system information.

3.	For more details about the AIW options, select the "Help" menu.

De-installation

If required, delete the AIW application from the hard disk by manually deleting the files originally installed via the AIW SETUP program.

Files in the installation directory (C:\AIW):

AIW.EXE, AIW.HLP, AIW.INI, OLIAIW.DLL, SETUPKIT.DLL and VER.DLL

Caution:  Be very careful about deleting the following files in the SYSTEM directory! Other programs installed on the computer may also rely on the presence of these files!

Files in the C:\WINDOWS\SYSTEM directory:

VBRUN300.DLL, CMDIALOG.VBX, MSOUTLIN.VBX, PICCLIP.VBX, SPIN.VBX and THREED.VBX


Contacting Olicom

Olicom Offices:

   Australia

   Austria

   Denmark

   France

   Germany

   Italy

   The Netherlands

   Singapore

   South Africa

   Spain

   UK

   USA

Olicom Support Centers:

   Denmark

   USA


Olicom Support - Denmark

Hotline Support: 	(+45) 45 27 01 02

Fax Support: 	  	(+45) 45 27 02 40

BBS Service: 	  	(+45) 45 27 01 00

Internet E-Mail:   	support@olicom.dk

Internet FTP Server:	ftp.olicom.dk

Internet WWW:   	http://www.olicom.dk


Olicom Support - USA

Hotline Support: 	1-800-OLICOM-1 or (+1) 214 516 4638

Fax Support: 	  	(+1) 214 516 0640

BBS Service: 	  	(+1) 214 422 9835

CompuServe:     	GO OLICOM

Internet E-Mail:   	support@olicom.com

Internet FTP Server:	ftp.olicom.com

Internet WWW:   	http://www.olicom.dk


Olicom's Address in Australia

Olicom Australia

Level 6

73-79 Walker Street

North Sydney, NSW 2060

Australia

Tel: 	 (+61) 2 955 1755

Fax:	 (+61) 2 929 5488


Olicom's Address in Austria

Olicom Austria

Regus Business Centre GmbH

Mariahilfer Strasse 123, 3rd Floor

A-1060  Vienna

Austria

Tel: 	 (+43) 1 599 99 107

Fax:	 (+43) 1 599 99 307


Olicom's Address in Denmark

Olicom A/S

Nybrovej 114

DK-2800 Lyngby

Denmark

Tel: 	 (+45) 45 27 00 00

Fax:	 (+45) 45 27 01 01


Olicom's Address in France

Olicom France

20 Esplanade Charles de Gaulle

Rue de Trois Fontanot

F-92000 Nanterre

France

Tel: 	 (+33) 1 46 69 79 69

Fax:	 (+33) 1 47 25 46 48


Olicom's Address in Singapore

Olicom Singapore

331 North Bridge Road

#03-01 Odeon Towers

Singapore 0718

Singapore

Tel: 	 (+65) 339 7221

Fax:	 (+65) 339 1676


Olicom's Address in South Africa

Olicom South Africa

3rd Floor, Price Waterhouse Building

90 Rivonia Road, Sandton

South Africa

Tel: 	 (+27) 11 320 0857

Fax:	 (+27) 11 320 0804


Olicom's Address in Spain

Olicom Iberica

Serrano, 240

E-28016 Madrid

Spain

Tel: 	 (+34) 1 345 72 76

Fax:	 (+34) 1 457 20 79


Olicom's Address in the Netherlands

Olicom The Netherlands

Bolduc Office Centre

Utopialaan 35-N

NL-5232 CD 's-Hertogenbosch

The Netherlands

Tel: 	 (+31) 73 6 491 546

Fax:	 (+31) 73 6 491 545


Olicom's Address in UK

Olicom UK

Suite 10, The Arena

Stockley Park

Uxbridge UB11 1AA

Middlesex

United Kingdom

Tel: 	 (+44) 181 899 1707

Fax:	 (+44) 181 899 1727


Olicom's Address in USA

Olicom USA, Inc.

900 East Park Boulevard

Suite 250

Plano, Texas 75074

USA

Tel: 	 1-800-2-OLICOM

Tel: 	 (+1) 214 423 7560

Fax:	 (+1) 214 423 7261


Olicom's Addresses in Germany

Hamburg Office:

Olicom Germany

Sachsenfeld 2

20097 Hamburg

Germany

Tel: 	 (+49) 40 23505 668

Fax:	 (+49) 40 23505 669

Frankfurt Office:

Olicom Germany

Birkenwaldstrasse 38

63179 Obertshausen

Germany

Tel: 	 (+49) 6104 959 141

Fax:	 (+49) 6104 959 146

Nuernberg Office:

Olicom Germany

Neuwiederstrasse 15

90411 Nuernberg

Germany

Tel: 	 (+49) 911 955 65 06

Fax:	 (+49) 911 52 57 46

Munich Office:

Olicom Germany

Stefan-Georg-Ring 29

D-81929 Munich

Germany

Tel: 	 (+49) 89 939 45013

Fax:	 (+49) 89 930 6898


Olicom's Address in Italy

Olicom Italia

Via Guido D'Arezzo 4

I-20145 Milano

Italy

Tel: 	 (+39) 2 480 094 65

Tel: 	 (+39) 2 480 095 49

Fax:	 (+39) 2 469 49 98


Contents of help file

Help file for OC-2220, version 2.05

  Olicom Ethernet GoCard Help

Select the topic about which you want more information:

Overview of Card Installation	Troubleshooting

The Installation Program   	System Requirements

Express Installation	Notebooks - Special Cases

Driver Installation	Contacting Olicom

Utility Programs 	         	Late-Breaking News


Express Installation

Express Installation is provided for users who want to configure their PC as a Novell DOS ODI workstation using Novell's Virtual Loadable Module (VLM).

The Express Installation installs the files needed to connect to a Novell-based network. Some of the files, those found on the NetWare Client diskette, have been licensed from Novell. You must therefore pay attention to the licensing terms which are displayed during the installation process.

The following diskettes are required for the installation:

*	Olicom Installation, Utilities and Documentation diskette

*	Olicom Novell NetWare Client for DOS and MS Windows diskette

Installation

1.	Insert the Olicom Ethernet GoCard and connect the cable as described in Physical Installation.

2.	Insert the Installation diskette and enter:

A:INSTALL

3.	Select the "Yes" button in the "Welcome to Olicom Install" menu to run the Express Installation (use the mouse or press <Enter>)

4.	Read the Novell Client license agreement and select "Yes" if the terms are acceptable to you. If you do not agree to the license terms, you may return the product for a full refund

5.	You are prompted for the destination directory for the Novell files. If required, you can change the default directory (C:\NWCLIENT). If you intend to access a Novell server from Windows, you should install the Windows support files. Make sure that your Windows directory is correctly specified.

Select "OK" to continue.

6.	The files are then copied from the diskette to your hard disk.

Insert the appropriate diskettes when you are prompted to do so.

7.	When all the files have been copied to the hard disk, some changes are made to your CONFIG.SYS and AUTOEXEC.BAT (and also to your SYSTEM.INI and WIN.INI files if you have accepted Windows support).

When you are asked whether or not you want to automatically login to the NetWare server each time you reboot the PC, "Yes" will add the necessary commands to perform a login on each reboot, whereas "No" will only load the necessary drivers to access the NetWare server.

8.	After installing the Novell files, you may install the required utilities that come with the Olicom GoCard.

9.	Finally, reboot your computer to complete the installation.

The Olicom GoCard is now installed and operational.


File Menu

The File Menu has one item:

Exit     Selecting this item terminates the Olicom Card Installation program.


Help menu

The help menu has the following items

Contents

Displays the help file contents

Installation Overview

Gives an overview of how to install the Olicom Card

Driver Installation

Displays information about driver installation

Contacting Olicom

Tells you how to contact Olicom

About

Gives information about the version of the Installation

program.


Inserting the Olicom Ethernet GoCard
Physical Installation

The information below describes how to install the Olicom Ethernet GoCard in a PCMCIA slot in your computer. See the computer documentation for more detailed information.

Static electricity can be destructive to sensitive components on the card. Discharge yourself by touching a metal part of a grounded unit before removing the card from the anti-static packing bag.

The Ethernet GoCard can be installed WITHOUT powering-off the computer.

1.	Select a free PC Card socket. The socket must be able to hold a PCMCIA type II card. See the computer documentation to see which card types are supported. The Olicom Ethernet GoCard is a Type II card.

2.	Insert the Ethernet GoCard in the socket. The end of the card with the broadest connector goes into the computer. If the card resists insertion, pull it out, rotate it 180 degrees and reinsert it. Not all computer manufacturers have agreed to the same orientation of the connector inside the socket.

3.	Connect one end of the supplied cable to a network cable or to a network outlet.

4.	Fit the connector to the Ethernet GoCard. It has a half-moon latch to secure the connection. Align the hooks of the connector with the corresponding holes in the Ethernet GoCard and push it gently into position. If it resists insertion, rotate it 180 degrees and try again.

Before continuing the installation, have the following items at hand:

*	The computer documentation

*	The computer operating system documentation (DOS,

Windows)

*	The Network Operating System documentation and

software

*	This Guide to Operations

*	The Install and Utility disk

*	The Drivers and Diagnostics disk


Installation Overview
Overview of Card Installation

The installation procedure comprises the following steps:

1.	Physically inserting the Ethernet GoCard in the computer PCMCIA slot and connecting the appropriate cables.

2.	Configuring the card by installing the Olicom Enabler.

3.	Installing the Network Card driver software

4.	Logging onto the network. See your network documentation for details.

The Olicom GoCard has been tested and found fully operational. However,  run the Diagnostic Program to check that nothing has been damaged during shipment.

You may also wish to install the Olicom Card Utilities software

If you want to connect as a Novell NetWare workstation and are running from a DOS platform, you can run the Express Installation.

Before starting the installation, have the following material at hand:

*	The computer documentation

*	The computer Operating System documentation (DOS,

Windows, OS/2, etc.)

*	The Network Operating System documentation (NetWare,

LAN Manager, etc.)

*	The Guide to Operations

*	The Drivers and Diagnostics disk

Some Notebooks require special configuration of the Olicom Enabler. Click here for a list of these notebooks.


Installation Program
Olicom Card Installation Program

The Olicom Card Installation Program (Install) helps you to configure your Olicom PCMCIA card, and to install the necessary software.

The Olicom Card Installation Program runs under DOS or Windows.

The following options are available when running Install:

/mono

The program will attempt to accommodate a monochrome display (DOS version only).

/express

Launch Express Install.

/custom

Do not launch Express Install.

/root=<path>

Use this option to change the disk/directory that external programs are loaded from. The Express Install routine uses, by default, the root directory of the disk from where the Olicom Install program is run. This is inconvenient if the Olicom program has been copied to the hard disk as the Novell Install program must be run from a floppy disk.

When you start the Olicom Card Installation program and if you decide not to use the Express Installation feature, the main menu is displayed. It has seven buttons and three menus. The buttons are labeled:

Installation Overview

Enabler Installation

Configuration

Utility Installation

Express Install, NetWare Client

Exit

The menus are

File

Sockets

Help


Novell Client Installation

Perform a Novell Client Installation (Express Installation) if you want to configure your PC as a Novell DOS ODI workstation using Novell's VLM (Virtual Loadable Module).

The Express Installation will use the default card configuration and prompt you to insert the appropriate Olicom diskettes.


Sockets menu

The Sockets menu contain a list of all the card sockets on your PCMCIA computer, and the Olicom cards that were detected in them.

Selecting an item from this menu lets you configure options for this particular card.

Note:

If the Olicom Enabler is not installed, the detection of Olicom Cards may not be completely reliable.


System Requirements

Installation of the Ethernet GoCard requires:

*	A computer with a free PCMCIA Type II or Type III slot

*	One of the following I/O address ranges must be free:

200-20F, 210-21F, 220-22F, 230-23F, 240-24F, 250-25F, 260-26F, 270-27F, 280-28F, 290-29F, 2A0-2AF, 2B0-2BF, 2C0-2CF, 2D0-2DF, 2E0-2EF, 2F0-2FF, 300-30F, 310-31F, 320-32F, 330-33F, 340-34F, 350-35F, 360-36F, 370-37F, 380-38F, 390-39F, 3A0-3AF, 3B0-3BF, 3C0-3CF, 3D0-3DF, 3E0-3EF, 3F0-3FF

*	One of the following interrupt levels must be free:

3, 5, 7, 9, 10, 11, 14, 15

*	Socket Services 1.x (optional)

*	Card and Socket Services 2.x (optional)

*	Free memory capacity to load the Ethernet GoCard driver with Novell NetWare, IBM or Microsoft workstation software. See the relevant network operating system (NOS) documentation for the exact memory requirements.

*	MS-DOS v. 3.3 or higher - for Novell NetWare DOS workstation environments

OS/2 v. 1.x or higher - for Novell NetWare IS/2 Requester environments

MS-DOS v. 3.3 or higher - for IBM PC LAN Program environments

MS-DOS v. 3.2 or higher - for Microsoft DOS Lan Manager environments

MS-OS/2 v. 1.0 or higher - for Microsoft OS/2 Lan Manager environments

IBM-OS/2 v. 2.0 or higher  for IBM Lan Server/Extended Services environments


Troubleshooting

If you encounter a problem with your OC-2220 GoCard, use the diagnostics program DIAG to isolate and resolve the problem.

Some notebook brands and models require special instructions for installation and configuration. See Notebooks - Special Cases for details.

Frequently Asked Questions - FAQs

Find below frequently asked questions and how to tackle them.

"No Card Found" message is displayed by the network driver.

A.	The Configuration/Power Management Utility delivered with your computer may allow you to disable the PCMCIA Controller and/or power to the sockets. Check that all power settings are on and see the documentation for your computer.

B.	Insert the Installation disk, start the INSTALL program, respond "No" to Express Installation and install the Card Enabler (it might not have been installed).

See Notebooks - Special Cases. If your computer is included in this list, change the settings as instructed.

C.	Run the Diagnostic Program.

D.	The wrong driver may be installed. Install the appropriate driver from the Driver diskette that came with your card.

The driver will not load when using your computer's Card and/or Socket Services.

A.	Install the Olicom Enabler using the Install Program on the Installation disk.

The network connection fails even though the Diagnostic Program has passed the card.

A.	Check that the cable is properly connected and that the card is fully inserted and correctly oriented in the PCMCIA slot.

B.	Verify that you are connected to the same network as the server. Ask your network administrator.

C.	Insert the Installation disk, start the INSTALL program and respond "No" to Express Installation.

See Notebooks - Special Cases. If your computer is included in this list, change the settings as instructed.

The Card stopped working.

A.	Run the Diagnostic Program.

B.	Re-install the card drivers that came with your card.

Everything has been tried! What now?

If you cannot resolve the problem, write down the encountered error message(s) and retrieve as much information as possible about your system configuration (drivers, PC brand and model, operating system, network operating system, etc.). Contact Olicom Support when you have collected this information.


Utility Installation

The Olicom Ethernet GoCard is shipped with a set of utilities for Power Management purposes. The Olicom Card Installation Program can install these utilities for you, in a directory of your choice.

It is also possible to install the Olicom Card Installation program on your hard disk, so that it is ready for use when you need it.

A third utility, SETSPEED, is not applicable for Ethernet PCMCIA cards. It is only used with Olicom Token-Ring cards.

Support for Novell SNMP is also available. See "Novell SNMP Installation" for details.

Further, the Olicom Adapter Information for Windows provides information about the state of the Olicom GoCard and drivers.


changes
Changes to System Configuration Files

The following changes to the system configuration files apply when installing the Novell NetWare Client.

CONFIG.SYS

LASTDRIVE is set to "LASTDRIVE=Z"

AUTOEXEC.BAT

Lines are added at the top of AUTOEXEC.BAT to change the destination directory for the NetWare Client files and to invoke the STARTNET.BAT command file. The NetWare Client software is subsequently loaded.

If requested during installation, additional lines are added that invoke the server login program.

SYSTEM.INI  (Windows)

The "network.drv" setting in the [boot] section is changed to "netware.drv".

.

The "network.drv" setting in the [boot.description] section is changed to "NetWare (v4.01)".

The "network" setting in the [386enh] section is changed to "*vnetbios,vipx.386,vnetware.386".

Also, the "TimerCriticalSection" setting is set to "10000".

WIN.INI  (Windows)

"nwpopup.exe nwuser.exe" in the [windows] section is added to the "load" setting (unless already present).