At 01:54 PM 11/18/2011, Tomer Godinger wrote: >The key emulation was done using INT 16, like I mentioned before, >and it worked - the program really did read the emulated keystroke. > >Then I changed the program so that it installs a small TSR that >emulates a keyboard event every 5 seconds or so, alternating between >emulating a key-down event and a key-up event. >When I tested it again with 'a' and in the DOS console, I saw, as >expected, 'a' characters being typed. > >So I changed the key from being 'a' to being the right arrow key. >Again, it worked in the console. >However, when I started a game (One Must Fall 2097) to test it >there, it did not receive the key events my TSR emulated. > >After that, I switched to using the outportb() function - and it worked. >The game moved the characters as if I was pressing the right arrow >key for a few seconds, then releasing it for a while. >However, when I started two other games (Commander Keen 1 and Golden >Axe), they did not receive the key events.
In particular for games, I would not expect that they necessarily use INT 16h functions to read the keyboard, specially when they come with their own mapping of the keys. You might have to get a level lower probably, messing with intercepting/simulating INT 09h to work directly on the scan codes instead and then probably make sure that you do not have any keyboard driver like KEYB installed either... Ralf ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
