Setpoint killed my keyboard?

njj1046

njj1046

njj1046

Associate
Joined
13 Nov 2007
Posts
369
Location
UK
Long story short as I can..

Bought a Logitech G5 to replace my MX510
Removed MX510 and drivers, plugged in G5 and installed setpoint.
The G5 didn't like my black icemat one bit, so I uninstalled setpoint, took out the G5 and put the MX510 back in for the time being.

After this, windows would occasionaly make the default noise for something connecting/disconnecting, the led's on my saitek eclipse would go out. The keyboard and mouse would be unresponsive for a few seconds; Then I'd get the disconnect/connect sound again and my keyboard and mouse would work.

I removed all reference to the setpoint drivers and re-installed my USB controller. All seemed well for a while until this morning.

Computer turns on, led's light up on the saitek keyboard, BIOS says no keyboard was detected. Also, the led's on the saitek would stay lit after the pc was turned off, which it never did before.

I'm now using an old logitech USB keyboard in the same USB port as the saitek was plugged into with no problems.

What do you reckon? This is a strange one for me :confused:
 
what version of setpoint were you using, got a black icemat and my g5 is fine.

maybe try a system restore to the point prior to the mouse/setpoint install.
 
I was using setpoint v4.40.

I'm just curious as to how much of a coinsidence it was that after installing and uninstalling the setpoint software, I had USB disconnects/reconnects and now the saitek keyboard is not working at all.

Was it just coinsidence that the keyboard gave up the ghost after this ordeal, or did the setpoint software cause the disconnects/reconnects and cause the keyboard to fail :confused:
 
would think it is coincidence, different products, could possibly understand it if it affected the logitech keyboard but not the saitek :confused:
 
the connect/disconnect sound makes me think it's a hardware problem with the saitek keyboard.
probably a cable/connector at a guess.

From what you've said it's even possible the keyboard isn't quite plugged in 100%.
 
Update...

I plugged the saitek in a front usb port earlier and windows detected it (remember, the BIOS wouldn't detect it at all previously). I then tried it in the usb port on the m/b that it was in originally and it detected it there too. In my mind that rules out that it's a problem with any of the usb ports on the m/b.

After 10 minutes windows made the disconnect/reconnect sound continuously for about 10 seconds and came up with the error "a usb device has malfunctioned".

I'm now back using the logitech keyboard. If this works ok I can only assume that there is something physically wrong with the saitek. I really hope this is the case as otherwise it means something more sinister is wrong.

It really is strange that this started happening after I installed/uninstalled a new mouse and the setpoint drivers.

Anyway, thanks for the help peeps. Hopefully the logitech keyboard will work ok for the next few days. If it doesn't, I probably won't be able to reply back here due to an accident involving a hammer and various keyboards/mice :)
 
You must log in or register to reply here.
Back
Top Bottom