Mouse Driver Software

To function properly, the mouse requires the installation of a device driver. In DOS, you must load

the driver manually through your CONFIG.SYS or AUTOEXEC.BAT file, but the driver is automatically

loaded in all versions of Windows. For maximum utility in both Windows and command-prompt sessions

run under Windows, use the latest version of the manufacturer’s mouse driver for the version of

Windows you are using. You need to use a driver such as MOUSE.COM only if you are using a DOS

application you run by booting the system directly to a DOS prompt in Windows 9x. Windows drivers

support the use of the mouse in DOS applications running under Windows by default.

If you need to use a mouse driver when you boot to a command prompt in Windows 9x/Me, the easiest

way to enable the driver is to add it to your CONFIG.SYS or AUTOEXEC.BAT file; I recommend adding

the driver that runs from a command prompt (often called MOUSE.COM) to your AUTOEXEC.BAT file.

For example, if the mouse driver is installed in a folder called \MOUSE on your C: drive, you would add

this line to your AUTOEXEC.BAT file:

C:\MOUSE\MOUSE.COM

This loads the DOS mouse driver into RAM when you boot the computer. One long-time problem

with mouse drivers has been the amount of conventional memory (memory below 640KB) used by

the mouse driver.

One of the biggest problems with the separate mouse driver is getting it loaded into an upper memory

block (UMB) to free up conventional memory. The older Microsoft mouse drivers—versions 9.0 and

earlier—require a large block of 40KB–56KB UMB to load; upon loading, they shrink down to less

than 20KB. Even though they take only 20KB or less after loading, you still need a very large area to

get them “in the door.”

The best tip I can give you for these separate drivers is to use the newest drivers available from

Microsoft or Logitech because they use less conventional memory than earlier versions. If you need

just the MS-DOS mouse drivers, you can download version 11.00 or above from the Microsoft Web

site. The IntelliPoint driver for 32-bit versions of Windows also includes MS-DOS driver support.

Logitech’s MOUSE.EXE MS-DOS mouse driver also can be loaded into UMBs, and all current versions

of MouseWare (6.43 and above) include the CLOAKING.EXE device driver to enable the Logitech

mouse driver to be loaded into extended memory to save even more conventional/UMB space. See

the Readme.txt file included in the Windows 3.1 folder of the MouseWare CD-ROM for details.

Keep in mind that you can use only serial or PS/2 port mice with MS-DOS; USB mice will not work.

Also, all mice are treated as two-button mice by the MS-DOS drivers unless you install Logitech menu

software to activate the middle button. (For more information, see the section “Taking Advantage of

Unused Upper Memory,” in Chapter 6, “Memory.”)

After placing the proper driver load command in your

system with the mouse connected and ensure the driver loads properly. If the proper command is in

place and the driver is not loading, watch your video screen as your system boots. At some point, you

should see a message from the mouse driver indicating that it is loaded. If you see a message indicating

that the driver failed to load, you must determine why. For example, the driver might not be

capable of loading because not enough memory is available. After you determine why the driver is

not loading, you need to rectify the situation and make sure the driver loads.

DOS Application Software

If your mouse does not work with a specific piece of DOS application software, check the setup information

or configuration section of the program. Be sure to indicated to the program (if necessary)

that you are using a mouse. If it still does not work and the mouse works with other software you are

using, contact the technical support department of the application software company.CONFIG.SYS or AUTOEXEC.BAT file, reboot the