The Input tools
These tools deliver keys, mouse buttons and pointer moves to the program running inside DOS. Everything goes in inside the emulated machine: no window comes to the front and your own pointer never moves (Input and the screen).
How input gets into the program
A small helper, SCRY.COM, stays resident inside DOS and carries out each key or mouse command the server sends it over the emulated COM1 port. start with program loads the helper by itself; a conf that starts the program from its own [autoexec] has to run the helper first.
Sent to a machine stopped at the debugger, an input runs it one frame at a time until the helper has taken every command, then leaves it stopped again. A frame here ends at the vertical retrace.
An input that was sent is not one the program took
Without expect a reply says what was sent, not that the program reacted: a dialog can swallow a key that went in correctly. Give expect, a pattern for the line the program writes to its own log (port 0xE9) when it reacts, and the reply says whether that line came.
The summary of every input says which case it is: "sent, reaction not checked", "reaction seen", "no reaction seen (TIMEOUT)" or "reaction could not be checked".
The tools
send_keysSend keystrokes to the DOS program, and check in its log that it reacted to them.send_mouseMove the DOS program's mouse pointer, press its buttons or drag, and read back where the pointer ended.