home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 20 NDrivers
/
20-NDrivers.zip
/
NPAFDDIO.ZIP
/
README.TXT
< prev
Wrap
Text File
|
1991-03-21
|
3KB
|
78 lines
Release: NDIS drivers for NP-AT and NP-EISA adapters in a OS/2 machine
Version: 1.4 D
Date: 03/21/91
------------------------------------------------------------------------
DIRECTORY ORGANIZATION:
\mslanman.os2 : "LANMAN" (OS/2)
\drivers : standard LanMan directory
\nif : standard LanMan directory
npat_os2.nif : for "at_lm.os2"
npea_os2.nif : for "eisa_lm.os2"
\fddi : standard LanMan directory
\npi : Network Peripherals subdirectory
\at : NP-AT adapter NDIS drivers for OS/2
at_lm.os2
procotol.ini
\eisa : NP-EISA adapter NDIS drivers for OS/2
eisa_lm.os2
procotol.ini
INSTALLATION NOTES:
1) To install all drivers into a Lan Manager Client,
choose one of the following methods:
a) use the SETUP program's "Import OEM Drivers" function to
install the software into the "lanman" directory tree;
b) transfer the files without using SETUP:
- xcopy a:\mslanman.os2\*.* c:\lanman\ /s
- Run the SETUP program after copying the files to select a
driver and update the CONFIG.SYS and PROTOCOL.INI files.
COMMON PROBLEMS AND LIMITATIONS:
Please call us if you find a problem or limitation.
1) "Bind failure due to a hardware configuration error". There are
jumpers on the board which select which type of FDDI connection
the board is to function as (A, B, S, M). It is also possible
to "override" the jumper setting through the PROTOCOL.INI file.
Refer to the user's manual for information about the jumpers.
In either case, a mismatch or error is not detectable until the
protocol stacks and the driver are "BOUND" and the network is
started. The NDIS driver will return a configuration error to
the protocol stack, the protocol stack MAY report that it cannot
run, and the operating system may report a failure as well.
If this situation occurs, make sure that the jumpers are correct,
and that the PROTOCOL.INI values are correct, and that the FDDI
station connected to the failing one supports the type that is
being selected (some may reject M connections, for example).
2) If you select an interrupt which another device is using,
an error is indicated when the driver(s) are started and they
find that the interrupt is already enabled. This only occurs if
the driver using the interrupt is loaded before the NDIS driver.
If you experience problems communicating with a server and all
other functions appear to work, you may have loaded a driver
after the NDIS driver which took the interrupt away from NDIS.
NEW OR UPDATED INFORMATION:
Please call us if you think something is missing.