You may have a conflict with another device, like the video card or an NIC card. I have seen NIC cards conflict with a video card, which in turn caused conflicts with other devices, like a USB mouse or a USB joystick. This might not even affect the display, or cause a BSOD, but simply render the device inactive during the boot until reconnected after the GUI is loaded. These kind of conflicts are not always visible from the Device Manager, but may show up as a series of unusual and/or consistent errors in the Event Viewer System log, which is located under Administrative Tools in the Control Panel. If one device in particular seems to be coming up with errors, uninstall it from the Device Manager, and physically remove it from the system. If this corrects the problem with the mouse, you've found the source of the problem. Fixing this might be as simple as shifting the cards around in the PCI slots, and updating the drivers for all the devices. Or if the video card is a GeForce4 card ... installing an older card. There have been some conflicts with GF4 cards and the BIOS versions on various mainboards (especially with the Intel 850 chipset), which causes some problems with ACPI power management and IRQ sharing.
If you have two devices in one hub (2 USB ports), you might consider adding an external powered hub for the mouse. The power demands for a passive USB hub shouldn't exceed 500mA, which is the basically the power drain for the combination of one low-powered device (i.e. a mouse) and a one high-powered device (a scanner). However, on many VIA mainboards, the hub can really only support one device per hub, even if the power limitations have not been exceeded.
You might also try disabling USB error detection. This is found under the Properties for the USN Universal Host Controllers and the Advanced tab. Select the check box for "Don't tell me about USB errors".
You may find the solution would be in updating the chipset drivers for the mainboard.
Finally, you should check to see if USB support is enabled in the BIOS, especially for legacy devices.
I wouldn't suggest adding an additional PCI card, even one that is USB 2.0, until you verify that there is no conflict with another device. If a conflict exists, forcing the system to allocate or share another IRQ address is not necessarily the best solution. I'm not saying that it won't work ... anything is possible. But that would not be my first choice for troubleshooting the issue.
Toejam31
<font color=red>First Rig:</font color=red> <A HREF="
http://www.anandtech.com/mysystemrig.html?rigid=17935" target="_new"><font color=green>Toejam31's Devastating Dalek Destroyer</font color=green></A>
<font color=red>Second Rig:</font color=red> <A HREF="
http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new"><font color=green>Toey's Dynamite DDR Duron</font color=green></A>
__________________________________________________________
<font color=purple>"Some push the envelope. Some just lick it. And some can't find the flap."</font color=purple>