Mouse Failure – Symptoms and Troubleshooting

Introduction

As software packages evolved beyond simple menus and began to make use of the powerful graphics systems coming into popular use during the mid-1980s (i.e., EGA and VGA graphics), ever-larger amounts of information were presented in the display. Simple, multi-layered text menus were aggressively replaced with striking graphic user interfaces (GUIs). System options and selections were soon represented with symbols (graphic “buttons” or “icons”), instead of plain text. Using a keyboard to maneuver through such visual software soon became a cumbersome (if not impossible) chore.

Peripherals designers responded to this situation by developing a family of pointing devices. Pointing devices use a combination of hardware and software to produceand control a graphical screen cursor. A software device driver generates the cursor and reports its position. As the pointing device is moved around, hardware signals from the pointing device are interpreted by the device driver, which moves the cursor in a similar manner. By positioning the cursor over a graphic symbol and activating one, two, or three of the buttons on the pointing device, it is now possible to select (i.e., “click” or “doubleclick”) and manipulate (i.e., “drag”) options in the application program instead of using a keyboard.

Three factors are needed to make pointing devices work: the physical signal-generating hardware itself, a software driver (the “device driver”), and the application program must be written to make use of the device driver. If any of these three items are missing, the pointing device will not work. This chapter looks at the technology, maintenance, and troubleshooting of two popular pointing devices: the Mouse and the trackball.

The Mouse

Although the development of computer pointing devices has been ongoing since the early 1970s, the first commercial pointing devices for IBM-compatible systems were widely introduced in the early 1980s. The device was small enough to be held under your palm, and your fingertips rested on its button(s). A small, thin cord connected the device to its host computer. The device’s small size, long tail-like cord, and quick scurrying movements immediately earned it the label of Mouse. Every Mouse needs at least one button. By pressing the button, you indicate that a selection is being made at the current cursor location. Many Mouse-compatible software packages only use a single Mouse button even to this day. A two-button Mouse is more popular (reflecting the endurance of the Mouse design) because a second button can add more flexibility to the Mouse. For example, one button can work to “select” an item; the second button can be used to “deselect” that item again or to activate other menus and options.

A few Mouse designs use three buttons, but the third button is rarely supported by application programs, aside from CAD or high-end art applications. 

Mouse Gestures

The first Mouse “gesture” is called clicking, which is little more than a single momentary press of the left Mouse button (on a two-button Mouse). Clicking is the primary means of making a selection in the particular application program. The second common gesture is doubleclicking, which is simply two single clicks in immediate succession. A doubleclick also represents selection, but its exact use depends upon the application program. The third type of Mouse gesture is the drag, where a graphical item can literally be moved around the display. Dragging is almost always accomplished by pressing the left Mouse button over the desired item, then (without releasing the button) moving the item to its new location. When the item moved to its new position, releasing the left Mouse button will “drop” the item in that location.

It is interesting that pen gestures are interpreted by the computer’s operating system, but Mouse movements and button conditions are handled by the actual application program (such as a word processor or game). Thus, the same Mouse gestures can be made to represent different actions, depending on which program is executing.

Cleaning a Pointing Device

Pointing devices are perhaps the simplest peripheral available for your computer. Although they are reasonably forgiving to wear and tear, trackballs and mice can easily be fouled by dust, debris, and foreign matter introduced from the ball. Contamination of this sort is  almost never damaging, but it can cause some maddening problems when using the pointing device. A regimen of routine cleaning will help to prevent contamination problems.

You can use pre-fabricated Mouse cleaning kits to speed the cleaning process. Turn your small-computer off before performing any cleaning procedures:

·         Remove the ball A ball is held in place by a retaining ring. For a Mouse, the retaining ring is on the bottom. For a trackball, the ring is in the top. Rotate the ring and remove it gently—the ball will fall out. Place the retaining ring in a safe place.

·         Clean the ball Wash the ball in warm, soapy water, then dry it thoroughly with a clean, lint-free towel. Place the ball in a safe place.

·         Blow out the dust Use a can of photography-grade compressed air to blow out any dust or debris that has accumulated inside the pointing device. You might want to do this in an open or outdoor area.

·         Clean the rollers Notice that the Mouse has three rollers: an X roller, a Y roller, and a small pressure roller that keeps the ball pressed against the X and Y rollers. Use a

·         Cotton Swab dipped in isopropyl alcohol to clean off any layers of gunk that might have accumulated on the rollers.

·         Reassemble and test Allow everything to dry completely, then replace the ball and retaining ring. Then test the pointing device to be sure that it is performing as expected.EM DATA AND TROUBLESHOOTING

Troubleshooting a Pointing Device

The weakest link in a pointing system is the peripheral pointing device itself. Few peripheral devices are subjected to the wear and general abuse seen by trackballs or mice. They are dropped, yanked, and moved constantly from place to place. Damage to the device’s PC board, cabling, and connector is extremely common because of abuse. Accumulations of dust and debris can easily work into the housing and create havoc with the rubber ball, tracks, and rollers. Hardware conflicts and driver-configuration issues can also result in limitless problems. This part of the chapter guides you through some simple troubleshooting techniques for your trackball and Mouse.

Mouse/Trackball Interfaces

From time to time, you might need to check the physical interface on a Mouse or trackball. At its core, the Mouse uses a simple serial device—that is, it can pass serial data back and forth with the host computer using communication protocols managed by the Mouse  driver. Three types of Mouse interfaces are common in the field: serial mice, bus mice, and PS/2 mice. This part of the chapter highlights the pinouts for each interface type.

Serial mice A “serial” Mouse connects to an existing RS232 serial port at the PC (usually COM1 or COM2) using a standard DB-9F (9-pin female) or DB-25F (25-pin female) connector. Table 25-1 lists the pinout for a Logitech Type M, V, or W serial Mouse connector. Bus mice In many circumstances, it is not possible to use a serial Mouse on an open COM port, and the PC is not fitted with a PS/2 port. In this case, it might be necessary to use a “bus Mouse,” which basically involves using a stand-alone Mouse-controller board (a bus Mouse controller) and a Mouse fitted with a bus Mouse connector—usually a male sub-miniature “D”-type connector or a miniature male DIN (circular) connector. Be careful not to mistake the 9-pin DIN connector of a bus Mouse for the 6-pin circular connector of a PS/2 Mouse.

Symptoms

Symptom 25-1. The Mouse cursor appears, but it only moves erratically as the ball moves (if at all) This Symptom might occur in either the horizontal or vertical axis. This Symptom suggests that an intermittent condition is occurring somewhere in the pointing device. You should not have to disassemble your computer during this procedure. Start your investigation by powering down the computer. Check the device’s cable connector at the computer. Be sure that the connector is tight and inserted properly. If you are in the habit of continually plugging and unplugging the Mouse/trackball, excessive wear can develop in the connector pins over time. If the connector does not seem to fit tightly in the computer, try a new pointing device.

More likely, the device’s rollers are not turning, or are turning only intermittently. In most cases, roller stall is caused by a dirty or damaged ball, or an accumulation of dirt blocking one or both sensors. Clean the ball and blow out any dust or debris that might have settled into the Mouse/trackball housing. Refer to the preceding section on cleaning and attempt to clean the device thoroughly. Never use harsh solvents or chemicals to clean the housings or ball.

If you have the Mouse connected to a standard serial communication port (a COM port), you should check that no other devices are using the same interrupt (IRQ). For example, COM1 and COM3 use the same IRQ, while COM2 and COM4 share another IRQ. If you have a Mouse on COM1 and a modem on COM3, there will almost invariably be a hardware conflict. If possible, switch the Mouse (or conflicting device) to another port and try the system again. 

844 Mice And Trackballs

Configuring MouseKeys operation.

If no hardware conflict occurs, and cleaning does not correct an intermittent condition, remove the device’s upper housing to expose the PC board, and use your multimeter to check continuity across each wire in the connecting cable. Because you probably will not know which connector pins correspond to which wires at the sensor PC board, place one meter probe on a device’s wire and “ring-out” each connector pin until you find continuity. Make a wiring chart as you go. Each time you find a wire path, wiggle the cable to stimulate any possible intermittent wiring. Repair any intermittent wiring, if possible. If you cannot find continuity or repair faulty wiring, simply replace the pointing device. 

Symptom 25-2. One or both buttons function erratically (if at all) Buttons are prone to problems from dust accumulation and general contact corrosion. Your first step should be power down your computer and disconnect the pointing device. Remove the ball and upper housing to expose the PC board and switches. Spray a small amount of electronics- grade contact cleaner into each switch, then work each switch to circulate the cleaner.

If cleaning does not improve intermittent switch contacts, you might wish to check continuity across the connecting cable. With the ball and housing cover removed, use your multimeter to check continuity across each wire in the connecting cable. Because you probably do not know which connector pins correspond to which wires at the device, place one meter lead on a device wire and “ring-out” each connector pin until you find continuity.

Once you find continuity, wiggle the cable to stimulate any possible intermittent wiring. Repair any intermittent wiring if you can, or simply replace the pointing device. 

Symptom 25-3. The screen cursor appears on the display, but it does not move If the cursor appears, the device driver has loaded correctly and the application program is communicating with the driver. Your first step should be to suspect the serial connection. If there is no serial connection, however, no pulses will modify the cursor’s position. If you find a bad connection, power down your computer before reattaching the device’s serial connector, then restore power and allow the system to reinitialize.

If the device is attached correctly to its proper serial port, the problem probably exists in the pointing device’s wiring. Remove the ball and upper housing to expose the PC board, then use your multimeter to check continuity across each wire in the connecting cable. Because you probably do not know which connector pins correspond to which wires in the device, place one meter lead on a device wire and “ring-out” each connector pin until you find continuity.

Once you find continuity, wiggle the cable to stimulate any possible intermittent wiring. Repair any intermittent or open wiring if you can, or simply replace the pointing device.

Symptom 25-4. The Mouse/trackball device driver fails to load The device driver is a short program that allows an application program to access information from a pointing device. Most computer users prefer to load their device drivers during system initialization by invoking the drivers in the CONFIG.SYS or AUTOEXEC.BAT files. Most drivers are written to check for the presence of their respective device first—if the expected device does not respond, the driver will not be loaded into memory. Other drivers load blindly, regardless of whether the expected device is present or not.

If the device driver fails to load during initialization, your pointing device might not have been detected. Power down your computer and check the connection of your pointing  device. Ensure the device is securely plugged into the proper serial port (or other

Troubleshooting A Pointing Device 845

Mouse port). If the device is missing or incorrectly inserted, install or re-secure the pointing device and allow the system to re-initialize. If you see a “File not found” error message displayed at the point your device driver was supposed to load, the driver might have been accidentally erased, might be corrupted, or might be located in a sub-directory where the CONFIG.SYS or AUTOEXEC.BAT files are not looking. Try re-installing a valid copy of your Mouse device driver and ensure that the driver is located where your calling batch file can access it. Reboot your system.

Most well-designed application programs check for the presence of a pointing device through the device driver during initial program execution. If the application program aborts or fails to execute because of a “No Mouse found” or “No Mouse driver” error, return to the preceding paragraphs and recheck the device and driver installation.

Symptom 25-5. You see a “General protection fault” after installing a new Mouse and driver under Windows First, this is probably not a hardware fault (although it would be helpful to check any Mouse driver command line switches in CONFIG.SYS or AUTOEXEC.BAT). It is more likely that the new Mouse driver is conflicting with one or more applications. Try several different applications—most will probably work just fine. Check with the Mouse manufacturer to see if there are any other reported problems, and find if any patches are planned. If you have an older version of the Mouse driver available, try replacing that one. An older driver might not work as well as a newer one, but it might not suffer from this kind of compatibility problem. If no patches or older drivers are available, you might be forced to change the Mouse and Mouse driver to something completely different to eliminate the problem.

Symptom 25-6. You see an error: “This pointer device requires a newer version” In virtually all cases, you have the wrong driver installed on the system for your driver. Check the driver and be sure that the driver you are using is appropriate for the particular Mouse. For example, a Logitech or Genius Mouse selected in Windows setup can cause this kind of problem if you have a Microsoft Mouse on the system. Change the Mouse type under Windows. Under Windows 95, you’ll need to remove the old Mouse reference from the Device manager, then use the Add new hardware wizard to install the new Mouse manually.

Symptom 25-7. You see an error: “Mouse port disabled or Mouse not present” This is almost always a connection or setup problem. Check the signal connector first. Be sure the Mouse cable is not cut or damaged anywhere, and see that it is attached securely to the serial or PS/2 port. Many newer system BIOS versions now provide an option in the CMOS setup for a Mouse port. Check the CMOS setup and see that any entries for your Mouse are enabled properly.

Symptom 25-8. The Mouse works for a few minutes, then stops When the computer is rebooted, the Mouse starts working again. This problem often plagues cutprice mice, and is almost always caused by buildups of static in the Mouse. The static charges are interfering with the Mouse circuitry, causing the Mouse to stop responding (though charges are not enough to actually damage the Mouse). There are generally three ways to resolve the problem: (1) spray the surrounding carpet and upholstery with a very dilute fabric softener to dissipate static buildup, (2) hire an electrician to ensure that the 

846 Mice And Trackballs

Computer and house wiring are grounded properly, or (3) replace the Mouse with a more static-resistant model.

Symptom 25-9. You attempt a doubleclick but get quadrupleclick, or you attempt a singleclick and get a doubleclick This is a phenomenon called “button bounce,” and is the result of a hardware defect (broken or poorly buffered Mouse buttons).

You might be able to clean the Mouse buttons by spraying in some good-quality electronicgrade contact cleaner. Otherwise, you’ll need to replace the Mouse outright.

Symptom 25-10. A single Mouse click works, but doubleclick doesn’tWhen this problem occurs, it is almost always because the “doubleclick speed” is set too high in the Windows 95 Mouse control panel. Try setting it lower. Click Start, select Settings, then open the Control panel. Doubleclick the Mouse icon and adjust the Doubleclick speed slider under the Buttons tab.

Symptom 25-11. A PS/2 Mouse is not detected by a notebook PC under Windows 95 There is a known problem with PS/2 Mouse detection on a Toshiba portable computer under Windows 95. You can usually correct the problem by taking the following steps:

1.      Shut down the computer entirely and physically disconnect the PS/2 Mouse from the PS/2 port.

2.      Restart the PC to the DOS mode and create backup copies of your CONFIG.SYS and AUTOEXEC.BAT files.

3.      Restart Windows 95 (reboot the PC, if necessary).

4.      Click Start, select Settings, open the Control panel, and doubleclick on the System icon.

5.      Select the Device manager tab and doubleclick the Mouse entry.

6.      Select the Mouse entry that is not being detected (i.e., “Toshiba AccuPoint”), and click Remove.

7.      Select and remove any other Mouse entries.

8.      Shut down the computer and reconnect the Mouse, then turn the PC back on.

9.      When the system reboots, it should detect the Mouse and attempt to reinstall the appropriate drivers. If this doesn’t fix the problem, a hardware issue could exist. Try a different PS/2 Mouse (preferably from a manufacturer different than the current one). If a different make and model PS/2 Mouse does not work, the PS/2 port might require service.

Symptom 25-12. Mouse pointer options are not saved This is a known problem when you use the “extra points” features in the Mouse Manager program included with the Microsoft Mouse driver. The pointer options are not saved or written to the MOUSE.INI file when you are running a virus-protection program, such as Microsoft Anti-Virus (MSAV) or Norton Anti-Virus (NAV). To correct this problem, remove the CHKLIST.MS or CHKLIST.CPS file in the directory, which contains the Mouse files. To determine the location of that directory, type “set” at the MS-DOS command prompt—it will return a list of locations of various files and memory strings. Look for the MOUSE= 

Troubleshooting A Pointing Device 847 TROUBLESHOOTING

Line, then go to that directory and delete the CHKLIST.MS or CHKLIST.CPS file. Reboot the system and try saving options again.

Symptom 25-13. Clicking the right Mouse button doesn’t start the default context menus of Windows 95 If the Mouse Manager software you’re running is using an assignment set for the right button, this assignment will override the Windows 95 default setting of “context menus.” Open the Mouse Management software utility and change the assignment for the right button to “Unassigned.” Save your changes. The right Mouse button will now access the default context menus.

Symptom 25-14. The modem won’t start after installing new Mouse software For example, this is a known problem when installing Logitech’s MouseWare 6.60 (or later) under Windows 95. Sometimes the Mouse drivers might detect the modem as a second Mouse and try to initialize it. This can cause the modem to go into a busy state. However, you can prevent the Mouse drivers from searching the serial port that the modem is using:

1.      Download the current Mouse driver for Windows 95.

2.      Edit the Windows 95 registry by clicking on the Start menu and selecting Run.

3.      Type “C:.EXE” on the Open line.

4.      Click OK. The Registry Editor program will start.

5.      Doubleclick on the HKEY_LOCAL_MACHINE folder.

6.      Doubleclick on the Software folder.

7.      Doubleclick on the manufacturer’s folder (i.e., Logitech).

8.      Doubleclick on the manufacturer’s driver folder (i.e., MouseWare).

9.      Doubleclick on the CurrentVersion folder.

10.  Click on the Global folder.

11.  Let’s assume the Mouse is on COM1 and the modem is on COM2. On the right side of the screen will be a list of value data strings. Doubleclick on the PortSearchOrde string. An Edit string dialogue box will appear. The Value data line will read: COM1, COM2

12.  Remove the space, the comma, and “COM2,” so the line reads: COM1

13.  If you only plan to use one Mouse on the system, change the Maximum Devices value data line to “1” using the same steps. This will tell the driver to stop searching for additional mice after the primary Mouse has been found.

14.  14 . Click OK, and the values under the data value section on the right side of the screen should change. Exit the registry editor (saving is automatic). Shut down the computer and reboot from a cold start so that your changes can take effect.

If you are not using a serial Mouse, remove “Serial” from the “SearchOrder” value data line so that no serial devices are searched for at all. In general, remove any reference to the port that the modem is using.

Symptom 25-15. A two-button “First Mouse” refuses to work on a Packard  Bell system The pointer doesn’t move, but Windows 95 did not report any Proble m detecting the Mouse. This is a known problem with some Packard Bell computers and the two-button “First Mouse” serial version (M/N: M34). It might be possible to work around the problem by pressing <Ctrl>+<Esc> to open the Start menu. Using the arrow keys, highlight Settings, then Control panel, and press the <Enter> key. Select the Mouse icon with the arrow keys, and press the <Enter> key. This will open the Mouse properties dialog box. “Tab over” to the Quick setup tab. Then, (using the right arrow key) open the Devices tab. Once on the Devices tab, “Tab over” to the Add Mouse button and press the <Enter> key. The Mouse-control software should now detect the two-button serial Mouse, and the pointer should now move properly. Unfortunately, you’ll need to perform this procedure each time you restart the system. Otherwise, you should try disabling the built-in serial port and install a different serial card.

You might also exchange the serial version for a PS/2 version, if your system has a dedicated PS/2 style Mouse port (be sure to uninstall the Mouse software if you plan to exchange the Mouse). Go to the Windows 95 Control panel and launch the Add/remove programs icon. Select the Mouse product (i.e., “Logitech MouseWare”) and click on the

Add/remove button. When the message “Uninstall Completed” appears, reboot the system.

Symptom 25-16. A Logitech three-button Mouse refuses to work on a Packard Bell computer You install a Logitech three-button Mouse on a Packard Bell computer, and when you open the Enhanced Mouse control center on the Devices tab, it states: “Pointing device on unknown port.” It also shows only a two-button Mouse. In virtually all cases, you’ll need to tweak the Registry:

1.      Click on the Start menu and select Run.

2.      Type “C:.EXE” on the Open line.

3.      Click OK. The Registry editor program will start.

4.      Open the Hkey_Local_Machinennnn>folder (where <nnnn>is an incremental fourdigit number starting at 0000).

5.      Click on each folder under the Mouse folder and delete them until no 000X folders remain.         

6.      Exit the Registry (saving is automatic) and reboot the system from a cold start.

7.      Open the Enhanced Mouse control center to verify the correct detection of the pointing  device.

Symptom 25-17. The Mouse pointer moves only vertically The Mouse is connected to a PS/2 port under Windows 95. If the Mouse works along one axis but not the other, it’s usually because of a hardware problem—either the Mouse needs to be cleaned or repaired. However, in some cases a software-configuration problem can occur when the Mouse driver (i e., Mouse Power v9.5) is installed on a system with Plug-and-Play BIOS running Windows 95, and the Mouse is connected to the PS/2-style Mouse port. As soon as you touch the Mouse, the pointer darts over the right edge of the screen, and then will move only up and down.

1.      To regain control over your computer, reboot in Safe mode.

2.      Click Start, then Run, then type “REGEDIT” and press <Enter>.

3.      Open the HKEY_LOCAL_MACHINE folder and see if “BIOS” is listed under  Enum. If it is, then you know the software configuration is causing the problem.

4.      Open HKEY_LOCAL_MACHINEPNP0F13, and look for a key (usually “05” or “07”) under “*PNP0F13.” Click on this key to highlight it. The key under “*PNP0F13” should now be highlighted, and the corresponding values should be displayed on the right side of the window. Notice that “string values” have an “ab” icon next to them and “binary values” have a “011” icon next to them.

5.      Compare your values to those shown. Edit your entries until all your values shown  on the screen match these values:

6.      Open HKEY_LOCAL_MACHINE. There should be multiple keys under Mouse (such as “0000” and “0001”). All but one are to be deleted. Carefully determine which one pertains to your current Mouse (by looking at the values associated with each key), and delete all keys under Mouse, except the related one.

7.      Be sure that the one remaining key under Mouse is labelled “0000” (rename it, if necessary).

8.      Click on theX box in the far upper-right corner of the Registry editor to close it.

9.      Reboot the computer from a cold start. The computer should reboot in normal mode, and the problem with the Mouse and keyboard should be gone.

Share on FacebookPlus on Google+

SUBSCRIBE TO OUR NEWSLETTER