Tank252ca

Oh, and that BIOS in your sig is still in beta, I believe. If you want support from DFI, be sure to revert to 623-3 which I think is the latest official release.

I have a feeling that a BIOS fix for this won't be too high on the priority list. All I can think of is a USB to PS2 adapter (or visa versa). Not perfect, but you need to get both devices connected to the same kind of port. I've never tested these for compatability, but a quick Google search turned up http://sewelldirect.com/ps2tousb.asp Maybe you can find something locally? Circuit City perhaps?

Vista, the default setting in the BIOS is for USB keyboard and USB mouse set to disabled, so if you reset the BIOS you need to enable any USB input devices again. I think you're fortunate that the trackball works with a USB keyboard. If AngryGames or Rgone are following this thread, any chance at all that a future BIOS update will allow use of mixed USB and PS2 keyboards and mice? It seems rather odd that I should have to keep my old PS2 keyboard plugged in to use my PS2 mouse, or that I should have to purchase a new USB mouse to go with the USB keyboard. I would happily give up the CMOS Reloaded feature to gain PS2 + USB functionality.

Well, I flashed the BIOS to NF4LDB14 and the PS2 mouse will still not work with a USB keyboard. Hopefully the Lanparty UT nF4 is not so old that they won't update the BIOS again (unless this is a hardware issue). Any way, Airdog, looks like the system you built either needs a PS2 keyboard and mouse or USB keyboard and mouse. I have both keyboards plugged in at the moment to keep things running until I replace the mouse, but if you're assembling a system for someone that obviously isn't an option. At least mice and keyboards are cheap.

Airdog, I am experiencing the exact same problem. My Lanparty UT nF4-D has been working fine for months, and when I exchanged the PS2 keyboard for a new USB Saitek Eclipse, the PS2 mouse was no longer working after I rebooted. (If I hotswap the keyboards while the system is running, the USB keyboard and PS2 mouse work. Rebooting kills the mouse.) The mouse and PS2 port are completely missing from the hardware list and there is no IRQ reserved for the mouse any longer. I contacted Saitek and was told that they had a couple of other reports of PS2 mice not working, and that in those instances it was a BIOS issue. Some motherboards require that a PS2 keyboard be connected for the PS2 mouse port to work. Looks like the DFI Lanparty suffers from that problem. I am already running BIOS 623-3, so that won't fix it for you, unfortunately. I am going to try the LDB14 BIOS from 2005/11/14 and will post results here.

Thanks for the suggestions. When I went to upgrade the BIOS I found out that the floppy drive did not work. It's an older dual floppy with 3½" and 5¼" drives in one unit. The connector on the drive is not keyed and when I examined the pin numbering I found out that the connector is backwards compared to single floppy drives sold today, so I had the cable on upside down. Turns out that the upside down floppy cable was the source of all of my blue screens, but I did update the BIOS any way and the system is rock solid now. 3dMark 2003 and 2005 both run smoothly. I'm very happy with this motherboard.

I uninstalled the nForce IDE drivers, but still got the blue screens. I noticed that when my Logitech Formula Force USB wheel was plugged in and powered on, the system would blue screen on every boot attempt, although I could boot with the wheel off and then turn the wheel on afterwards and calibrate it ok. I carefully scanned the registry deleting all Logitech Profiler and Wingman software entries (leaving any mouse entries untouched) and ran a registry cleaner to remove any dead entries (this was an upgrade from Windows98SE). XP was still able to detect the make and model of the wheel, but the proper calibration screen was now gone (defaulted to joystick setup) so I installed the Wingman software again. (Note: Do not use the latest Wingman software if you own an old Formula Force wheel. Support for the FF was dropped with version 4.4 and later. I recommend version 4.3 of the Wingman software unless you have a newer wheel like the Logitech Momo). With the proper Wingman Profiler installed the wheel calibrates correctly again and the system will now boot up with the wheel plugged in and powered on. Will do some more extensive testing this weekend and report back. There may be a USB issue so I might flash to a newer BIOS.

Thanks, I'll start with removing the IDE drivers. BTW, 157 passes of memtest386 and no errors, so the memory appears to work fine. Must be a driver or BIOS issue. Need to get this fixed as I'm off to a LAN part in two days. :eek:

Just put a new system together (specs below) but I'm getting various blue screens in XP-SP2, including THREAD_STUCK_IN_DEVICE_DRIVER, IRQL_NOT_LESS_THAN, PFN_LIST_CORRUPT and page faults. Occurs during regular desktop chores, not just 3D gaming. The system is running stock (no overclocking) and I'm using the default BIOS settings except for Maximum Payload Size = 256 and the serial port, IRDA and SATA devices are disabled. Looks like it could be a memory issue, although I did run memtest386 before installing the drives and no errors came up (and I'm running it again all day today). I have 2x512MB of OCZ Permier PC3200 dual-channel RAM: http://www.ocztechnology.com/products/memo...er_dual_channel Is this considered 'value' memory? The system is set at the rated 2.5-3-3-7. Just wondering if I should be using the BIOS settings posted by RGone and AngryGames? Are the Nforce IDE drivers an issue under XP? I'll try and get the BIOS version number posted today. I do have the two extra (molex and floppy) power connectors plugged into the motherboard. Any suggestions welcome.