Messed UP IR Remote control

Hi,

I have a Windows XP MCE setup with the RC6 remote control and the OVU4003/00
IR trsansceiver. Until this morning this was working perfectly.

However I then got overexuberant in installing optional updates via Windows
Update - based on my obviously flawed logic that even if I do not actually
need a particular update, installing it anyway is unlikely to cause any
harm.

The unfortunate result was that now certain keys on the remote no longer
work - most annoyingly the "stop" and "back" keys. Now, I thought I was
being sensible and creating a restore point before doing any of these
updates - that way I could roll back any changes. However something went
wrong here as the restore point does not exist (I guess I should have
verified that it was correctly created in the first place!).

Looking at the device manager, the problem may be related to the fact that I
now have a driver for "Microsoft eHome Infrared Transceiver" under "Human
Interface Devices". I don't think this used to be there (I think there are
also extra instances of "HID-compliant consumer control device" and
"HID-compliant device").

There is no option to disable the "Microsoft eHome Infrared Transceiver"
driver. However uninstalling it does make the device manger list of "Human
Interface Devices" look identical to the previous working configuration.
However at this point the IR remote does not work at all. Either re-booting
or disconnecting and re-connecting the USB IR transceiver simply results in
the "Microsoft eHome Infrared Transceiver" driver being re-installed. And we
are back to the Remote partially working but not all codes.

Anyone got any ideas. Apologies for my extremely non-scientific methodology!

Regards,
John



.

Relevant Pages

  • Re: Messed UP IR Remote control [UK] - Update
    ... > I have a Windows XP MCE setup with the RC6 remote control and the ... > doing any of these updates - that way I could roll back any changes. ... > that I now have a driver for "Microsoft eHome Infrared Transceiver" ...
    (microsoft.public.windows.mediacenter)
  • Re: Group Policy - Pushing out Software
    ... I know the way we access users machines using Remote Desktop ... remotely, log on as them and do updates, without ... life easy for 2 administrators keeping 80 users machines updated. ... packages to specific profiles only. ...
    (microsoft.public.windows.server.active_directory)
  • RE: Messed UP IR Remote control
    ... > I have a Windows XP MCE setup with the RC6 remote control and the OVU4003/00 ... > However I then got overexuberant in installing optional updates via Windows ... > Interface Devices" look identical to the previous working configuration. ...
    (microsoft.public.windows.mediacenter)
  • Re: automatic update on Mac OS X
    ... Since VNC will not applay updates, and is just for remote controlling the ... Sebastian ...
    (Security-Basics)
  • TSLSA-2002-0025 - rsync
    ... This update fixes the signed/unsigned remote exploit bug in rsync. ... All TSL updates are available from ... These packages have been available for public testing for some time. ...
    (Bugtraq)