I see. Indeed, it would be best to have interrupt chaining eventually, in case someone wants to use an original DOS mouse driver. Well, good luck then :) [edit] Unfortunately, latest drivers and game patches cannot be downloaded any more, despite the web page still exists: http://www.mindflux.com.au …

CALLBACK_Setup is probably not meant to be used for chaining interrupt handlers - and I seriously doubt any fork does something like this, as that would bring performance penalty. Unless you are developing a mouse driver API extension, adding any special/custom function to INT33 is probably not the …

Of course, feel free to take the modified serialmouse.* back into DOSBox-X, it’s open source :) Just keep in mind that the interface to the rest of the mouse subsystem has changed - bitfield for buttons is now different (for sake of uniformity with the rest of the mouse emulation), there is no Mouse …

Thanks for the DDK hint, indeed I might find a clue here. > Are you doing I/O access directly or are you doing the I/O out as IN/OUT instructions where Windows 3.1 can see it? I don’t understand - I have extended port 0x60 and 0x64 emulation. I have already stolen your serial mouse emulation, and …

- PS/2 AUX port emulation. This enables DOS programs and OSes to work that don't use INT 33h and communicate directly with the PS/2 mouse connected to the keyboard controllers "AUX" port. This code is wired in so that INT 33h emulation is enabled by default, but shut down the instant the "reset" …