Can you confirm whether or not a driver rollback from within device manager
will fix the problem? There's a few threads going on about this issue in
other groups.
--
----
Crosspost, do not multipost
http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question
http://support.microsoft.com/kb/555375
Help Us Help You
http://dts-l.net/goodpost.htm
"Al G" <Al
> wrote in message
news:0D7830F7-EB00-4DDF-BFB8-...
> You are not alone.
> All computers I am responsible for with PS2 mice have failed after
> installing the IdeaCom driver.
>
> Our fix has been to remove the driver (in XP- \windows\system32\drivers)
> then uninstall it from HID in device manager.
>
> A reboot will cause the OS to reload the original driver.
>
> Note that you must remove the driver before the reboot, or the bad driver
> will reload and you will be right back to where you started.
>
> FYI - We had to use a USB based mouse to get around until this was done.
> USB
> mice still work after the update.
>
> Also, this is the fix that has worked for us (about 18 computers) and is
> not
> official. We are still waiting to see what Microsoft is going to do about
> it. Until then we have issued an alert to our customers NOT do any
> updates.
>
> ALG
>
> "rajkiranpro" wrote:
>
>> I noticed my mouse fail suddenly after installing windows updates
>>
>> Security Update for Windows Vista (KB958687)
>> Windows Malicious Software Removal Tool - January 2009 (KB890830)
>> Update for Windows Mail Junk E-mail Filter [January 2009] (KB905866)
>> IdeaCom Technology Inc. - Input - IdeaCom HID Touch Screen (PS/2)
>> (Recommended)
>>
>> After restarting the system after the updates were installed my mouse
>> didn't
>> work at the login screen, I had to use my keyboard to login.
>> and on the desktop there was an dock appearing on the left of my screen
>> with a pen symbol. it was like ink trainer for tablet pc (I don remember
>> the
>> exact process name).
>> and I had to restore my system back to previous restore point to get my
>> mouse working again.
>>
>> is there any workaround for this problem without using system restore.
>>