[Elfman]

Nevermind, got it to work. Thanks.

Mind posting how? I just picked this unit up, and can't get any response from the internal IR receiver, which is enabled in bios. I (think I) even managed to manually get the drivers installed, as I now have something that says "microsoft ehome" in driver manager which installed itself after I manually installed the ITECIR infrared receiver driver to the HID device that is located on PCI standard ISA bridge... But it still doesn't work, like at all. The USB extension works in that it responds to key presses, but then infinitely loops whatever I just hit. No combination of any of the various driver options has gotten the internal receiver working for me. I'm about to just cave and buy a separate remote here...

EDIT: And through the magic of, "as soon as you post something asking for help it'll just suddenly work," as soon as I posted this it just suddenly worked.

Would love to know what you did. I am experiencing the exact same thing. All drivers installed, no front receiver, dongle responds but loops through commands at a rapid pace. Been banging my head against this for a month now and still can't get it to work. Just wanting to know if I can try anything before a re-install is attempted.

*EDIT*

Okay, I think I got it figured out. I ended up rebuilding the box. Didn't take long. But as soon as I had a desktop, I installed the CIR utility from the disk. That got my front panel IR window working properly. However, when I plugged in the dongle, I still got looping commands until I unplugged it. After some digging (and cussing), I decided to simply look at the device as Windows sees it. Went to Control Panel > Hardware and Sound > Devices and Printers. I noticed that I had a "MCE USB IR Receiver - Spinel plus" installed. I thought that this was weird since it had the icon of a full blown keyboard on it. Ended up right-clicking it and selecting "Keyboard Settings". From there, I adjusted the first two options available. I set 'Repeat Delay' to long and 'Repeat Rate' to slow. That seemed to take care of it. I can only guess that when the IR receiver got a signal, it had to interpret the command similar to a keyboard stroke and because the rate was set higher, it was spamming the system and causing the loop. Would have been a nice piece of knowledge earlier. Oh well. Things appear to be working well now.

*Edit #2*

Sheesh. I spoke too soon. Problem still exists. Guess I didn't test it thoroughly enough.