Ticket #1502 (closed defect: fixed)

Opened 9 years ago

Last modified 8 years ago

Mouse problem in Win 3.x (VM lockup on first click)

Reported by: ghr Owned by:
Priority: major Component: other
Version: VirtualBox 2.0.4 Keywords: mouse win 3.x
Cc: Guest type: Windows
Host type: other


Host: Win XP Home SP1

Guest: DOS 6.22/Win 3.x

Problem: at first mouseclick in Win 3.x the VM freezes and consumes 100% CPU (which it normally doesn't due to wqghlt.386 installed).

Workaround: use keyboard for getting around :-(

Note: reminds me somewhat of a problem I had with same host, same guest and VB 1.3.8 (problem disappeared with VB 1.4.0; VB 1.5.6 was also fine)

Change History

comment:1 Changed 9 years ago by ghr

With a VM created under 1.6.0 VirtualBox 1.6.2 gives the same result: Mouse is useless.

comment:2 Changed 8 years ago by timanderson

Confirmed here too. Would like to find a fix.


comment:3 Changed 8 years ago by urza9814

Same problem here, but even when navigating with the keyboard it will frequently lock up.
Tried to uninstall mouse drivers, but that also caused it to lock up.
Reinstalled without any mouse driver and it's running fine.

comment:4 Changed 8 years ago by vin

Same issue. I'll confirm that the problem does not exist in 1.5.6, as that's what I've had to downgrade to in order to get my 3.1 VMs running. This means no SB16 sound though, so still waiting on a fix in 1.6.x

comment:5 Changed 8 years ago by sandervl73

  • Version changed from VirtualBox 1.6.0 to VirtualBox 1.6.4
  • Summary changed from Mouse problem in Win 3.x to Mouse problem in Win 3.x (VM lockup on first click)

comment:6 Changed 8 years ago by sandervl73

  • Guest type changed from other to Windows

comment:7 Changed 8 years ago by Kira

I can confirm that the problem still exists in 1.6.6.

A workaround is to use "win /s" to start Windows 3.1 in Standard mode rather than 386 Enhanced mode. Unfortunately, this won't work in Windows 3.11 as it doesn't have Standard mode.

comment:8 Changed 8 years ago by webman

Still exists in verion 2.0.0 of virtualbox

comment:9 Changed 8 years ago by vin

Also still in 2.0.2

comment:10 Changed 8 years ago by The MAZZTer

I confirm, but oddly sometimes I can get ONE click in. Then the second kills it.

comment:11 Changed 8 years ago by educos

Got the same issue - also decided to use the keyboard to navigate through the (old!) UI. However the VM still locked when I tried to increase the resolution from VGA (the default) to VGA 1024x768 256 colors.

The fix is really simple: Maybe I should just get a life and not mess with Windows 3.1 :)

comment:12 Changed 8 years ago by vin

No fix yet in 2.0.4. Version on this bug should probably be updated to reflect that this is still an issue with the 2.0.x series.

comment:13 Changed 8 years ago by sandervl73

  • Version changed from VirtualBox 1.6.4 to VirtualBox 2.0.4

comment:14 Changed 8 years ago by Mash

same problem here. Installed Windows 3.11 (on DOS 6.22). The system freezes after 3 minutes. VirtualBox Version is 2.0.4

comment:15 Changed 8 years ago by DaveLovesVBox

Problem still exists with 2.06. XP, DOS 6.22, win3.1

Are these bug reports being ignored?

comment:16 Changed 8 years ago by michael

All bug reports are looked at, but we simply lack the manpower to deal with them all (just subscribe to the vbox-trac list to get a feeling for the numbers). I know that this has been said before, but the vast majority of the VirtualBox code is available under the GPL, so there is nothing stopping other people from working on resolving bugs, problems and feature requests.

comment:17 Changed 8 years ago by vin

There's been no specific mention in the changelog, but brief testing with 2.1.2 caused no lockup in WFW 3.11. Where as recently as 2.1.0, it would lock up within the first couple of clicks or a few seconds of mouse movement.

comment:18 Changed 8 years ago by ni81036

  • Status changed from new to closed
  • Resolution set to fixed

Yes, there were fixes in dynamic recompiler which could have fixed this issue. Will close it, please reopen if not really fixed.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use