Not being certain if the problem is hardware or software, I chose this board to ask my question. I have a Logitech TrackMan Wheel mouse, which sometimes has given me some problems where it wasn't recogtnized on boot, or on rare occassions the cursor would become unresponsive, until I pulled the plug and replugged it again. That has always solved the problem...until the next time.
However, this seems to have taken a turn for the worse, because when the cursor froze a bit ago, and I did as usual, it did not seem to notice when I unplugged or replugged the mouse back in, and the LED remained unlit afterward. I moved the mouse to my other computer, and it worked fine, so I plugged the mouse back into the first machine, but in the front I/O port instead, and Windows saw it right off.
This would seem to indicate a problem with either my USB hub or the rear I/O port, except that there is no problem with the other USB devices plugged into the hub. I also noticed that the hub LED for the mouse doesn't light during the BIOS run, only after Windows start to boot. Shouldn't it remain lit either way? If there is a hardware problem, it would seem that the OS would never see it, but I believe that if I reboot, it will function as before. I would really like to get a grip on this, if someone has a handle?
However, this seems to have taken a turn for the worse, because when the cursor froze a bit ago, and I did as usual, it did not seem to notice when I unplugged or replugged the mouse back in, and the LED remained unlit afterward. I moved the mouse to my other computer, and it worked fine, so I plugged the mouse back into the first machine, but in the front I/O port instead, and Windows saw it right off.
This would seem to indicate a problem with either my USB hub or the rear I/O port, except that there is no problem with the other USB devices plugged into the hub. I also noticed that the hub LED for the mouse doesn't light during the BIOS run, only after Windows start to boot. Shouldn't it remain lit either way? If there is a hardware problem, it would seem that the OS would never see it, but I believe that if I reboot, it will function as before. I would really like to get a grip on this, if someone has a handle?
My Computer
- Computer Manufacturer/Model Number
- DIY
- OS
- W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
- CPU
- Phenom II 1090T w/Noctua NH-D14 /**4400+ X2 w/CM Hyper TX 3
- Motherboard
- ASRock 890FX Deluxe 4/**A8N-SLI
- Memory
- 2 x 2GB Patriot PGS34g1600LLKA/**4x1GB Corsair VS
- Graphics Card(s)
- EVGA GTX460 SC/**EVGA 8800GTS
- Sound Card
- Asus Xonar D2X/**Xonar D1
- Monitor(s) Displays
- Acer X233H, Dell E152FPc /**LG M237-WD
- Screen Resolution
- 1920x1080 & 1024x768/**1980x1080
- Hard Drives
- WDC 2TB, 1.5TB, 1TB, 500GB,Seagate 500GB , Maxtor 80GB /**500GB Seagate & WDC 1TB Black
- PSU
- CM RS600 w/ APC BX1000G/**Antec 500 TP w/ APC BX1000
- Case
- HAF922/**Antec 1040IIB
- Cooling
- 3x200mm, 1x140 and 1x120mm/**5x80mm fans
- Keyboard
- Logitech Media USB/**Saitek Eclipse
- Mouse
- Cordless Trackman Wheel/**Ditto
- Internet Speed
- 3.3Mbps
- Other Info
- SB 560 5.1 w/ Sennheiser RS140/**Creative T20 speakers, Dvico FusionHDTV7 Gold RT, Cisco E3000, HP 5510V AIO, Linksys E3000, Belkin F5U237 hub and **F5D8055 adapter
(** = 2nd rig)
