What happened?
Mouse pointer position oscillates rapidly between two points in y axis only.
A Microsoft two button serial mouse is defined and attached to the COM1 port of a Tandy SL/2.
The machine is booted and mouse input is captured. Deskmate is started from the ROM. (In my case, from D:)
Mouse pointer is initially static and stable. After a short time moving the mouse pointer, the pointer will typically oscillate between two points on the y axis. This may be stable, or may slowly resolve itself by the two y axis points moving closer together until settling on a single point. This will happen again shortly after moving the mouse pointer.
I have not observed this behaviour in the x-axis.
Further information:
This behaviour seems to happen regardless of whether the Microsoft MS-DOS mouse driver is loaded or not.
This behaviour is also observed in all of the applications below:
Carrier Command
Sim Ant
Lemmings
Sim City
Castle Master
I don't notice this behaviour in Windows 2.03
As far as I can tell, the bug seems to have been introduced in build #4860, where a more serious bug was eliminated.
Please let me know if I can give any more information.
Configuration file
[General]
vid_renderer = qt_software
host_cpu = Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
emu_build_num = 6033
uuid = d1a49e3e-e0c3-5f4d-a9e0-05d344c3326f
video_fullscreen_first = 0
kbd_req_capture = 1
force_43 = 1
[Machine]
machine = tandy1000sl2
cpu_family = 8086
cpu_speed = 8000000
cpu_multi = 1
cpu_use_dynarec = 0
fpu_softfloat = 0
time_sync = local
mem_size = 640
[Video]
gfxcard = internal
[Input devices]
mouse_type = msserial
[Sound]
fm_driver = nuked
[Network]
net_01_link = 0
net_02_link = 0
net_03_link = 0
net_04_link = 0
[Storage controllers]
hdc = xta_wdxt150
cassette_mode = load
[Ports (COM & LPT)]
serial2_enabled = 0
[Floppy and CD-ROM drives]
fdd_01_type = 35_2dd
fdd_01_image_history_01 = /home/phil/Documents/86Box/Floppy Images/TotalEclipse.img
fdd_01_image_history_02 = /home/phil/Documents/86Box/Floppy Images/Lemmings/Lemmings720.img
fdd_02_image_history_01 = /home/phil/Documents/86Box/Floppy Images/Games/Carrier360.img
fdd_02_image_history_02 = /home/phil/Documents/86Box/Floppy Images/Arkanoid/Arkanoid.img
fdd_01_image_history_03 = /home/phil/Documents/86Box/Floppy Images/Lemmings_Crack.img
fdd_02_image_history_03 = /home/phil/Documents/86Box/Floppy Images/001831_lode_runner/disk01.img
fdd_02_image_history_04 = /home/phil/Documents/86Box/Floppy Images/000447_bubble_bobble/disk2.img
fdd_01_image_history_04 = /home/phil/Documents/86Box/Floppy Images/Super Tetris crack EXE file.IMA
[WDXT-150 XTA Fixed Disk Controller]
base = 0320
irq = 5
bios_addr = C8000
bios_rev = rev_1
[Hard disks]
hdd_01_parameters = 17, 6, 615, 0, xta
hdd_01_fn = HD_Images/HD_Image_1.vhd
hdd_01_xta_channel = 0
hdd_01_vhd_blocksize = 1024
[Microsoft Serial Mouse]
port = 0
buttons = 2
Operating system
Linux Mint 20.3
CPU
Intel Core i7 6700K clocked to 4.6 GHz
86Box version
build 6033
Build architecture
Linux - x64 (64-bit)
Build type
Download source
Official website (Jenkins, GitHub)
Additional context
No response
What happened?
Mouse pointer position oscillates rapidly between two points in y axis only.
A Microsoft two button serial mouse is defined and attached to the COM1 port of a Tandy SL/2.
The machine is booted and mouse input is captured. Deskmate is started from the ROM. (In my case, from D:)
Mouse pointer is initially static and stable. After a short time moving the mouse pointer, the pointer will typically oscillate between two points on the y axis. This may be stable, or may slowly resolve itself by the two y axis points moving closer together until settling on a single point. This will happen again shortly after moving the mouse pointer.
I have not observed this behaviour in the x-axis.
Further information:
This behaviour seems to happen regardless of whether the Microsoft MS-DOS mouse driver is loaded or not.
This behaviour is also observed in all of the applications below:
Carrier Command
Sim Ant
Lemmings
Sim City
Castle Master
I don't notice this behaviour in Windows 2.03
As far as I can tell, the bug seems to have been introduced in build #4860, where a more serious bug was eliminated.
Please let me know if I can give any more information.
Configuration file
Operating system
Linux Mint 20.3
CPU
Intel Core i7 6700K clocked to 4.6 GHz
86Box version
build 6033
Build architecture
Linux - x64 (64-bit)
Build type
Download source
Official website (Jenkins, GitHub)
Additional context
No response