diaapi.blogg.se

1. EHOME INFRARED RECEIVER (USBCIR) DRIVER POWER FAULT DRIVERS
2. EHOME INFRARED RECEIVER (USBCIR) DRIVER POWER FAULT CODE

Hmm, poking around in the Win7 x86 RC set up in a VM on my dev box, the task scheduler's create task / new trigger- View image here: -n event functionality looks promising. And DevCon looks to be a great tool to have around in general. DevCon looks like a good option if nothing else works out. I'm playing around with DevCon (on my main development box). Thanks, Bob- your post is HUGELY helpful. If I disable and enable the device in Win7 it starts working again. The eHome IR receiver works (worked) in Vista 圆4 SP1 under the S3 sleep scenario described above on exactly the same hardware.Ģ.

EHOME INFRARED RECEIVER (USBCIR) DRIVER POWER FAULT DRIVERS

Pretty much default settings.Īll Win-7 drivers except for ATI video, currently running ATI Catalyst 9.5ġ. Microsoft 'XPMCE classic' eHome Infrared Receiver USB IR remote control Here's the details of the hardware & software:ĪSUS P5G33 motherboard running the P5K-VM v1001 BIOSĢx 1TB WD Caviar Green harddrives (#1 for OS & apps, #2 for media storage) All the motherboard USB & keyboard device wake-up jumpers are set to the '+5VSB' setting, which keeps power to the ports when the motherboard goes to sleep so external devices (like the remote control) can wake the system. It works great although I don't overclock or do anything silly other than use the more advanced fan control the new BIOS provides.Ģ. Since I was there I went ahead and flashed (BIOS rollback hacked) to the fully-functional P5K-VM v1001 BIOS instead of the severely-limited P5G33 BIOS. I had problems getting it to POST with the Wolfdale E8400 CPU until I borrowed a celeron and upgraded the BIOS. 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:ġ. 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. The funny thing is that it seems I'm alone in reporting this problem.

EHOME INFRARED RECEIVER (USBCIR) DRIVER POWER FAULT CODE

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.