Infrared drivers (v2.0) for OS/2	README.TXT 05/04/01
--------------------------------
 
These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21.They do NOT work on the 560.

What's new:
----------

This release fixes some problems with Nokia phones and PPP connections (e.g. with InJoy).
After a while, the connection would freeze because of a limitation in packet size that Nokia phones
seem to have and that we did not notice with other phones (Ericsson).


To install:

- Unpack the IRDDx.ZIP file (will create an \irdd directory and unzip a bunch of files into it

-  For now, you'll have to manually add the following lines to the end of your
   CONFIG.SYS file:

   REM  Begin IBM OS/2 IrDA Driver Section
   DEVICE=x:\IRDD\IRDA_PHY.OS2
   DEVICE=x:\IRDD\IRDA_DD.OS2
   DEVICE=x:\IRDD\IAS_DD.OS2
   DEVICE=x:\IRDD\IRCOMM.SYS /V 
   REM DEVICE=x:\IBMCOM\MACS\IRDANDIS.OS2
   REM  End IBM OS/2 IrDA Driver Section

-  Create a WPS icon for the PMIRDA.EXE program and place it in your Startup Folder.

-  make sure you delete the old IR driver (IRDD.SYS) from your CONFIG.SYS file


1) IrCOMM support
-----------------

The IRCOMM.SYS  driver make it possible to assign a virtual COM port to your Infrared attached IrCOMM
device (Cellular phone, etc.). You can then use any COM port aware application package to access the
device like through a normal COM port, i.e. issue AT commands to a modem, etc.

Communication Applications tested with this release are:

- InJoy IP Dialer V2.3
- Opalis BTX decoder (German online service)
- ...

NOTE: THe AT&T Global Network Dialer does NOT work with IRCOMM for now...

IrCOMM also supports printing via the infrared port. Just install the right printer driver, then point
it to the COM port IrCOMM is using.
For Win-OS/2 printing, you can select the same COM port as you Win-OS/2 printer port.

Printers tested so far:

- HP LaserJet 6MP
- HP DeskJet 340

Whenever the IRCOMM driver detects a device, you will see the red indicator come on and tell you
there's an active connection.

The IRCOMM.SYS driver supports the following parameters (case sensitive!):

/V			tells you which COM port the driver has assigned to itsself
/COMPORT:COMx	sets the COM port that IrCOMM will use


2) NDIS support
---------------

IBM's IrDA for OS/2 also provides an NDIS (Network Driver Interface Specification 2.01) programming
interface, This code replaces the IR drivers that are shipped with Warp 4 / Warp Server for e-business,
which works on the 760 series Thinkpads, but not on the newer ones.

The drivers support the following software combinations: 

OS/2 Warp 4.0 (TCP/IP 4.x, Peer networking, LAN Requester) 
OS/2 Warp Server for e-business

                 
All protocols which use NDIS (i.e. NetBIOS, TCP/IP, 802.2) may be used. 

The setup for all of these is similar: 

1. Install the base OS/2 Infrared drivers (see above).

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 "x:\IRDD". 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. 


*** END of README.TXT ***

