NT 3.51 SMP support breaks BIOS USB legacy mouse.

[diovanti]

*from boot.ini*
multi(0)disk(0)rdisk(0)partition(3)\WINNT35="Windows NT 3.51"  /sos
multi(0)disk(0)rdisk(0)partition(3)\WINNT35="Windows NT 3.51 [APIC] SP" /sos  /hal=halapic.dll /kernel=ntoskrnl.exe
multi(0)disk(0)rdisk(0)partition(3)\WINNT35="Windows NT 3.51 [APIC] MP" /sos  /hal=halapic.dll /kernel=NTKRNLMP.exe
multi(0)disk(0)rdisk(0)partition(3)\WINNT35="Windows NT 3.51 [MPS]"     /sos  /hal=halmps.dll  /kernel=NTKRNLMP.exe

When I enable multiprocessor support, halmps w/ ntkrnlmp, any connected USB mice don't work. USB keyboard still works without any problems. There must be some kind of glitch that is disrupting USB BIOS legacy mouse support.

If I use halapic w/ ntkernmp, the mouse works fine, but any network access quickly hardlocks the system. Does halapic.dll even support multiprocessor configuration or is it only supposed to be used with SP kernel?

Default HAL is fine, but alas no multiprocessor support.

MPS version 1.1 is set in the BIOS.

Any ideas on how to get mice working without sacrificing dual core support?

---
Foxconn 865G7MF-SH LGA 775 Intel 865G
Pentium D  3.2GHz (Dual Core), 2GB RAM
GeForce 5200 AGP, VBEMP 2015 for NT 3.51, SNAP for OS/2
Realtek 8139 100Mbps Onboard [10ec:8139], SUBSYS [105b:0c71]
Onboard ICH5 2xSATA, VIA 6241 2xSATA PCI (Memphis BIOS), UniATA Duh!
FreeDOS, ME, NT 3.51 / 4 / 5 / 5.1 / 6, ReactOS (Doesn't Work)
OS/2 4.52, Solaris 10u8, Fedora 8, Mint 18.3

[broken120x120]

Maybe this isn't the best answer, but you could always just use a PS/2 mouse instead of a USB one. Alternatively, if you like the mouse that you are using, you can get a USB to PS/2 adapter that simply emulates your USB mouse as a PS/2 mouse. If for some reason your computer lacks a PS/2 port, you could also get a PCI PS/2 card.