MicroTouch TouchWare for Windows 95, Windows 3.1x, and MS-DOS Version 3.4, April 1997 Copyright 1991-1997 MicroTouch Systems, Inc. All rights reserved. __________________________________________________________________ CONTENTS 1.0 Installing TouchWare 1.1 Installing for Windows and MS-DOS (Disk 1 & 2) 1.2 Installing for MS-DOS Only (Requires Disk 2) 1.3 Upgrading from a MS-DOS Only Setup 1.4 Installing on Dual-Boot Systems 1.5 Installing to a Network Drive 1.6 Conflicts with Interrupts (IRQs) 1.7 Conflicts with Long Path Statements in AUTOEXEC.BAT 2.0 New Features in TouchWare 3.4 3.0 TouchWare Files 3.1 TouchWare Programs and Version Numbers 3.2 TouchWare Files for Windows and MS-DOS 3.3 TouchWare Files for MS-DOS Only 4.0 Using a TouchPen with the Touchscreen 4.1 Making Pen Touch Work Like Finger Touch 4.2 Adjusting Baud Rate to Improve TouchPen Tracking 5.0 ThruGlass Touchscreens and Controllers 5.1 Old ThruGlass Controllers Not Supported 5.2 Changes in Touch Terminal Not Updated in Control Panel 5.3 Interference from Security Tag Readers 6.0 Super VGA Support for DOS Touchscreen Driver 6.1 DefaultVirtualSize Parameter 6.2 CalibrateVideoMode Parameter 7.0 User Documentation 8.0 Known Limitations and Restrictions 8.1 Mouse Driver and Touchscreen Conflicts 8.2 Uninstall Not Accessible From Add/Remove Programs 8.3 Cannot Uninstall More Than One Instance 8.4 Uninstalling on a mouseless system. 8.5 DOSTOUCH with Windows 95 Limitation 8.6 Controller Frequency Limitations 8.7 Microcal Limitation 8.8 System May Hang on Restart After Install 8.9 Delay in Opening Windows Touchscreen Control Panel __________________________________________________________________ 1.0 INSTALLING TOUCHWARE 1.1 Installing for Windows and MS-DOS (Disk 1 & 2) o Windows95 - Use the Control Panel applet ADD\Remove files to install program. o Windows 3.1x - Install diskette 1 in disk drive and run Setup from File Manager. o MS DOS - Install diskette 2 in disk drive and run Install.bat from the diskette. 1.2 Installing for MS-DOS Only (Disk 2 only) To install TouchWare for MS-DOS only, insert Disk 2 into a diskette drive and run the INSTALL program. The Install program only uses Disk 2 and loads only the touchscreen files for MS-DOS. 1.3 Upgrading from a MS-DOS Only Setup If you are installing over a previous "MS-DOS only" install of TouchWare and you are now installing into Windows for the first time, the Setup program creates a new DOSTOUCH.INI file. Any custom settings you made to the DOSTOUCH.INI file are not saved. Therefore, you may want to make a backup of the DOSTOUCH.INI file before installing TouchWare. Note that overwriting the DOSTOUCH.INI file only occurs in this one case. In all other cases, the Setup program does not overwrite an existing DOSTOUCH.INI file. Note: The default directory for TouchWare is C:\MTS\TOUCH. 1.4 Installing on Dual-Boot Systems When you install to a dual-boot system (that is, Windows 95 and Windows 3.1), you must install TouchWare to two different directories if you want to be able to uninstall each version. Be sure to select Custom Install when you run the Setup program so you can specify the destination directory. 1.5 Installing to a Network Drive Although not recommended, you can install TouchWare to a network drive. However, your network must be configured such that you can log in and have access to the network before attempting to load the touchscreen driver. If Windows starts up before you log in to the network, the touchscreen will not work because Windows cannot load the necessary touchscreen files from the network. 1.6 Conflicts with Interrupts (IRQs) Your PC configuration must have a unique communication (COM) port and interrupt request (IRQ) available to assign to the touchscreen. The touchscreen cannot share an IRQ with another device in your system configuration, even though the other device may support IRQ sharing. 1.7 Conflicts with Long Path Statements in AUTOEXEC.BAT As defined by MS-DOS, the PATH statement in your AUTOEXEC.BAT file cannot have more than 127 characters. When you install TouchWare, the Setup program adds the TouchWare destination directory to the beginning of the PATH statement. The Setup program will display an error message if adding the directory will exceed the limits of the PATH statement. If you continue with the TouchWare installation, Setup will truncate some of the information at the end of the PATH statement. To see what information was deleted, you can always look at the previous version of your AUTOEXEC.BAT file (for example, AUTOEXEC.BAK or AUTOEXEC.00x). __________________________________________________________________ 2.0 NEW FEATURES IN TOUCHWARE 3.4 o Enhanced Setup program for installing the software -- Allows for Express or Custom install -- Installs for Windows 95, Windows 3.1x, and MS-DOS -- Includes updated search routine for finding touchscreen o Includes TouchWare Uninstall utility o Updated Windows Touchscreen control panel -- Includes option for adjusting controller frequency -- Includes status information about the touchscreen controller and firmware o Updated Microcal Diagnostic utility -- Provides option to automatically test and adjust the frequency of SMT3 and TouchPen touchscreen controllers -- Supports additional touchscreen controllers, including SMT3, TouchPen, and ThruGlass -- Runs terminal emulation mode at full screen -- Supports non-standard COM ports o Added support for ThruGlass touchscreen and controller -- Includes ThruGlass control panel for Windows -- Includes ThruGlass control panel for MS-DOS __________________________________________________________________ 3.0 TOUCHWARE FILES 3.1 TouchWare Programs and Version Numbers The TouchWare 3.4 release consists of the following Windows and MS-DOS programs: Program Version Number ------- -------------- TouchWare for Windows 3.4 TouchWare for MS-DOS 3.5 Microcal Diagnostic Utility 6.1 3.2 TouchWare Files for Windows and MS-DOS The following table lists all the TouchWare files and provides a brief description of each file. The Setup program installs the TouchWare files for both Windows and MS-DOS. Installation of TouchWare requires approximately 2.5MB. File Name Description --------- ----------- CTL3D.DLL System file required to uninstall TouchWare DEISL1.ISU Uninstall instructions; file must exist to uninstall TouchWare DOSPANEL.EXE Touchscreen control panel for DOS DOSPANEL.HLP Help file for the DOS Touchscreen control panel DOSPEN.EXE Pen Configuration utility for DOS DOSTOUCH.EXE Touchscreen driver for DOS DOSTOUCH.INI Initialization file for the DOS touchscreen driver DOSTOUCH.OVL DOS touchscreen driver overlay MCAL.OVL Microcal Diagnostic utility overlay MICROCAL.EXE Microcal Diagnostic utility MICROCAL.HLP Help file for the Microcal Diagnostic utility MTCONFIG.EXE DOS Touchscreen Configuration utility MTSMOUSE.DRV Cursor display driver for Windows; required only if you are not using a mouse with the touchscreen MTTOUCH.HLP TouchWare help file QCAL.OVL Microcal Diagnostic utility overlay QUICKCAL.HLP Help file for the Microcal Diagnostic utility README.TXT Product information, release notes REG32.EXE Program for updating the Windows 95 registry TGCAL.EXE ThruGlass control panel for DOS TOUCH.386 Touchscreen driver for Windows enhanced mode TOUCH.DRV Touchscreen driver for Windows TOUCHDLL.DLL A library of functions used by the Windows Touchscreen control panel TOUCHMTS.DLL Library of function calls TOUCHTRM.EXE ThruGlass terminal emulation program TWUNINST.EXE TouchWare uninstall utility UNINST16.EXE Uninstall utility WINPANEL.EXE Touchscreen control panel for Windows WINPEN.EXE Pen Configuration utility for Windows WINTGCAL.EXE ThruGlass control panel for Windows WINTGCAL.HLP Help file for the Windows ThruGlass control panel WINTGCAL.INF ThruGlass configuration file 3.3 TouchWare Files for MS-DOS Only File Name Description --------- ----------- DOSPANEL.EXE Touchscreen control panel for DOS DOSPANEL.HLP Help file for the DOS Touchscreen control panel DOSPEN.EXE Pen Configuration utility for DOS DOSTOUCH.EXE Touchscreen driver for DOS DOSTOUCH.INI Initialization file for DOS touchscreen driver DOSTOUCH.OVL DOS touchscreen driver overlay MCAL.OVL Microcal Diagnostic utility overlay MICROCAL.EXE Microcal Diagnostic utility MICROCAL.HLP Help file for the Microcal Diagnostic utility MTCONFIG.EXE DOS Touchscreen Configuration utility QCAL.OVL Microcal Diagnostic utility overlay QUICKCAL.HLP Help file for the Microcal Diagnostic utility README.TXT Product information, release notes TGCAL.EXE ThruGlass control panel for DOS _________________________________________________________________ 4.0 USING A TOUCHPEN WITH THE TOUCHSCREEN 4.1 Making Pen Touch Work Like Finger Touch If you are using a TouchPen controller, you can use your finger or a touch pen as a touch-input device. By default, the touch pen ignores the Touch Mode setting and the Audible Feedback setting specified in the Touchscreen control panel. If you want the touch pen to function exactly like your finger touch, add the following line to the [Windows Touch Screen] section of the SYSTEM.INI file: Note: The system.ini is in the Windows directory. PacketModifier=35 When you restart your system, the touch pen will function exactly like your finger. The touch pen will use the Touch Mode setting and the Audible Feedback setting specified in the Touchscreen control panel. 4.2 Adjusting Baud Rate to Improve TouchPen Tracking If you experience tracking problems while using the touchpen, the baud rate is probably set too low. The standard baud rate for MicroTouch controllers is 9600. This rate is generally acceptable for most applications. If you need to adjust the baud rate, be sure to change the baud rate of both the touchscreen driver and the touchscreen controller. __________________________________________________________________ 5.0 THRUGLASS TOUCHSCREENS AND CONTROLLERS TouchWare 3.4 includes a new Windows ThruGlass control panel for setting up a ThruGlass touchscreen. You use the control panel to select your screen type, set the frequency and sensitivity of the controller, and calibrate the touchscreen. o You can use the Windows ThruGlass control panel to set up a 10.4-inch or a 17-inch touchscreen. o You can use the DOS ThruGlass control panel to set up a 17-inch touchscreen only. If you want to use a 10.4-inch touchscreen in MS-DOS, try setting up the screen in Windows and then using it in MS-DOS. If you still need help with the setup, call MicroTouch Technical Support. 5.1 Old ThruGlass Controllers Not Supported TouchWare 3.4 has new files for configuring the sensitivity of a ThruGlass touchscreen. Because these files are not backward compatible, TouchWare 3.4 does not support the following old ThruGlass controllers: o 34-100, 34-101 o 34-200, 34-201 If you are using an old ThruGlass controller and want to upgrade to TouchWare 3.4, contact MicroTouch Technical Support at (508)659-9200 for more information. 5.2 Changes in Touch Terminal Not Updated in Control Panel The ThruGlass control panel has options for changing the frequency and sensitivity of the controller. You can also change these values by using the Touch Terminal program. Although your changes are saved correctly, the ThruGlass control panel is not updated with the correct values. 5.3 Interference from Security Tag Readers Radio security tag readers may interfere with the ThruGlass touchscreen if you place them within six inches. To eliminate the interference, you can move the reader away or place a piece of grounded metal between the reader and the screen. __________________________________________________________________ 6.0 SUPER VGA SUPPORT FOR DOS TOUCHSCREEN DRIVER To improve the handling of non-standard video modes, you can manually add the following parameters to the C:\MTS\TOUCH\DOSTOUCH.INI file: o DefaultVirtualSize o CalibrateVideoMode You should use these parameters if the cursor (also called the mouse pointer) cannot reach all areas of the video display or if the cursor movement seems exaggerated and extends beyond the video image. However, before attempting to correct the problem by using these parameters, use the Microcal Diagnostic utility and make sure the touchscreen is calibrated properly. Use the Microcal Draw option to test the calibration. 6.1 DefaultVirtualSize Parameter The DefaultVirtualSize parameter tells the driver what display size to use if the video mode cannot be recognized. This usually occurs when using a pre-VESA Super VGA adapter card. The format of the parameter is two numbers separated by a space: DefaultVirtualSize=X Y X = The default video resolution of the virtual screen in the horizontal direction. Y = The default video resolution of the virtual screen in the vertical direction. Example: DefaultVirtualSize=1024 768 6.2 CalibrateVideoMode Parameter You should use the CalibrateVideoMode parameter when you know the video mode number(s) assigned by the video BIOS. You must specify the "CalibrateVideoMode" parameter if your application uses more than one non-standard video mode. You may repeat the CalibrateVideoMode parameter as many times as necessary to describe multiple video configurations. The CalibrateVideoMode parameter has 9 values. You must separate each value with a space. The format is as follows: CalibrateVideoMode = OEMmode VESAmode T X Y [Xoffset Xsize Yoffset Ysize] Examples: CalibrateVideoMode= 6 0 0 640 350 CalibrateVideoMode=3 0 1 80 25 0 1023 85 853 (with optional parameters) Use the first 5 values to handle the video mode properly. OEMmode = The video mode number reported to the video BIOS using function 0. This value is always required. If there is also a VESA mode (see below) with no corresponding OEM mode, enter a value between 0x80 and 0xff (128-255). VESAmode = The video mode number reported to the video BIOS using function 0x4f02 (usually greater than 0x100). If there is no VESA mode for the OEM mode specified above, enter 0. You can define up to 2 OEMmodes that are not also VESA modes. VESA modes greater than 0x11b are not defined and count as unknown OEM modes. T = 0 if graphics mode. 1 if color text mode. 2 if monochrome text mode. X = The horizontal virtual screen size in graphic modes (T=0). The units are pixels. In text modes (T=1), enter the screen dimension in characters (for example, 80). The driver computes the virtual screen size by using an 8x8 cell (for example, 80x25 -->640x200; 132x50 -->1056x400). Y = The vertical virtual screen size in graphic modes (T=0). The units are pixels. In text modes (T=1), enter the screen dimension in characters (for example, 25). The driver computes the virtual screen size by using an 8x8 cell (for example, 80x25 -->640x200; 132x50 -->1056x400). Use the next 4 values as a group to align the touchscreen with the video image in the event that the image is smaller than the calibrated touch area. This is a common problem when using LCD displays. These values are optional and may be omitted. All values are in touchscreen units (0 to 1023). Xoffset = The horizontal distance from the left edge of the touchscreen active area to the left edge of the display image. Xsize = The width of the display image (in touchscreen units). Yoffset = The vertical distance from the bottom edge of the touchscreen active area to the bottom edge of the display image. Ysize = The height of the display image (in touchscreen units). As for any parameter in the DOSTOUCH.INI file, the touchscreen driver ignores any invalid entries although unusual behavior may result. You may need to contact the vendor of your video adapter and/or the vendor of your software package in order to determine the proper values. Feel free to experiment if you are unsure of video mode numbers and/or resolutions. Incorrect entries will NOT harm the touchscreen or your system. __________________________________________________________________ 7.0 USER DOCUMENTATION The following documentation is new or updated for TouchWare 3.4: o TruePoint Touch Monitor with a Serial/SMT or a TouchPen Controller Getting Started, Version 2.1 o TruePoint Touch Monitor with a PC Bus Touchscreen Controller Getting Started, Version 2.2 o TouchWare User's Guide, Version 3.4 o Touch Controllers Reference Guide, Version 2.1 o ThruGlass Touchscreen Hardware Installation Guide, Version 2.0 __________________________________________________________________ 8.0 KNOWN LIMITATIONS AND RESTRICTIONS 8.1 Mouse Driver and Touchscreen Conflicts The MicroTouch touchscreen may not work if your mouse uses one of the following drivers: o LogiTech mouse drivers (LMOUSE), some versions o Compaq mouse drivers (QMOUSE), some versions o IntelliPoint for Windows 95 If you are using the LogiTech or Compaq mouse driver, replace the driver with a standard Microsoft mouse driver before you install TouchWare. If you are using Windows 95 IntelliPoint, use the Add/Remove Programs control panel to remove it before you install TouchWare. 8.2 Uninstall Not Accessible From Add/Remove Programs in Windows 95. _ Windows95 - Run Uninstall which is located in the MicroTouch TouchWare folder. 8.3 Cannot Uninstall More Than One Instance You cannot uninstall more than one instance of a TouchWare installation. For example, suppose you 1. Install TouchWare to the \MTS\TEST1 directory. 2. Install TouchWare again and place the files in a different directory, for example, \MTS\TEST2. 3. Run the TouchWare Uninstall utility. The Uninstall utility will only remove the touchscreen files and folders for one installation. There is one exception. If you are using a dual-boot system (that is, Windows 95 and Windows 3.1), you can uninstall one TouchWare installation per operating system. However, you must have installed TouchWare to two different directories. 8.4 Uninstalling on a mouseless system If you have a mouseless system running TouchWare version 3.2 and you upgrade to TouchWare version 3.4, attempting to run the Uninstall utility will NOT restore your 3.2 system. You MUST reinstall TouchWare 3.2 immediately after completion of the Uninstall of TouchWare 3.4and before rebooting your system. Otherwise, your system will not boot properly. 8.5 DOSTOUCH with Windows 95 Limitation The latest version of the DOS Touchscreen Driver (DOSTOUCH) gives limited support for full-screen MS-DOS applications running under Windows 95. You can run full-screen MS-DOS applications under Windows 95, however, you cannot run Windows 95 touch applications during the same session. The Windows touchscreen driver and the DOS touchscreen driver cannot be loaded at the same time. 8.6 Controller Frequency Limitations o You cannot use the Controller Frequency option on the Windows Touchscreen control panel to adjust the frequency of a TouchPen controller. You must use Microcal. o You cannot use the Controller Frequency option on the Windows Touchscreen control panel to adjust the frequency of a ThruGlass controller. You must use the ThruGlass control panel. o If you are using a resistive touchscreen controller (for example, SMT3R or SMT3RV), you do not need to adjust the frequency. 8.7 Microcal Limitation In the event Microcal encounters a conflict with a device other than a touchscreen while searching COM ports to locate the touchscreen, you should specify the COM port and IRQ when invoking the utility to avoid the conflict. 8.8 System May Hang on Restart After Install When the Setup program finishes installing TouchWare, you must restart your system to load and activate the touchscreen driver. The system may hang after the install and not restart. If this occurs, press the Reset button or toggle the On/Off switch to restart your system. 8.9 Delay in Opening Windows Touchscreen Control Panel The Windows Touchscreen control panel now displays status information about the touchscreen controller and the firmware version. If your touch system is using an older controller, the Touchscreen control panel may take longer to open than expected. The delay is a result of obtaining the controller, firmware, and frequency information. __________________________________________________________________ MicroTouch, the MicroTouch logo, Microcal, ThruGlass, and TouchWare are either registered trademarks or trademarks of MicroTouch Systems Incorporated in the United States and/or other countries. __________________________________________________________________