Open ghost opened 2 years ago
Did you follow the wiki instructions, in particular this comment:
If given the option during installation, do not select the "IBM Personal Systems/2 Mouse", as it seems to cause Windows to hang at the title screen. Instead select the "Microsoft Mouse connected to PS/2 Mouse Port".
yes i did, but i selected Microsoft Mouse (Bus or Serial)
because that option supports both ps/2 and serial mouse
i tried the Ps/2 mouse option, it too gave broken mouse in 386 mode (win386) , but worked fine in real mode
Bus mouse is NOT PS/2. It is a different (rare) connection type.
i know, i tried Microsoft Mouse Connected at PS/2 Port
but it also gave broken mouse
I have been doing some testing with DOSBox-X 0.83.2 to 0.83.18 with the Microsoft PS/2 mouse option selected during SETUP.
Booting DOS (6.22) and starting Windows/386 2.11 with WIN386.EXE works, and you can navigate the menus with the keyboard. But the moment you try to use the mouse, Windows freezes and neither mouse nor keyboard work.
Starting the same windows version with WIN86.COM and the mouse works fine.
I tried enabling some LOG debug options (keyboard, mouse, pit, pic) but it did not output any useful errors, other then after a few keystrokes that the keyboard buffer was full. The only error of note is perhaps this one:
LOG: 41184662 ERROR BIOS:INT16:Unhandled call 6F
But this happens on startup of Windows, before trying to use the mouse.
for me , keyboard works but mouse doesn't , and loading mouse drivers as CTMOUSE before Windows doesn't work
Windows has it's own mouse driver, loading a DOS mouse driver beforehand does nothing other then wasting some ram.
Sorry for bumping this, but I have this issue as well. Windows 1.04 and Windows for Workgroups 3.11 work just fine, but Windows 2.11/386 doesn't unless I start it in non-386 mode ("WIN86.COM"), otherwise, it outright just freezes when it reaches the desktop, neither the keyboard or the mouse work.
As a workaround you can use the serial mouse emulation that DOSBox-X provides, and select a serial mouse during Windows SETUP.
I just tried reinstalling with the "IBM Personal System/2 Mouse", "No Mouse or other pointing device", "Microsoft Mouse (Bus or Serial)" and the "Microsoft Mouse connected to Serial-PS/2 Interface" pointing device options with serial mouse emulation enabled and it is still the same. I also tried stripping down my autoexec.bat and config.sys each time by pressing F8 on startup of MS-DOS 6.22, but no results still.
Code of Conduct & Contributing Guidelines
Have you checked that no other similar bug report(s) already exists?
What operating system(s) this bug have occurred on?
Windows 10 21H1
What version(s) of DOSBox-X have this bug?
Dosbox-X 0.83.16 SDL1
Describe the bug
i installed Windows 2.1x/386 on top of MS-DOS 3.31 on 32mb hdd image, typing WIN386 works, but mouse does not move type WIN86 works and mouse works
Expected behavior
expected working mouse in 386 mode
Steps to reproduce the behaviour
install DOS 3.31 on hdd image: 1.IMGMAKE win386.img -t hd -size 31 -nofs 2.imgmount 2 win386.img 3.imgmount a dos331.img 4.boot -l a 5.FDISK 6.Format C: /s (after rebooting guest system) after installing: 1.imgmount c win386.img 2.imgmount a disk01.img disk02.img disk03.img disk04.img disk05.img 3.boot -l C 4.a: 5.setup after installing windows 386: win386 and get a broken mouse , exiting and typing win86 and mouse works fine
Used configuration
Emulator log
Additional context
here is the hdd image: https://mega.nz/file/AlBFVSaR#O2heF9Vhl_o8llsqt71gXONMTv4AdTJb6jvRUpkA_Nc