How to deal with the discord relationship between modem and mouse

A lot of external devices are used in the computer, but these external devices don't have the imaginary harmony, they will also quarrel. Normally, the use of MODEM is to make it easier for multiple machines to access the Internet, but no one has ever imagined that this MODEM will conflict with its own mouse. So what is going on? Let's use the case to analyze it for you!

I have a 33.6Kbps built-in cat and a PS/2 with a TP-LINK (using the Cirrus chip). The mouse, then the mouse is broken, I went to the computer city to buy a new mouse port, but unexpected things happened. After the mouse is bought back, it is connected to the COM1 port on my Gigabyte HX motherboard (HX chip, integrated S3V64+ graphics card, COM2 position is occupied by the VGA port, so only one COM1 port is left), boot into Win98, recognized as “Standard Serial mouse” type mouse, it is also very easy to use. The next day I was ready to go online. When I dialed the MODEM, the mouse suddenly failed! No matter how I shake it, it didn't help. Then I used the keyboard to force the connection to close, and the mouse suddenly “lived”! This is too strange! Connect again! The mouse is "dead". Restart! The mouse still can't be used! Reinstall Win98 and Kitten drivers! Hey! Just a dial-up mouse is dead.

This situation on the surface is that MODEM and the mouse have software or hardware conflicts, but reinstalling WinXP can not solve the problem. The hardware quality problems of MODEM and mouse are definitely excluded, because they only conflict when dialing a connection. Would it be that the MODEM driver has a bug? I opened the MODEM driver and looked at it. The date of the release turned out to be November 1997, which is definitely not compatible. So I borrowed a PS/2 mouse from my friend, went online to find a new driver, and finally downloaded the latest driver on Cirrus' own website. But after installing the dial-up mouse, it still can't be used! This can tell me how to do it! At this time, I suddenly remembered that I had read an article about the COM camera that cannot be used by the COM port caused by the improper BIOS setting of the motherboard. It is the COM port usage problem of my integrated motherboard, but I forgot which magazine I was in. I had to find it in the BIOS of the motherboard, but because the motherboard is too old, I can't find an option about IRQ.

Then I went back to WinXP. When I started the desktop, I suddenly saw an icon that I had never seen before in the toolbar in the lower right corner! Open it and see that it is a newly added detection built-in. The cat's working status program, one of which is "comport" is used to select the cat's working port, there are four options, is "COM1, COM3, COM2 and COM4", according to the default settings, the cat's interface is in “COM3” Yes! That article seems to be talking about the motherboard. Although COM1 and COM3 have two different I/O addresses, their IRQs are the same! In other words, COM1/COM3, COM2/COM4 are two pairs of serial ports. The same interrupt (IRQ) is used to control two different I/O addresses, so when the devices connected to COM1 and COM3 (or COM2 and COM4) work simultaneously, there will be conflicts on the IRQ address, resulting in One device is not working properly. I suddenly realized that the original built-in cat took up the IRQ of the mouse when it was used! The mouse does not "dead"; it is strange! I quickly changed the working port of the kitten to COM4, ​​so that the cat and mouse use different IRQ addresses. Then restarted, dialed the Internet again, the fault finally disappeared, the mouse and the cat cooperated very well on the Internet, and the cat no longer "bites" the mouse.

There is a common reason for the conflict between the modem and the mouse. Therefore, if you encounter this problem, don't panic, look at the solution and get it step by step.