summary refs log tree commit diff stats
path: root/results/classifier/118/none/1785485
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/none/1785485')
-rw-r--r--results/classifier/118/none/178548556
1 files changed, 56 insertions, 0 deletions
diff --git a/results/classifier/118/none/1785485 b/results/classifier/118/none/1785485
new file mode 100644
index 000000000..22b1550f3
--- /dev/null
+++ b/results/classifier/118/none/1785485
@@ -0,0 +1,56 @@
+graphic: 0.709
+device: 0.685
+user-level: 0.642
+semantic: 0.603
+performance: 0.577
+peripherals: 0.410
+mistranslation: 0.405
+network: 0.375
+register: 0.347
+permissions: 0.329
+ppc: 0.321
+vnc: 0.318
+arm: 0.307
+architecture: 0.305
+debug: 0.300
+socket: 0.297
+risc-v: 0.285
+files: 0.269
+VMM: 0.265
+PID: 0.257
+boot: 0.250
+virtual: 0.244
+kernel: 0.238
+hypervisor: 0.224
+TCG: 0.220
+x86: 0.199
+KVM: 0.175
+i386: 0.147
+assembly: 0.143
+
+Mouse moves erratically when using scroll wheel on Windows NT 4, Windows 95, and Windows 3.1 guests
+
+QEMU version: 3.0.0 RC3
+Guests: Windows NT 4.0, Windows 95, Windows 3.1
+
+Program: When the user uses the scroll wheel, the mouse's movement becomes erratic. 
+
+This is noticed immediately when the scroll wheel is used. Sometimes the problem can be fixed by moving the scroll wheel some more.
+
+My theory is this problem is because of the lack of support for the Microsoft Intellimouse in these guest operating systems.
+
+The QEMU project is currently considering to move its bug tracking to
+another system. For this we need to know which bugs are still valid
+and which could be closed already. Thus we are setting older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+After doing tests with Windows 95, 3,1, NT 4.0, and 2000 I can say this bug appears to be fixed.
+