User guide

Chapter 2 - Installation

NetWare Driver Installation

Multi-Tech Systems provides AIO drivers for the ISI3334 cards, so they can function with Novell compatible

asynchronous applications (e.g., NetWare Connect). The AIO driver is simply an NLM (NetWare Loadable Module)

that runs on the file server. Drivers must be loaded on the file server where the board is installed. Drivers can be

loaded from the file servers console prompt or incorporated for autoloading in the AUTOEXEC.NCF file.

To install the Multi-Tech AIO driver, copy the file AIOISIX.NLM to the system directory of the file server from a

workstation on the network. To copy, you can use the following command:

COPY E:\SERVCARD\DRIVERS\NOVELL\AIOSIX.NLM F:\SYSTEM

If you have downloaded the ISI driver from the MultiTech web site onto a diskette, use this command:

COPY A:\NOVELL\AIOISIX.NLM F:\SYSTEM

To load the driver, go to the system or PC console (where the ISI card is installed) and enter the following at the

prompt:

LOAD AIOISIX [port=W] [interrupt=X] [name=Y] [note=Z]

To install the ISI card scripts, copy aiomdms.mdc to f:\system\aio\directory. Click Yes to overwrite the existing

aiomdms.mdc file.

Configuring Ports for NetWare Connect

When the driver is installed, it will allocate consecutive ports for the ISI card as follows:

 4 consecutive ports for the ISI3334-4.

 8 consecutive ports for the ISI3334-8

To set up NetWare Connect ports, enter LOAD NWCCON at the NetWare console prompt. LOAD NWCCON opens

the NetWare Connect Configuration Utility. Select the appropriate menu options (modem type, speed, flow control,

etc.).

Removing the Driver (Novell)

In Novell, remove file AIOISIX.NLM from the system directory and make the appropriate changes to the

Autoexec.ncf file.

Troubleshooting

Problem: I loaded the driver at the file server console, then I started NetWare Connect and connected a modem to

a port on an ISI3334. When I try to communicate with the modem, I see the DTR of the modem being raised, but

the modem does not respond to my AT commands.

Solution: There might be an IRQ conflict between an ISI3334 and some other hardware in your system. Even

though that particular device (for example, a mouse) is not activated under NetWare, that device will still control the

IRQ. See your system's documentation to find out how to disable that device.