Digitizer Support for OS/2 (ArcaOS, eComStation)

Provides guidance and tools to ease the development and integration of digitizer and touch screen solutions into the system.

May be freely used and exchanged, as long as it is not modified. You may use this product solely at your own risk. I cannot be held responsible for any damages occurring due to your using this product. You may not lease, rent or sell this product to any other party. Have fun.

For COM input devices you may have to look into the ACPITREE output to see what interrupt number and port address are to be used. Knowing these you have to put either the DEVICE=?:\OS2\BOOT\COM.SYS or DEVICE=?:\OS2\BOOT\PSCOM.SYS device driver statement with the proper parameters into your config.sys file.

On the Lenovo ThinkPad X200T with Wacom Penabled the ACPITREE output contained:

+*DTR_ T:[Device] HID:[WACF004] STA:[0xd] SxD State:[0xff:ff:ff:ff]
  Current state:
  > IO:[1 0x200 - 0x200 Al:1 Len:8]
  >Trigger by Edge, Polarity High IRQ-4
  > ENDTAG

To define COM1 to access the Wacom Pen at port=200 and irq=4 and eComStation installed on boot drive O: the input device driver statement is:

DEVICE=O:\OS2\BOOT\PSCOM.SYS (1,200,4,I)

To define COM1 to access the Wacom Pen at port=200 and irq=4 and OS/2 Warp 4.0 installed on boot drive O: the input device driver statement is:

DEVICE=O:\OS2\BOOT\COM.SYS (1,200,4,I)

After reboot you may run the COMRAW.CMD script to get raw digitizer input data at 38400 baud from the Lenovo ThinkPad into the 38400.RAW file. Run the DECODE.CMD script to display digitizer input data from that 38400.RAW file. Use COMRAW 19200 to run at 19200 baud and DECODE 19200.RAW to display it.

The USB 2.0 Extended Control Driver for OS/2 (ArcaOS, eComStation) is required. Obtain this product here free of charge.

For USB input devices you may have to look into the USBDock output to see what idVendor, idProduct and bcdDevice are to be used. Knowing these you have to put the DEVICE=?:\OS2\BOOT\USBECD.SYS device driver statement with the proper parameters into your config.sys file.

For my Wacom Bamboo CTH-460 tablet the USBDock extended report contained:

Vendor ID       :0x056A
Product ID      :0x00D1
Device Release# :0106

To define $BAMBOO$ to access the Wacom Bamboo CTH-460 tablet with idVendor=056A and idProduct=00D1 and bcdRelease=0106 and eComStation or OS/2 Warp 4.0 installed on drive O: the input device driver statement is:

DEVICE=O:\OS2\BOOT\USBECD.SYS /D:056A:00D1:0106 /N:$BAMBOO$

To define $E2500U$ to access the ELO Model 2500U device with idVendor=04E7 and idProduct=0105 and bcdRelease=0100 and eComStation or OS/2 Warp 4.0 installed on drive O: the input device driver statement is:

DEVICE=O:\OS2\BOOT\USBECD.SYS /D:04E7:0007:0105 /N:$E2500U$

After reboot you may run the USBWRITE.CMD script to obtain and display the device descriptor, configuration descriptors and associated interface and endpoint descriptors. Use USBWRITE $BAMBOO$ for the Wacom Bamboo CTT-460 tablet or USBWRITE $E2500U$ for the ELO Model 2500U device.

The Emulate Mouse Driver for OS/2 (ArcaOS, eComStation) is required. Obtain this product here free of charge.

You have to look into your config.sys file to find which mouse device driver has been installed on your system. You may find AMOUSE.SYS or MOUSE.SYS and you need to add the STYPE=XSMOUSE$ parameter to that device driver statement and insert the ?:\OS2\BOOT\XSMOUSE.SYS device driver statement just above it.

To define XSMOUSE$ to connect XSMOUSE.SYS to AMOUSE.SYS with ArcaOS installed on drive O: the output device driver statements are:

DEVICE=O:\OS2\BOOT\XSMOUSE.SYS
DEVICE=O:\OS2\BOOT\AMOUSE.SYS STYPE=XSMOUSE$

To define XSMOUSE$ to connect XSMOUSE.SYS to AMOUSE.SYS with eComStation installed on drive O: the output device driver statements are:

DEVICE=O:\OS2\BOOT\XSMOUSE.SYS
DEVICE=O:\OS2\BOOT\AMOUSE.SYS SMP STYPE=XSMOUSE$

To define XSMOUSE$ to connect XSMOUSE.SYS to MOUSE.SYS with OS/2 Warp 4.0 installed on drive O: the output device driver statements are:

DEVICE=O:\OS2\BOOT\XSMOUSE.SYS
DEVICE=O:\OS2\BOOT\MOUSE.SYS STYPE=XSMOUSE$

After reboot you may run the PUTEVENT.CMD script to see if the mouse pointer moves to the center of the screen.

Display from DECODE.CMD using the correct baudrate looks like:

sBtn=00,xPos=03799,yPos=02328,zPos=00026,Stylus:MoveOnly
sBtn=01,xPos=00953,yPos=00810,Finger:But1Down
sBtn=01,xPos=01789,yPos=03436,zPos=01418,Stylus:But1Down
sBtn=00,xPos=00953,yPos=00810,Finger:NoButMov
sBtn=00,xPos=01794,yPos=03433,zPos=00016,Stylus:MoveOnly
sBtn=00,xPos=00010,yPos=00027,zPos=00024,Stylus:NoButMov

The following COM input devices have been tested successfully:

Working with these scripts requires calibration:

To calibrate the digitizer using your stylus, put the tip of your stylus for 1 second to the top left and bottom right corners of the screen.

Use tc4200rs.cmd with rotated tablet (snap flipped screen).

Working with these scripts requires calibration:

To calibrate the digitizer using your finger, put the tip of your finger for 1 second to the top left and bottom right corners of the screen.

To calibrate the digitizer using your stylus, put the tip of your stylus for 1 second to the top left and bottom right corners of the screen.

The following USB input devices have been tested successfully:

Working with this script requires calibration:

To calibrate the digitizer using your finger, put the tip of your finger for 1 second to the top left and bottom right corners of the screen.

Working with these scripts requires calibration:

To calibrate the digitizer using your finger, put the tip of your finger for 1 second to the top left and bottom right corners of the screen.

To calibrate the digitizer using your stylus, put the tip of your stylus for 1 second to the top left and bottom right corners of the screen.