Section Three
4When prompted for ‘Packet driver or NDIS driver’ select ‘NDIS driver’.
5.When asked do you have a PROTOCOL.INI file answer:
YES
6.When prompted for path to PROTOCOL.INI file type:
C:\NDIS
7.When asked which driver does LanWatch bind to type:
OSITECH_NIF
8.When prompted for full path and filename of NDIS driver type:
C:\NDIS\OTCETH.DOS
Continue with installation.
The following are examples of the CONFIG.SYS, AUTOEXEC.BAT and PROTOCOL.INI file modifications after installing LanWatch.
CONFIG.SYS
DEVICE=C:\LW\PROTMAN.DOS /I:C:\NDIS
DEVICE=C:\LW\FTPSOFT.DOS
DEVICE=C:\NDIS\OTCETH.DOS
AUTOEXEC.BAT
C:\LW\NETBIND.COM
PROTOCOL.INI
[OSITECH_NIF]
DRIVERNAME=OTCETH$
| [LANWATCH] |
|
| DRIVERNAME | = FTPSOFT$ |
| BINDINGS = | OSITECH_NIF |
Note: | Keyword specifications associated with the NDIS driver are explained | |
| in Appendix B, Error Messages in Appendix C. | |
IBM LAN Server
When installing IBM LAN Server 3.0 or 4.0 you may use the OEM Network adapter driver import capability for the Ositech Trumpcard NDIS device driver. For a DOS workstation, follow the instructions for installing the IBM LAN Support Program.
3 - 6 | Trumpcard Ethernet LAN |