Logitech MouseWare 6.43 README File (c) Copyright 1994 Logitech, Inc. All Rights Reserved. ************************************************************ This README file contains important information that supplements the Logitech Mouse User's guide. To view or print this file under DOS, use README.EXE which is supplied on the installation disks. At the DOS prompt type the following: README If you are using Windows, run Write and open README.WRI. If MouseWare has already been installed, double click on the "Mouse ReadMe" icon in the Logitech SenseWare Group. ************************************************************ README FILE CONTENTS 1. WHAT'S NEW IN THIS RELEASE 1.1 One-Step Installation 1.2 Cloaking Feature 1.3 MouseWare on the Go 1.4 Windows Control Center 1.5 Windows Shortcuts 1.6 Windows Help 1.7 DOS/Windows Mouse Drivers 1.8 DOS Utilities 2. INSTALLATION NOTES 2.1 Installing Over a Previous Version of MouseWare 2.2 Uninstalling a Previous Version of MouseWare 2.3 How To Do a Network Install 2.4 Manually Decompressing Application Files 2.5 Installing the Mouse for DOS 5.0/6.0 Shell Program 3. OS/2 Support 3.1 Installing to OS/2 2.1 3.2 Win-OS/2 2.x Support 3.3 DOS Under OS/2 2.x 4. Windows NT Support 5. DOS/WINDOWS DRIVER TECHNICAL NOTES 5.1 Using Your Mouse with a Built-in Trackball 5.2 How to Attach the Mouse to COM3 or COM4 5.3 MOUSEDRV.INI Parameters 5.4 Loading the DOS Mouse Driver into High Memory 5.5 Installing Cloaking Feature 6. DOS/WINDOWS UTILITIES TECHNICAL NOTES 6.1 Smart Move Feature 6.2 Changing the Keyboard Override 7. ADI DRIVER 7.1 Installing the AutoCAD Real Mode ADI Driver 7.2 Installing the AutoCAD Protected Mode ADI Driver 7.3 Using the ADI Driver 7.4 Difference Between AutoCAD Release 11 and 12 7.5 Programming The Buttons 8. TROUBLESHOOTING 8.1 Installation Problems 8.2 Restoring AUTOEXEC.BAT, CONFIG.SYS, WIN.INI and SYSTEM.INI 8.3 Bus Mouse Conflict 8.4 Mouse Detection Problems 8.5 Renaming Installed Directory 8.6 Toshiba T3400 sub-notebooks and IBM ThinkPad 9. APPLICATION DISK CONTENTS 9.1 Mouse Driver Files 9.2 Windows Program Files 9.3 DOS Program Files 9.4 Installation Program Files ____________________________________________________________ 1. WHAT'S NEW IN THIS RELEASE MouseWare 6.43 comes in two flavors: MouseWare Enhanced and MouseWare Lite. If you have the MouseWare Lite package and wish to upgrade to the enhanced package: in the US: call Logitech's Customer Relations line at 1-800-231-7717 in Europe, Africa, and the Middle East: ++41 (0) 21 869 98 55 United Kingdom: ++44 (0) 344 89 14-52 MouseWare 6.43 works with any Logitech compatible and Microsoft compatible pointing devices. This release has several features which makes it easier to use a built- in trackball common on many notebook computers. 1.1 One-Step Installation If you are installing MouseWare for both DOS and Windows, you can install the complete software all in Windows, without being in DOS. Please make sure you run install from within Windows to get full Windows support. To install the network installable version of MouseWare, please refer to NETWORK.WRI. To view this file, use Windows' WRITE.EXE application. 1.2 Cloaking Feature The MouseWare 6.43 DOS mouse driver is designed to work in conjunction with a special interface program called "Cloaking". The CLOAKING.EXE interface program allows the DOS mouse driver MOUSE.EXE to be loaded in extended memory, freeing valuable conventional and upper memory for your DOS applications. For more information on how to install this new feature, refer to the section: "Installing Cloaking Feature." 1.3 MouseWare on the Go Whether you use a trackball on the road or a mouse back in the office, MouseWare can detect which mouse you are using and adjust the Acceleration, Mouse Speed, Button Swap and Orientation options according to your preferences. See the section "Using Your Mouse with a Built-in Trackball". 1.4 Windows Control Center The Windows Mouse Control Center has a new Smart Move feature (enhanced package only). When enabled, the cursor automatically goes to the default push button when a dialog or message box appears. See the section "Smart Move Feature". Three new Acceleration settings are selectable via the DOS Mouse Control Center and Windows Mouse Control Center (enhanced package only). Acceleration causes the cursor to move a greater or lesser distance depending on how quickly you move your mouse. 1.5 Windows Shortcuts The Windows Mouse Control Center sets the middle button to perform a Double-Click, by default. Running an application becomes as simple as moving the cursor over the application icon, then clicking the middle button. However, if you are upgrading from MouseWare 6.00 or above and already have button shortcut(s) assigned, it will preserve your existing button setting(s). The Drag Lock feature can now be assigned to the middle and/or right button(s). Drag lock lets you drag an object without having to hold down a mouse button as you move the mouse. The default Keyboard Override for temporarily disabling the Windows shortcuts is the Control key. While pressing the Control key and clicking the assigned button(s), the Windows shortcut(s) will be disabled. See the section "Changing the Keyboard Override". The new Home Cursor shortcut has been added to the Windows Mouse Control Center (enhanced package only). When assigned to a button, clicking on that button causes the cursor to jump to the middle of the screen. This feature is especially useful on monochrome monitors where it is sometimes difficult to locate the cursor. 1.6 Windows Help A redesigned Windows Help is included in the release. 1.7 DOS/Windows Mouse Drivers Both the DOS and Windows mouse drivers now use a mouse configuration file MOUSEDRV.INI. This makes it possible for both drivers to save their mouse settings and to behave similarly. The settings can also be changed via the DOS and Windows Mouse Control Centers. Advanced Power Management, which helps conserve battery power in laptops/notebooks has been added. Both the DOS and Windows mouse drivers can use COM3 and COM4. See the section "How to Attach the Mouse to COM3 or COM4". The DOS mouse parameters BON, BOFF, BLOW, and BHIGH are no longer supported. Use the AOFF, ALOW, AMEDIUM, and AHIGH parameters. DLEFT is no longer supported. See MOUSEDRV.TXT for more information on the mouse parameters. 1.8 DOS Utilities In previous releases the DOS Mouse Control Center was a terminate stay resident (TSR) program named CLICK.EXE. In this release, CLICK.EXE has been renamed to MOUSECC.EXE, and is no longer a TSR. LogiMenu and MTutor are no longer part of the release. 2. INSTALLATION NOTES 2.1 Installing Over a Previous Version of MouseWare With MouseWare 6.43, a Logitech SenseWare group is created to include the new program icons. Under Windows 3.1, the Logitech Mouse Control Center can also be accessed via Windows' Control Panel. If you've installed MouseWare 6.43 over a previous version of MouseWare, you need to restart Windows in order for the Control Panel to use the new Logitech Mouse Control Center. 2.2 Uninstalling a Previous Version of MouseWare To remove a previous version of MouseWare from your disk, first install MouseWare 6.43. At the end of the installation process, reboot your system so that the new mouse drivers will be used. To remove the old MouseWare Windows software: DEL C:\WINDOWS\LMOUSE\*.* RD C:\WINDOWS\LMOUSE DEL C:\WINDOWS\LMOUSE.DLL This example assumes the Windows directory is named C:\WINDOWS. To remove the old MouseWare DOS files: DEL C:\MOUSE\CLICK.EXE DEL C:\MOUSE\LOGIMENU.COM DEL C:\MOUSE\*.MNU DEL C:\MOUSE\GOMENU.* This examples assumes the old MouseWare software is located in the C:\MOUSE directory. 2.3 How To Do a Network Install The retail version of MouseWare is meant for a single user only. The installation instructions for the network installable version of MouseWare are in NETWORK.WRI. To view this file, use Windows' WRITE.EXE application. 2.4 Manually Decompressing Application Files Several files on the installation disk have been compressed. These files must be decompressed before you can use them. The INSTALL program automatically decompresses these files during installation. However, should the need arise, we have provided a method for you to manually decompress these files. Compressed files have file names that end with "%". To decompress a file manually, use the LGEXPAND.EXE utility provided on the installation disk. For example, to decompress the file "DGLOGI.COM" to your hard disk, type: A:\lgexpand A:\DGLOGI.CO% C:\MOUSE\DGLOGI.COM Please make sure that the destination directory (C:\MOUSE in this example) exists before you issue this command. 2.5 Installing the Mouse for DOS 5.0/6.0 Shell Program The DOS mouse driver should be loaded prior to the DOS DOSShell and not within a DOS box. Also Windows 3.x should not be launched from a DOS DOSShell. This may result in loss of mouse functionality under Windows 3.x. 3. OS/2 Support 3.1 Installing to OS/2 2.1 OS/2 2.1 has 3-button support for Logitech serial and PS/2 mouse, and 2-button support for Logitech bus mouse. OS/2 2.1 should automatically detect and support the Logitech mouse connected to your system when OS/2 is installed. If your Logitech mouse does not work properly after installing OS/2, you will have to manually select the proper Logitech mouse driver. Please follow these steps to correct the problem: 1) Determine the type of mouse you are using. If you have a PS/2 or bus mouse skip down to part 2. If you have a Logitech serial mouse you need to know if it is M-series or C-Series. Look at the bottom of your mouse, if it says "CA", "CC", "CE" or "C7" then you own a C-Series mouse, otherwise, you own an M-Series mouse. e.g. C-Series MODEL NO. C7 MODEL NO. CA e.g. M-Series M/N: M-CJ13 M/N: M-MB11 2) Double click the OS/2 System icon. 3) Double click the System Setup icon. 4) Double click the Selective Install icon. 5) Select the Mouse option and press Enter. 6) If you are using a PS/2 or M-Series serial mouse you may select any of the following: "PS/2 [tm] Style Pointing Device", "Serial Pointing Device", "Logitech M-Series Mouse". 7) Select the entry "Bus Style Mouse" if you have a bus mouse. 8) If you have a Logitech C-series mouse and are running OS/2 version 2.1, select "Logitech [tm] C- Series Serial Mouse". If, you are running version 2.0, choose "Logitech [tm] Mouse". 3.2 Win-OS/2 2.x Support In Win-OS/2 full screen mode, full functionality is available. To install MouseWare 6.43 under Win-OS/2: 1) Double click the "Command Prompts" icon on the OS/2 desktop. 2) Double click on the "Win-OS/2 full screen" icon. 3) Run the "INSTALL" program from the MouseWare 6.43 diskette. When running Windows applications from the OS/2 desktop the acceleration and speed sensitivity features will be disabled. Do not run Win-OS/2 from a DOS box while running MouseWare 6.43, your mouse will not function properly under these circumstances. 3.3 DOS Under OS/2 2.x MouseWare 6.3 DOS functionality will not be available in DOS under OS/2. Your mouse will be controlled by OS/2. 4. Windows NT Support Do not install MouseWare 6.43 in Windows NT. Use the Logitech mouse driver included in the Windows NT release. This driver has full support for all the Logitech pointing devices. To change the mouse settings, run the Windows NT control panel. 5. DOS/WINDOWS DRIVER TECHNICAL NOTES 5.1 Using Your Mouse with a Built-in Trackball If you have a PS/2 built-in trackball on your Laptop computer and you want to be able to use an external mouse connected on the serial port, you should make the following modification in the MOUSEDRV.INI file: [Global] ForcedConnection=Off SearchOrder=Serial, PS2, Bus, Inport If you have a SERIAL built-in trackball and you want to use an external mouse connected to the mouse port (PS/2) you should make the following modification: [Global] ForcedConnection=Off SearchOrder=PS2, Serial, Bus, Inport If you have a SERIAL built-in trackball and you want to use an external mouse connected to the serial port, identify which COM port is used by the built-in trackball and the external serial port (e.g. built-in trackball on COM2 and external mouse on COM1). You should make the following modification: [Global] ForcedConnection=Off SearchOrder=PS2, Serial, Bus, Inport PortSearchOrder=COM1, COM2 Note: The external COM port should be listed first in the PortSearchOrder. If your notebook allows you to set the built-in trackball or the external serial port to COM3 or COM4 with a non-standard base address and IRQ, then you should specify the values in the [COMx] section. For example, if your built-in trackball uses IRQ11 and a base address of 338 hex, add the following: [COM3] BaseAddress=338 IRQValue=11 5.2 How to Attach the Mouse to COM3 or COM4 MouseWare supports COM3 and COM4. For instance, if you are connecting your mouse to COM3 using IRQ11 and base address 338 hex, you should make the following modifications in the MOUSEDRV.INI file: [Global] SearchOrder=Serial, PS2, Bus, Inport PortSearchOrder=COM3, COM1, COM2 Connection=Serial ConnectionPort=COM3 [COM3] BaseAddress=338 IRQValue=11 Note: The COM port must be supported by your computer's configuration. The mouse driver cannot configure the COM ports for you. This value must match those used by Windows' PORTS Control Panel. 5.3 MOUSEDRV.INI Parameters See MOUSEDRV.TXT for more information on the mouse configuration file. 5.4 Loading the DOS Mouse Driver into High Memory It is recommended that you do not use "LOADHI" to load the DOS Mouse Driver, since the driver will optimize the use of available upper memory automatially, and thus freeing up conventional memory. The use of "LOADHI" with the Mouse Driver could force the driver to consume conventional memory instead of available upper memory. 5.5 Installing Cloaking Feature Cloaking works in conjunction with a supported memory manager to enable the mouse driver to load in extended memory. Without cloaking, the DOS mouse driver consumes about 27k of conventional or upper memory. Working in conjunction with the cloaking interface, however, it uses a mere 1k of conventional or upper memory! This 1k size footprint is called the stub. The main part of the DOS Mouse driver will be loaded in extended memory. If the cloaking interface is present the DOS mouse driver program will automatically load in extended memory. Compatibility: CLOAKING.EXE will work with any of the following extended memory managers: EMM386.EXE Microsoft RM386.EXE 3.03 or later Helix QEMM386.SYS Quarterdeck 386MAX.SYS Qualitas You will need to be running one of these programs in order to use CLOAKING.EXE. The EMM386.EXE program is included with DOS versions 5.0 and above, and with Windows. Installing Cloaking: MouseWare 6.43 copies CLOAKING.EXE in the mouse directory but doesn't enable cloaking. You must do it manually. Locate the line which loads your extended memory manager and insert the cloaking driver right after. Extended memory managers are generally loaded in the config.sys file. Example: DEVICE = C:\DOS\EMM386.EXE DEVICE = C:\MOUSE\CLOAKING.EXE The first line loads the EMM386 memory manager; The second line loads the cloaking driver; The DOS mouse driver MOUSE.EXE is usually loaded in AUTOEXEC.BAT. DOS Mouse Driver MOUSE.EXE Memory Management Parameters: By default, the DOS mouse driver will try to load as high as possible in memory following this order: 1) Extended memory 2) Upper memory 3) Conventional memory By default, the stub will try to load as high as possible in memory following this order: 1) Upper memory 2) Conventional memory You can customize the DOS driver memory location by using the following command line parameters: /MEMSA Loads the stub in upper memory /MEMSC Loads the stub in conventional memory /MEMA Loads the mouse driver in extended memory /MEMU Loads the mouse driver in upper memory /MEMC Loads the mouse driver in conventional memory Example C:\MOUSE\MOUSE /MEMU /MEMSC It should be noted that if the driver can not be loaded in the region specified, it will automatically attempt to load in the next lowest region of memory. Troubleshooting: If you experience difficulties with the cloaking driver, your system might be incompatible with the current version of the cloaking driver. To disable the cloaking driver: If you run DOS 6.0 or above: 1. Reboot your computer; 2. During the reboot process press the F5 key to disable CONFIG.SYS and AUTOEXEC.BAT; 3. Edit CONFIG.SYS and remove the cloaking driver line. If you run DOS 5.0 or under: 1. Reboot your computer; 2. During the reboot process press simultaneously the CTRL SHIFT ALT key. This will prevent the cloaking driver from loading; 3. Edit CONFIG.SYS and remove the cloaking driver line. 6. DOS/WINDOWS UTILITIES TECHNICAL NOTES 6.1 Smart Move Feature When Smart Move (enhanced package only) is enabled, the cursor automatically goes to the default push button when a dialog or message box appears. For some applications that use non-standard dialog boxes and/or non-standard buttons, this feature may not work all the time. If the dialog box does not have a default command button, Smart Move moves the cursor to the first button it finds. The cursor is not moved if it cannot find a button. If you prefer to have the cursor move to the center, or upper left corner of the dialog box if no button is found, use a text editor like Notepad and edit the file MOUSECC.INI. [Button Assignments] MoveTo=Center or MoveTo=TopLeft To set it back to default, remove the "MoveTo=" line. 6.2 Changing the Keyboard Override The Keyboard Override for temporarily disabling the Windows shortcuts is the Control key, by default. If you would like to change it to the Shift key or set it to none, use a text editor like Notepad and edit the file MOUSECC.INI. [Button Assignments] Disabler=Shift or Disabler=Off To set it back to default, remove the "Disabler=" line. 7. ADI DRIVER 7.1 Installing the AutoCAD Real Mode ADI Driver Copy and decompress the real mode AutoDesk Device Interface (ADI) driver DGLOGI.COM to a directory in your PATH variable, or simply copy it to your MOUSE directory. Make sure you load DGLOGI.COM after you already loaded the DOS mouse driver. You may want to edit your AUTOEXEC.BAT file and add the line: DGLOGI after the MOUSE command line. While in AutoCAD, configure your digitizer to ADI digitizer or AutoDesk Device Interface (depending on your release), and select the default interrupt (0x79). You can set the ADI sensitivity by loading the Real Mode ADI driver as follows: DGLOGI Snnn where nnn is a number between 1 and 100. The default is 50. To remove DGLOGI.COM from memory, type 'DGLOGI OUT' or 'DGLOGI OFF'. 7.2 Installing the AutoCAD Protected Mode ADI Driver Copy and decompress the protected mode ADI driver DGLOGI.EXP to your ACAD directory or to its drivers sub- directory, depending on your AutoCAD release. AutoCAD Release 11 requires that the protected mode ADI driver be placed in the same directory as AutoCAD OR in the path specified by the environment variables ACAD, ACADCFG, OR the driver may be specified exactly by setting the DGPADI environment variable to point to DGLOGI.EXP with the absolute path, for example: SET DGPADI=C:\ACAD\DGLOGI.EXP AutoCAD Release 12 creates a directory specifically for drivers, therefore you should copy DGLOGI.EXP into that directory. While in AutoCAD, run CONFIG to properly configure the driver. Make sure you select the "Logitech Enhanced" driver. 7.3 Using the ADI Driver The Logitech Real Mode ADI driver is compatible with all versions of AutoCAD, as well as other AutoDesk products such as AutoSketch, or AutoShade. The Logitech Protected Mode ADI driver is compatible with AutoCAD releases 11 and 12. Both the real and the protected mode ADI drivers require that you load the Logitech DOS mouse driver prior to using the ADI drivers. Both drivers combine keyboard shift states with mouse buttons to produce 16 ADI button events for complex AutoCAD menu handling. This allows you to access common AutoCAD commands without taking your hands off the mouse. Please refer to your AutoCAD Reference Manual, under Button Menu section. These drivers also work with 2-button mice by simulating a middle button when you click both buttons at once. The Button Menu map is as follows: BUTTON COMBO DEFAULTS -------------------------------------------------- PICK = Left Pick 1 = Right Return 2 = Middle Menu (Cursor menu in ACAD11) 3 = Ctrl + Left Cancel 4 = Ctrl + Right Snap On/Snap Off 5 = Ctrl + Middle Ortho On/Ortho Off 6 = Alt + Left Grid On/Grid Off 7 = Alt + Right Coordinates On/Coordinates Off 8 = Alt + Middle ISO Plane Top/ ISO Plane Right/ ISO Plane Left 9 = Ctrl + Alt + Left Tablet Off 10 = Ctrl + Alt + Right 11 = Ctrl + Alt + Middle 12 = Shift + Left 13 = Shift + Right 14 = Shift + Middle 15 = Ctrl + Shift + Left 7.4 Difference Between AutoCAD Release 11 and Release 12 In AutoCAD Releases 11, the Logitech Real Mode Mouse Driver is: 3] AutoCad Device Interface. In AutoCad Release 11, the Logitech Mouse Driver for the Enhanced mode (386 and above) selection is: 2] ADI P386 Digitizer. In AutoCad Releases 12, the Logitech Real Mode Mouse Driver is: 2] ADI Digitizer (Real Mode). In AutoCad Release 12, the Logitech Mouse Driver for the Enhanced mode (386 and above) selection is: 8] Logitech Enhanced Mouse Driver ADI 4.2 V1.0 - By Logitech. Suggested sensitivity settings for the Logitech Mouse: Sensitivity - 100 Ballistics - High 7.5 Programming The Buttons According to AutoDesk, the user cannot change the button defaults in AutoCAD Release 11. The mouse buttons CAN be changed within AutoCAD Release 12. Changing the mouse buttons is documented in the AutoCAD Customization Manual, in the Custom Menus chapter (chapter 6), beginning on page 82. More information is available in the AutoCAD Interface, Installation, and Performance Guide, in the Using AutoCAD 386 chapter (chapter 5), beginning on page 77, and the AutoCAD Reference Manual, in the AutoCAD Drawing and Interface chapter (chapter 3), on page 58. 8. TROUBLESHOOTING 8.1 Installation Problems Before running INSTALL, please make sure you have at least 20 file handles in your CONFIG.SYS. Add this line to your CONFIG.SYS if not already present: FILES=20 Should your system lock up at the end of the Windows installation, you may experience some difficulty trying to relaunch Windows. If this should happen, perform the following steps: 1)From DOS, enter the directory that you installed MouseWare to. This directory is C:\MOUSE by default. 2)Type the following command and press enter: POSTCOPY 3)The installation is now complete. 8.2 Restoring old AUTOEXEC.BAT, CONFIG.SYS, WIN.INI and SYSTEM.INI The installation program saves these files starting with the .000 extension, and increments it to the next available numbered extension if it finds an existing file with the same name and extension. 8.3 Bus Mouse Conflict If you have a Bus Mouse with its jumper set on IRQ 2, you may experience compatibility problems when starting Windows. Some video boards (EGA, VGA) may use IRQ 2. The problem can be solved by changing the IRQ selection jumper on your Bus board to another interrupt not in use. Consult your video user's manual for more information. 8.4 Mouse Detection Problems Mouse connected to the Mouse Port (PS/2 port): If your mouse is connected to the mouse port and is not detected by the system, attempt the following step(s): 1)Your mouse port might need to be enabled through the SETUP menu of your computer (please check with the documentation of your computer on the usage of SETUP menu). 2)If you have a mouse with both serial and mouse port adapters, connect it to the computer through the serial port. Reboot and check if the mouse is detected properly. 3)If you must connect the mouse through the mouse port, add the following modification to the MOUSEDRV.INI file, reboot and check if the mouse is detected properly: [Technical] ForcePS2EquipmentFlag=On If the problem persists, please check for a possible computer BIOS ROM upgrade from your computer manufacturer. Some notebook type systems such as IBM Thinkpad have both an external Mouse Port and an integrated Pointing Stick which is connected to the Mouse Port. If your mouse is having difficulty running on the Mouse Port of such a system, try using the serial port instead. Mouse connected to the Serial Port: If your mouse is connected to the serial port and is not detected by the system, add the following modification to the MOUSEDRV.INI file, reboot and check if the mouse is detected properly: [Technical] Timing=Software For more information on MOUSEDRV.INI, please refer to MOUSEDRV.TXT. 8.5 Renaming Installed Directory If you accidentally renamed your MOUSE directory without modifying the Windows INI files, it may cause Windows to not run at all, because it would not be able to find the Mouse Drivers. You should then run INSTALL from the MouseWare diskette, follow the instructions to re-install, and make sure you select installing also the Windows Drivers. 8.6 Toshiba T3400 sub-notebooks and IBM ThinkPad Mouse connected to the mouse port (PS/2 port): If the "pointing device mode" parameter in the computer's setup is set to "simultaneous", an external mouse connected to the mouse port will be identified as a generic two-button mouse. If this external mouse has three buttons, the following modifications should be made to the MOUSEDRV.INI file: [PS2] NumberOfButtons=3 ButtonMapping=3Key The connected device model may also be specified. For more information on the MOUSEDRV.INI file, please refer to the MOUSEDRV.TXT file. 9. APPLICATION DISK CONTENTS 9.1 Mouse Driver Files LMOUSE.DRV Windows Mouse Driver (for Windows 3.0 or greater) LVMD.386 Windows Virtual Mouse Driver (for Windows 3.0 or greater for 386 enhanced mode) MOUSE.EXE Logitech DOS Mouse Driver MOUSEDRV.INI Mouse driver configuration file MOUSEDRV.TXT Text file documenting MOUSEDRV.INI and MOUSE.COM parameters. 9.2 Windows Program Files WMOUSECC.EXE Mouse Control Center WMCCDLG.DLL WMOUSECC.HLP Mouse Help File WBUTTONS.EXE Mouse Control Center Button Engine WBUTTONS.DLL WCURSOR.EXE Cursor Enhancement Program WCURSOR.DLL (enhanced package only) 9.3 DOS Program Files MOUSECC.EXE DOS Mouse Control Center COMCHECK.EXE Tests the Connection of Your Serial Mouse DGLOGI.COM Real Mode ADI v4.1 Compliant Driver DGLOGI.EXP Protected Mode ADI v4.2 Compliant Driver 9.4 Installation Program Files INSTALL.EXE Windows/DOS Installation Program INSTALL.INF NETWORK.WRI Documents INSTALL.INF (use Windows' WRITE.EXE to view) DINST.EXE DOS Installation Program DINST.SCR DINST.CFG README.EXE Readme File Viewer README.TXT Readme File README.WRI Readme File (Use Windows' WRITE.EXE to view)