![]() ![]() This is why, when I wrote the mouse pointer integration support for Windows 3.1, I wrote the PS/2 mouse emulation to send mouse events with NO motion (dx=0 and dy=0, only the button state) unless mouse capture is active. Code that requires reading relative motion should require the user to capture the mouse. Perhaps it would be better if the INT 33h mouse integration were to only report absolute mouse position, and not report relative motion, if your synced=true code is working. Heres what Ive tried so far: - Tried with in autoexec.bat - Tried with mouse.sys in config. Its a Mitsumi two-button serial mouse on COM1. I also noticed that relative motion with DOOM works, but it's a pain to have to move the cursor back and forth manually to try and turn. An old 386SX/40 with DOS 6.22 and Windows 3.0, I cant get the mouse to work on Windows, even tough it works fine on DOS programs and games. It's possible that the mouse driver wasn't enabled, or that it's set to the wrong choice, and is ignoring the mouse altogether. I found one demoscene "invite" that uses the mouse but reads only relative motion, which caused the cursor to not match the host. You might want to try to running setup.exe in dosbox from the directory that win 3.1 is installed in and check on the mouse option. I also noticed a problem with DOS games that read relative mouse motion instead of absolute. VMware mouse driver for Windows 3.1, the mouse will be seamlessly integrated with the host system and can enter/exit the DOSBox-X window without having to be captured or. DOSBox doesn’t have a restart option (I don’t think) so you just need to quit. So it’s just asking you to restart DOSBox. The message is coming from the installer and, from its point of view, DOSBox is the whole computer. Then you and reopen DOSBox and start Windows 3.1 again. ![]() Host cursor is visible while Windows 3.1 is using the DOSBox Integration Device (should be hidden as long as Windows within is reading the host mouse position). VMware mouse support for seamless mouse integration in Windows 3.1 DOSBox-X now implements basic support for the VMware mouse protocol so that when used together with e.g. Just exit Windows 3.1 inside of DOSBox, then exit DOSBox. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |