Vmware player disable mouse integration11/8/2023 ![]() ![]() You'll note that on these, the mouse actually works even inside a Win31 windowed DOS box. However at least many of the text mode utilities that came with DOS itself do work with absolute positioning. I think WINOS2 does something similar.Īlso, yes, most DOS programs/games I know use relative data from the DOS mouse driver, as learnt from the DOSbox days :(. ![]() (Likewise they are also broadcast inside the DOS VMs so that the programs/mouse drivers there would know when to do their stuff). the video driver is supposed to catch them to do its stuff. These were broadcast when Windows enters/leaves fullscreen and e.g. I think an approach that does not require an extra VxD is to hook int 2Fh and look out for 4001/4002 calls. Unfortunately, I found that the VirtualBox BIOS does not forward the contents of the Z byte/wheel to the mouse handler, even when I set it to 4-byte packets, so I'd need to think of something else.įor the fullscreen DOS box issue as far as I can see it's exactly the same issue as you describe. Sorry, are these issues related to the wheel "hack", or as you mention elsewhere because the driver is clobbering the high word of the 32-bit registers ? In any case, I remember there where wheel mice for 3.x which included drivers, so it may be a matter of scavenging for one of these and see what the driver did. WRT your comment about DOS boxes, I think it'd need a VMD to flip it back to normal PS/2 protocol (since VMware at least turns off relative positioning see #3 ) or a implementation (cool, but a lot of DOS software may be hardcoded to expect PS/2 or relative input at minimum see #15 ). I'm tempted to hide it behind an INI option (and hey, maybe also support a control panel from the driver to control that kind of thing - that's definitely possible per the DDK). Maybe one day I'll rewrite it.Īs for wheel support: it does work, but there might be problems like in #22 and #23. Plus I'm more familiar with the Microsoft toolchain, and AFAIK most drivers were based on (and MS intended it to be) DDK samples. Oh, that's very nice! The VirtualBox interface looked a lot more complex with PCI in play.Īs for why this one is the way it is: I was considering C, but I wasn't familiar with x86 or the driver space, so basing my driver off the existing one seemed easier than figuring out the very scantly documented Windows drivers in C. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |