WheelK : at last, use that mouse =wheel= in DOS ! (Announce)

> In addition to doing that, you can also check that it really works> (actually simulate a keystroke and see if it appears in the keyboard buffer> or not).

Yeah, but... I'm not sure it is 100% correct, depending on the BIOS int 16/05 which might "STI" before returning, thereby allowing other processes to consume the injected key before we had a chance to check it reached the buffer. Possibly not a serious objection in practce, but needs more analysis and, frankly, the tests above should leave very few false positives while being perfectly safe.

Actually; ICBW but I think the only outliers must be very early revisions of the orignal, IBM brand, PC-AT. For those, identification of the BIOS by date and/or examination of the feature byte (int 15/C0, which is safe to call) and correlating with Ralf's interrupt list would be a good determination - and overkill too... such machines must rest in a tehnological museum.

...

> My USBKEYB program includes an external API for simulating keystrokes with> the /K method. You can check for that API, and if it exists, use it to> simulate the keystrokes via scan codes so you don't have to do it yourself.> Indeed it is a can of worms, but a necessary one to open if there is any> hope of creating a usable DOS USB keyboard driver.

> Also as an FYI, the next version of USBMOUSE will include a similar API to> simulate/virtualize mouse movements and button presses.