Fix compatibility problems with VBADOS (VBMOUSE.EXE) mouse driver

[FeralChild64]

• fixed PS/2 packet data loss problems when BIOS was receiving the next packet before the previous one was fully retrieved (due to this problem VBMOUSE.EXE was completely broken if emulated PS/2 mouse supported wheel)
• prevented unnecessary dummy mouse events in VMware mouse protocol
• added support for PS/2 mouse packet size 1 to the BIOS - VBADOS seems to prefer it
• silenced warning in our internal DOS driver, which was a result of VBADOS checking if it is already installed

Driver link: https://git.javispedro.com/cgit/vbados.git/about/ (changes are related to VBMOUSE.EXE DOS driver, not to the Windows driver)

[johnnovak]

Just one minor comment @FeralChild64 , nice work as always 👍🏻

[Torinde]

Tested that - it worked for me. Thanks!

Can it be made even more seamless? #3290

[Grounded0]

Hint for anyone who wants to use this but doesn't want to deal with compatibility problems that might occur by keeping this loaded outside of Windows 3.1x:

$ cat WIN.BAT
config -set cputype=pentium_slow
c:\vbados\vbmouse.exe
win.com
c:\vbados\vbmouse.exe uninstall
config -set cputype=auto

[FeralChild64]

This driver is mainly useful if booting real MS-DOS. We already provide what is needed for the Windows INT33 driver.

[Grounded0]

I have a little bit of a problem when working with MS-DOS Prompt inside Windows 3.1x. Mainly tracking and mouse click registration problems. When VBMOUSE.EXE is loaded its smooth sailing even with MS-DOS Prompt running.

Is VBMOUSE.EXE only required if you use MS-DOS Prompt inside Windows 3.1x? It could be that i have something wrongly configured or does loading the FreeDOS COMMAND.COM cause problems. The running process in the status line changes from KRNL386 to COMMAND when i'm running MS-DOS Prompt.

Can you personally notice this, is this expected behaviour or should i file a ticket about it?

[FeralChild64]

@Grounded0 I can see the mouse does nit behave correctly within MS-DOS Prompt window, but I think it would be a good idea to have an issue for this.