Originally posted by: John
I build and service a lot of systems, therefore I have the opportunity to work with a lot of different hardware. I can't recall the last time I've seen the NVIDIA IDE driver cause a stability or performance problem on a nForce Intel or AMD rig. Most of the time the naysayers that continually bash the NVIDIA IDE driver have very little technical experience. If you like using the MS IDE driver then more power to ya. Whatever works best and gives you a good piece of mind is all that really matters; especially if it's your own system.
I guess so. The reason I ask is, are there any advantages whatsoever with installing the NVIDIA SW IDE driver besides hotplug support which triggers the annoying 'Safely Remove Hardware' system tray icon? We already know its NCQ support is helpless on desktop systems.
I find the logic flawed that you would risk instability when there are no real advantages to it. My A8N-SLI Deluxe nForce 4 SLI system will flat-out not boot (BSOD with nv sata sys driver) with BIOS 1001 and the latest NVIDIA SW IDE driver, and that's on a brand new install of XP SP2. I have tried it, and it's very frustrating. With the latest BIOS it will boot properly, but then my display drivers will crash spontaneously. When I do not install the SW IDE, my display driver never crashes. I do not overclock, and my memory has passed an hour of memtest (and I do not have any stability problems with other programs or drivers).
ASUS themselves say right on the chipset download to update the BIOS before installing the chipset driver, and there's a reason for that. Just FYI...
In regards to the NVIDIA NAM, I choose not to install it since there are other viable options. A NAT router w/ SPI is a move viable option IMHO.
I agree with that. I have had a NAT router and not a single virus. NAT is secure by nature, on the inbound. And to get viruses to send stuff >>out, you'd have to open e-mail attachments/receive via a hole in web browser to trigger a virus to exist in the first place. Proper patching (WMF exploit for example) and reasonable practices (disable preview in OE so shell stuff can't execute) will prevent the virus in the first place.