Return to site

Ehome infrared receiver windows 10

broken image

The motherboard is that which is shipped in a ASUS V2-P5G33 system (a great inexpensive little system, btw, too bad its not manufactured anymore) which is basically a stripped-down ASUS P5K-VM motherboard. So here's the how my setup differs from the standard:ġ.

broken image

So I was hoping the resident gurus might be able to help set this system straight. So I'm beginning to suspect it might be some non-standard stuff going on with the motherboard. Microsoft keeps closing the bugs I file as 'cannot reproduce' and The Google isn't helping much.

broken image

The funny thing is that it seems I'm alone in reporting this problem. Device manager shows a bang on the 'Microsoft eHome Infrared Receiver', it has a code 43 - 'Device stopped working because it reported a problem.' In win7 beta1 I just disabled sleep and ran the box 7x24 but that's lame - I've been able to get S3 working well on my systems since back in the XPMCE days. Whenever the system resumes from S3 sleep, the remote control doesn't work. It was running Vista OK but like most people I freaking hate Vista so I switched to the Win7 beta1 and then clean installed Win7 RC.Įverything works for the most part, except for the IR remote control.

I've put together a system to be the family HTPC.