First post, by Bumrusher89
I was just thinking about on how I am going to get a mouse to work on Windows 3.1 DOS sessions without trying to load a mouse driver on Autoexec.bat. Well making a startup PIF for cutemouse is not going to help nor for mouse.com... Reasons for I am looking for away to load a mouse from within Windows 3.1 without using Autoexec.bat is that I am trying to avoid certain DOS games from getting a system integrity error... Because even if you don't have a mouse loaded on Autoexec.bat. You still have a cursor you are moving with the mouse on Windows 3.1. But not on DOS session VMs for some strange reason, because Virtual 86 mode has a way for DOS mosue support. I mean if you are using the mouse on Windows 3.1 without having mouse.com already on autoexec.bat, why isn't it being used on DOS sessions when in Windows 3.1? This doesn't make any sense to me... The mouse works when on Windows 3.1 with out having mouse.com or cutemouse loaded on Autoexec.bat and I know that 386 enhanced mode has virtual mouse support through V86 mode, but it does not on DOS sessions? There's something wrong of what I am doing here.
And I don't even know why the virtual mouse drivers on virtual 86 mode aren't making my mouse work on DOS sessions. If you know the problem why virtual 86 mode is not using the virtual mouse emulation, please let me know what I was doing wrong.