summaryrefslogtreecommitdiffstats
path: root/mailinglist/output_launchpad/1785485
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 14:51:13 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 14:51:13 +0000
commit225caa38269323af1bfc2daadff5ec8bd930747f (patch)
treee0a5fefde9ee100ba6f32fb36de6707490e4164e /mailinglist/output_launchpad/1785485
parent904141bfb8d5385b75eb3b7afec1dcda89af65a7 (diff)
downloademulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.tar.gz
emulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.zip
add mailinglist scraper results
Diffstat (limited to 'mailinglist/output_launchpad/1785485')
-rw-r--r--mailinglist/output_launchpad/178548526
1 files changed, 26 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1785485 b/mailinglist/output_launchpad/1785485
new file mode 100644
index 00000000..52e991be
--- /dev/null
+++ b/mailinglist/output_launchpad/1785485
@@ -0,0 +1,26 @@
+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.
+