Re: "Fake" Keyboard or Mouse driver by AntonBassov
AntonBassov
Thu Mar 08 16:12:08 CST 2007
> If I connect a new keyboard or mouse on host, every time I press a key on
> it, the Virtual machine doesn't matter about USB, PS/2, bluetooth or other
> connection type; it will show the key that was pressed; regarding any type
> of driver ecc ecc....
This is because, from the host system's perspective, virtual machine is just
an application that runs on the host system. Apparently, it just redirects
keystrokes
to the virtual machine simply by means of Windows messages, so that the
guest OS has no clue where it physically comes from - there is no need for a
driver here. In any case, even if it does it from the kernel mode,
communication between the host and guest systems is done via some proprietary
mechanism known only to VM
designers, so you are out of luck.
Certainly, you can inject keystrokes and mouse events into the host system
input queue from the filter driver (as well as simply by SendInput()), but
only VM designers know how all that activity will be interpretated by the
VM.....
Anton Bassov
"The Junk Yard Dog" wrote:
> > Anything that you have simulated on a host machine gets processed by the
> > host, rather than guest machine - if you want to simulate events on the
> > guest
> > machine,
> > you have to install your simulation software to it. If the guest OS is
> > Linux, then you have to get a Linux driver for it, so that you are asking
> > a
> > question in the wrong NG...
>
>
> The driver will be installed on host machine, not on the virtual.
> If I connect a new keyboard or mouse on host, every time I press a key on
> it, the Virtual machine doesn't matter about USB, PS/2, bluetooth or other
> connection type; it will show the key that was pressed; regarding any type
> of driver ecc ecc....
>
> ...oO Please cut "-SOME TREES-" for reply Oo.
>
>
>