R.Wieser wrote:
Hello All,

I've been given a "RC6 MCE based RemoteContol" (home entertainment center
related), and would like to disable its build-in handling, so that I can let
some other program (like EventGost) do the work (and not get a mix-and-mash
result).

A suggestion I found was to replace a conversion table stored in the
registry with a dummy one. But that would make switching back much harder (I
know, backups and all that).

My question is: Isn't there a "do not work" registry-key I could introduce
(easy to switch on, easy to switch off/remove) ? I'm even giving extra
points for a method (preferrably by calling some API) that will work without
having to reboot the 'puter. :-)

Regards,
Rudy Wieser

I can simply replace the conversion table thats stored in the registry with

I'm not sure I understand what you're trying to do.

If you "disable" a device in Device Manager (devmgmt.msc),
then another actual device driver would be needed to
access that piece of hardware. So something has to be there.
The "disable" in Device Manager which is available on a per-item
basis, is a form of control.

Normally, a piece of software needed to modify an input stream,
would use a "filter driver" approach. It allows the basic driver
to continue working, and a "shim" (UpperFilter or LowerFilter)
is install. If the driver writer wants the original consumer to
be cut off, I presume the filter driver can simply not pass any events
onward to the rest of that particular driver stack. The
position of the filter (Upper or Lower), determines who
gets what part of the information stream.

An example of a filter driver, is how Track Pads work.
Initially, they declare themselves in Plug and Play,
as a "HID Device". A basic level of functionality is
present. However, if you want "virtual buttons" on the
trackpad surface, a separate (Synaptic or similar brand)
filter driver is needed. That driver sits as a shim in
that particular HID driver stack, intercepts coordinates
and events, and provides a richer set of functions. That
filter driver still allows lots of the information stream
to pass through the filter, so that the cursor moves around
on your computer screen, as you move your finger over the
trackpad surface.

Multiple shims can be installed. For example, if you install
two Virtual Machine hosting softwares, each of those can
install a filter driver in the NIC stack.

*******

The EventGhost developer should be doing the grunt work
for you. Attacking the Registry with an ice pick, seems
so 90's.

*******

Maybe some idea here will help ?

http://www.eventghost.org/mediawiki/...for_Windows_XP

Paul