EventGhost

This is the support thread for X10 remotes, where you can post your questions specific to this plugin.

Some X10 remotes are:

• ATI Remote Wonder
• ATI Remote Wonder PLUS
• SnapStream Firefly
• NVIDIA Personal Cinema Remote
• Marmitek PC Control
• Pearl Q-Sonic Master Remote 6in1
• Niveus PC Remote Control
• Medion RF Remote Control
• Packard Bell RF MCE Remote Control OR32E

and a lot more.

One problem with the X10 remotes are the huge amount of different drivers that are available. There are mostly three kind of driver packages:

1. A bare hardware driver for the receiver
   This is what you get, if you plug the receiver into the USB port and let Windows Update install the driver for it. But even though the device-manager is now happy, that he has a driver for the hardware, this driver alone will give you no events inside EventGhost. The driver normally shows up in the device-manager as "X10 USB Wireless Transceiver (ACPI-compliant)".
2. Packages with X10nets.exe service
   These drivers are so far the best option for EventGhost. They install the hardware driver for the USB receiver and an 'X10nets.exe' service that you can see inside the task-manager. EventGhost can now contact this service to get notified of remote button presses and the service will do nothing else additionally.
3. The HID drivers
   Many manufacturers deliver a driver that installs the remote as a HID device. This way the remote actually becomes a kind of keyboard and emulates keypresses without any additional program. What sounds nice so far, has a huge drawback. Third-party programs like EventGhost aren't able to stop these remotes from sending keypresses, so the keypress will arrive additionally to any action EventGhost does in reaction of a remote button press. To get rid of this behaviour I have written something in the documentation: http://www.eventghost.org/docs/x10
   These packages normally also install the X10nets.exe service.
   
   But also see the next post of a possible new way to handle these.

So I experimented a little with these HID drivers and noticed that they install an additional service called "X10Hid.sys". But this service doesn't show up in the services control panel and also has not entry in the task-manager. These kind of services are "device driver services" and cannot be stopped in a running system. Instead you have to disable them (for example through the registry) and restart the computer.

What I want to do now is to find out, if these HID driver packages are a good option for EventGhost users. The advantage of these HID driver packages is, that they are mostly newer and better supported by the manufacturers. One packages that looks especially fine is the driver for the ATi-Remote-Wonder(-Plus) as it includes drivers for both 32bit-Windows and 64bit-Windows.

You can get this driver here: http://support.amd.com/us/gpudownload/P ... sta64.aspx
Don't get anxious, because it say "Vista (64 bit)". This driver should work on XP and 32bit versions also.

After you have installed this driver package, you should find an ÔÇ£X10 Hid DeviceÔÇØ in the device-manager, as it's explained here: http://www.eventghost.org/docs/x10

So try to remove it, but don't install another driver afterwards. Then test briefly, if everything works as it should.

There is an easier way to disable this ÔÇ£X10 Hid DeviceÔÇØ through the registry editor. Just open up:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\X10Hid
and set the value of the "Start" key to 4 and reboot. If this works so far, we can later automate this registry manipulation inside the plugin.

No mention of the x10 MouseRemote...
Of course this is a legacy serial device, but a great remote, with one of the best ranges I've seen. 100-150'.

I've used this with a serial to USB converter using an FTDI chip, successfully.
http://www.usbgear.com/XC-232-C.html

How are the IDs generated? Randomly on plugging in the USB connector? They seem to change from time to time (and I sometimes reorganize the wires behind my PC). Currently I have to enable one ID for the keys in the lower part of my remote control and another ID for controlling the mouse, whereas until recently I could use one ID for the whole remote control. I use a Q-Sonic Master Remote from Pearl.

I had a bug with X10 that I was able to fix with a small change in the plugin.

http://www.eventghost.org/forum/viewtop ... 947#p10947

Hi. I have a problem with a Medion OR24V remote controller (Win 7 32). I need to press every button twice to work (event ghoust detects button press after second time).

Are you using the x10 remote drivers for EventGhost?

For 32 bit they are located here
http://eventghost.net/downloads/x10drivers_x86.exe

I've been doing research and tried lots of things, but I can't get it to work for some reason! I have the newest Eventghost and Kodi working perfectly on Windows 7 and 8.1, but on my Win 10 machine, the same setup doesn't work. I can see the ATI Remote Wonder Driver in the list of devices in the Device Manager (same install, same driver as on 8.1). I have EventGhost installed and running with the same settings as 8.1 (I saved them on 8.1 and loaded them in EG on Win 10). I even manually switched the generic X10 driver plugin in EG to Remote Wonder via the configuration options.

No matter what I've tried, I can't get any button presses to register. Normally when I press a button on a different system, the keys would show up on the left panel of EG making it clear it's seeing the activity. No dice on Win 10.

Any ideas? Am I missing some special configuration or option?

ok so here is the skinny on this. The drivers made for the remote are ancient. and they are not being updated. Therefore they are not signed for windows 10, the ones that we provide for x10 are also not signed.

Microsoft was kind enough to give everyone a gift when they released build 1607, they decided they were no longer going to allow unsigned drivers to be installed. They also figured to help us all out with it they would provide no errors. and show the device installed and is functioning like it should be. with no indication of a driver malfunction.

If you follow the link below you will be able to get the drivers to install properly. This holds true for any and all drivers that are not specifically signed for windows 10. windows 7, 8, 8.1, and 10 all share (for the most part) the same driver framework. so drivers made for Windows 7 almost always will work in 10, drivers specifically made for 10 may or may not work with previous versions of windows, it's a crap shoot.

viewtopic.php?p=45688#p45688