|
Additional Information: |
For instructions and limitations on creating the diskette, click  here.
Installation Guide
The following instructions assume some familiarity with the LAN software. The installation process installs the basic drivers for each operating system, then the additional NDIS2 or ODI driver as a part of the LAN software installation. For detailed installation instructions on the latter step, refer to the respective LAN software documentation.
[For OS/2 Warp 3.0, 4.0, Warp Connect and Warp Server]
IBM's IrDA for OS/2 provides an NDIS (Network Driver Interface Specification 2.01) programming interface, and supports the following software combinations:
OS/2 Warp 3.0 with TCP/IP 3.0 with LAN Requester
OS/2 Warp 4.0 with TCP/IP 4.0 with Peer networking and with LAN Requester
OS/2 Warp Connect
OS/2 Warp Server
Other applications which use NDIS (or TCP/IP on NDIS) may also be used.
The setup for all of these is similar:
1. Insert this disk in drive A: and install the base OS/2 Infrared drivers by running INSTALL2.EXE. At a command line, type:
A:\INSTALL2 /S:A:\ /T:x:<target directory> /B:y: where x is the target drive and y is the boot drive where CONFIG.SYS is. This will copy files to your hard disk, and edit CONFIG.SYS, removing previous IR device drivers and adding new ones.
2. Install the communications product you are using with Warp, as listed in the supported products above.
In each case select MPTS (Multi-Protocol Transport Services) as the transport method. Configure MPTS by clicking on its icon or by typing MPTS on an OS/2 command line.
Select "Configure" in the first panel. In the second panel, select LAN Adapter and Protocols, and click on "Configure".
If you are using a previous level of Infrared support (such as that shipped with OS/2 Warp 4.0) check in the Current Configuration for "IBM Infrared NDIS MAC driver". If it exists, select "Remove".
If you have the "IBM IrDA NDIS2 driver" previously installed, you will need to select "Remove", then "OK", close, and reboot, since there are locked files. Restart MPTS and continue below.
Under "Network Adapters", select "Other Adapters", then enter the path "A:\NDIS\OS2". Files will be copied onto the hard disk into the \IBMCOM and \IBMCOM\MACS directories. Once the copying completes, select "IBM IrDA NDIS2 driver" from the list, and click on "Add". Under "Protocols", select the higher-level client protocols which will be required. Specify "TCP/IP" for TCP products, or "NetBIOS" for LAN Requester/Server and Peer Networking Products.
3. Edit the individual protocol selections:
From "Current Configuration", select "IBM IrDA NDIS2 Driver" and select "Edit". To view the allowable values for any field, put the mouse cursor in the field, click and press F1.
Enter a unique Network Address of the form "Xhhhhhhhhhhhh" where "h" is a hex character, or the locally-administered LAN address if you are connecting through an IR LAN Access Point. This address must be different from your session partner in a point-to-point setup, and unique in a LAN setup.
If you are using a LAN Access Point, you must also configure the appropriate Type of LAN Emulation ("Ethernet" or "TokenRing").
Edit the client Protocol which you selected.
4. Click on "OK" to close and save your changes. After MPTS ends, you need to reboot your system.
[For Windows for Workgroups 3.11]
1. Insert the disk in drive A:.
2. Install the base DOS/Windows driver by running INSTALLD.EXE. At an MS-DOS command line, type:
A:\INSTALLD /S:A:\ /T:x:<target directory> where x: is the target drive.
3. Install Windows for Workgroups. Choose Custom Install. In the Network Setup panel, choose "Install Microsoft Windows Network". Select Advanced, Drivers and Add Adapter. Choose 'Unlisted or Updated Network Adapter' and OK. Specify A:\NDIS\DOS as the driver source path and select the IBM IrDA NDIS2 driver. Change the default Network Address for the driver by selecting Setup and Network Address.
Enter a unique Network Address of the form "Xhhhhhhhhhhhh" where "h" is a hex character, or the locally-administered LAN address if you are connecting through an IR LAN Access Point. This address must be different from your session partner in a point-to-point setup, and unique in a LAN setup.
If you are using a LAN Access Point, you must also configure the appropriate Type of LAN Emulation ("Ethernet" or "TokenRing").
[For PC-DOS 7.0 with Personal Netware]
1. Insert the disk in drive A:
2. Install the base DOS/Windows driver by running INSTALLD.EXE as described in the Windows for Workgroups 3.11 section above.
3. Install Personal Netware. When asked for 'Primary Network Interface Card', choose 'OEM supplied driver' and set A:\ODI as the Source path for driver files. Choose configure Primary Interface Card and specify your Network Address under 'Optional Node Address'. Every ThinkPad should have a unique address.
Note: The ODI driver only supports the Ethernet Access Point.
[For PC-DOS 7.0 with Novell Client v4.0]
1. Insert the disk in drive A:
2. Install the base DOS/Windows driver by running INSTALLD.EXE as described in the Windows for Workgroups 3.11 section above.
3. Install the client software for Novell Netware. In step 4 insert this disk and select A:\ODI as the driver location. Choose 'IBM IrDA ODI Driver' and set the optional Node Address to your Network Address. Each ThinkPad should have a unique Network Address.
Note: The ODI driver only supports the Ethernet Access Point.
[For Windows 3.10/3.11 with IBM Internet Connect for Windows Corporate Kit Version 5.0]
1. Insert the disk in drive A:.
2. Install the base DOS/Windows driver by running INSTALLD.EXE as described in the Windows for Workgroups 3.11 section above.
3. Install IBM Internet Connect for Windows Corporate Kit Version 5.0. Select 'Provide LAN access'.
4. When asked for your network card's device driver disk, insert the disk in drive A: and specify A: as the source. You can change the IR port's Network Address by editing PROTOCOL.INI.
If you are using a LAN Access Point, you must also change the appropriate Type of LAN Emulation ("Ethernet" or "TokenRing") by editing PROTOCOL.INI.
Note: If you have other LAN adapters that are automatically detected by the IBM Internet Connection for Windows installation program, the PROTOCOL.INI binding specification may not be set up correctly. Only the IBM IrDA NDIS2 Driver should be specified, or you can manually add the necessary stanza/binding by editing PROTOCOL.INI later.
National Language Support
Only some drivers will be available in other languages. If you do not see a listing like this for additional languages, then that driver is available in English only. The English driver will work in ALL countries.
This driver is available in the following language format. (NOTE: If the version numbers below do not match the version number given above, then the updated driver listed above is available in ENGLISH only!):
DK -Dansk - v1.02
FI - Finnish - v1.02
FR - French - v1.02
GR - German - v1.02
IT - Italian - v1.02
NE - Dutch - v1.02
NO - Norwegian - v1.02
SP - Spanish - v1.02
SV- Swedish - v1.02
|
