home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 33 VDrivers
/
33-VDrivers.zip
/
os2_30.exe
/
READ.ME
< prev
next >
Wrap
Text File
|
1995-07-12
|
10KB
|
283 lines
MicroTouch Systems, Inc.
OS/2 Touch Screen driver, Version 3.0A
Procedure to Install and Operate the MicroTouch OS/2 Touch Screen Driver
------------------------------------------------------------------------
Hardware and Cabling:
---------------------
Connect the touch screen controller to your PC's COM1 or COM2 port and
be sure the power is on.
Software:
---------
1. Insert the floppy disk containing the touch screen software in your
A: (or B:) drive.
2. Run SETUP.EXE from the A: (or B:) drive and follow the instructions
on the screen.
3. Reboot the system.
The setup program will make the following changes to your system:
1. The installation defaults to \MTSOS2 as the directory for all touch
screen files. If the directory does not exist, it is created.
2. Your CONFIG.SYS file is modified as follows:
a. The following line is added before the MOUSE device driver line
DEVICE=C:\MTSOS2\MTOUCH.SYS
or
DEVICE=C:\MTSOS2\MTOUCHP.SYS
b. The MOUSE device driver line is modified to read:
DEVICE=C:\MTSOS2\MOUSE.SYS TYPE=MTOUCH$
Notes: The touch screen drivers must be loaded BEFORE any other
communications drivers such as COM.SYS and VCOM.SYS.
See the section called "COM.SYS Error Messages" if needed.
If using a mouse AND a touch screen, see the section called
"Installing the Touch Screen and a Mouse on the Same System".
If using IBM's AVC software, see the section called "Audio
Visual Connection (AVC) Users" at the end of this file.
3. The control panel, MTCHCTRL.EXE (or PENPANEL.EXE), and the pen/finger
switching utility, OS2PEN.EXE, are added to a new Program Group called
MicroTouch Touch Screen.
Additional Information:
-----------------------
The MTOUCH.SYS and MTOUCHP.SYS device drivers can take the following
parameters:
DEVICE=C:\MTSOS2\MTOUCH.SYS
SERIAL=[COM1|COM2|COM3|COM4|COM5|COM6|COM7] default = COM1
IRQ=[2|3|4|5|6|7] default = 4
BAUD=[1200|2400|4800|9600|19200] default = 9600
ALTTYPE=[e.g. MSBUS$|MSINP$|MSSER$] default = NONE
BEEP=[UP|DOWN|NONE] default = NONE
BUTTONEMUL=[LEFT|RIGHT] default = LEFT
BUTTONMODE=[TAP|DRAG|LIFTOFF] default = LIFTOFF
OFFSET=touchpoints (0 to 1023) default = 0
TAPDISTANCE=pixels (0 to 1023) default = 24
TAPTIME=milliseconds default = 750
Note: all the parameters should be on a single line separated by a space.
COM1 always uses IRQ4 regardless of the IRQ setting.
COM2 always uses IRQ3 regardless of the IRQ setting.
ALTTYPE
The type of mouse being used, if one exists.
Refer to your mouse documentation for the "type" parameter.
BAUD
The data rate used by the controller.
BEEP
Determines whether a beep is issued on touchdown, liftoff or not at all.
BUTTONEMUL
The mouse button emulated by a touch.
BUTTONMODE
The button events are handled differently depending on the BUTTONMODE
that is in effect.
For the BUTTON mode (called "tap" mode in config.sys), the first
touchdown will generate mouse movement and immediate left button down
and left button up events.
For the DESKTOP mode (called "liftoff" mode in config.sys), the first
touchdown will generate mouse movement events. The first liftoff will
generate a button down event followed by a button up event. Subsequent
touchdowns (taps) on the same location will generate button down events.
For the DRAWING mode (called "drag" mode in config.sys), all touchdowns
will generate button down events and all liftoffs will generate button
up events.
The following table summarizes the mouse events generated under
various conditions:
Button Mode Drawing Mode Desktop Mode
(Tap) (Drag) (Liftoff)
----------- ------------ ------------
1st touchdown button down/up button down movement
continuing touch movement drag movement
1st liftoff movement button up button down/up
tap button down/up button down/up button down/up
2nd continuing touch movement button down movement
2nd liftoff movement button up button down/up
IRQ
The hardware interrupt number used by the communications port.
OFFSET
The distance that the display cursor is shifted above your finger in order
to make it visible.
SERIAL
The communications port to which the touch screen has been connected.
TAPDISTANCE
The maximum "distance" between taps for a double tap (or double mouse
button click) to be recognized.
TAPTIME
The maximum "time" between taps for a double tap (or double mouse
button click) to be recognized.
Driver Load Messages:
---------------------
If the driver loads successfully, the system will display a message
similar to the following:
Touch Screen Device Driver (Version 2.x)
Copyright (C) 1991-1995 MicroTouch Systems, Inc.
Methuen, MA, All Rights Reserved
Installed....
Driver Error Messages:
----------------------
If the driver does not load successfully, the system will display a
message similar to the following:
Touch Screen Device Driver (Version 2.x)
Copyright (C) 1991-1995 MicroTouch Systems, Inc.
Methuen, MA, All Rights Reserved
--> Touch screen controller not responding.
--> Use alternate mouse device.
Other error messages are shown below:
--> Invalid Parameter
Meaning: The system is trying to parse the device line parameters
of the driver, but could not find a parameter that matched.
Action: Check the device line parameters on the device driver.
Make sure the parameter names and formats are correct.
** Error: Unable to get DosGetInfoSeg
Meaning: The system is trying to get the global and local Info
segments, but fails. This is an OS/2 kernel problem.
Action: Check the CONFIG.SYS file to make sure the OS/2 kernel
is properly installed.
** Error: Serial Port not available
Meaning: There is no serial port available.
Action: Make sure the serial port specified in the CONFIG.SYS
is present and free.
** Error: Unable to Initialize Comm Port
Meaning: The system is unable to initialize the Comm Port.
This is usually caused by a hardware problem.
Action: Make sure the Comm Port is working.
** Error: Unable to set IRQ
Meaning: The IRQ specified in the device line parameter is used by
another process.
Action: Make sure the Irq parameter in CONFIG.SYS file is valid.
COM.SYS Error Messages:
-----------------------
If COM.SYS or VCOM.SYS do not load, the system will display one
or more error messages. The meanings of these error messages are:
** Error: COMx did not install. The interrupt level is not available.
Meaning: If 2 or more async cards use the same interrupt and the touch
screen is connected to one of them, this message will appear
when COM.SYS is loaded.
Action: Change the interrupt level on the second card.
** Errors: SYS1201: Device driver "C:\OS2\BOOT\COM.SYS" specified in the
DEVICE statement on line xx of the CONFIG.SYS file was not
installed. Line xx is ignored.
Press Enter to continue.
SYS1201: Device driver "C:\OS2\MDOS\VCOM.SYS" specified in the
DEVICE statement on line xx of the CONFIG.SYS file was not
installed. Line xx is ignored.
Press Enter to continue.
Meaning: All the async ports are used, for example, a serial mouse and
touch screen are connected to the 2 available ports.
Action: Remove COM.SYS and VCOM.SYS from your CONFIG.SYS file.
Installing the Touch Screen and a Mouse on the Same System:
----------------------------------------------------------
If using Pen OS/2, change MTOUCH.SYS to MTOUCHP.SYS in what follows.
Under OS/2 Version 2.x:
For a standard PS/2 mouse, edit the CONFIG.SYS file and add/modify
the following device statements:
DEVICE=C:\MTSOS2\MTOUCH.SYS
DEVICE=C:\MTSOS2\MOUSE.SYS STYPE=MTOUCH$
For a non-standard mouse, edit the CONFIG.SYS file and add/modify
the following device statements:
DEVICE=C:\OS2\ddddd.SYS
DEVICE=C:\MTSOS2\MTOUCH.SYS ALTTYPE=ddddd
DEVICE=C:\MTSOS2\MOUSE.SYS TYPE=MTOUCH$
where ddddd = the device dependent driver name
Under OS/2 Version 1.x:
Edit the CONFIG.SYS file and add/modify the following three device
statements:
DEVICE=C:\OS2\MSxxx01.SYS
DEVICE=C:\MTSOS2\MTOUCH.SYS ALTTYPE=MSxxx$
DEVICE=C:\MTSOS2\MOUSE.SYS TYPE=MTOUCH$
where xxx = INP for an in-port mouse,
SER for a serial mouse or
BUS for a bus mouse
The order of the above device statements is important, and cannot be
changed. We recommend you test the mouse and touch screen devices
separately first before combining them on the same system.
Audio Visual Connection (AVC) Users:
------------------------------------
To use the touch screen with AVC, you MUST run the program MTS_AVC.EXE
to enable AVC mode BEFORE running AVC as follows:
MTS_AVC
AVC
If you don't run MTS_AVC, the touch screen will appear to be inaccurate.
Upon exiting AVC, turn off the AVC mode as follows:
MTS_AVC off
A sample command file, TOUCHAVC.CMD, is included with this software. It
contains the above commands to automatically enable and disable AVC mode.
Please also note that the touch screen should be in "DRAG" mode (see the
"Control Panel" section above) for best results with AVC.