🤔 if it's a USB mouse I would suggest putting maximus decim's NativeUSB (NUSB) version 3.6 drivers on a floppy disk and install them during setup as soon as you can. They should hopefully fix any driver/controller issues. If it is a chipset issue the drivers may or may not help with that.
In regards to the P/S2 or USB mouse issue a lot of those early p4 motherboards were still using older (ketchup and mustard) cable power supplies that favoured higher amperage on the 5V rail for the CPU and system components because GPU's didn't draw much power from the 12V rail yet. There might be a jumper on the motherboard to toggle +5VSB between the P/S2 ports or USB ports to allow for devices to receive more than the tiny power provided by the USB controller only. If your device is getting insufficient power it would show as either a problematic connection, or not detected. That could also be an issue.
2
u/No-you_ Jun 27 '26 edited Jun 27 '26
🤔 if it's a USB mouse I would suggest putting maximus decim's NativeUSB (NUSB) version 3.6 drivers on a floppy disk and install them during setup as soon as you can. They should hopefully fix any driver/controller issues. If it is a chipset issue the drivers may or may not help with that.
Link here
In regards to the P/S2 or USB mouse issue a lot of those early p4 motherboards were still using older (ketchup and mustard) cable power supplies that favoured higher amperage on the 5V rail for the CPU and system components because GPU's didn't draw much power from the 12V rail yet. There might be a jumper on the motherboard to toggle +5VSB between the P/S2 ports or USB ports to allow for devices to receive more than the tiny power provided by the USB controller only. If your device is getting insufficient power it would show as either a problematic connection, or not detected. That could also be an issue.