| Author | Message | ||
     Christian Reynolds Rating: N/A |
I had a really bad flash/flicker problem with my h3d gaming glasses. I called i-glasses support, and they told me to wait until the new nvidia drivers came out. I told them I had the same problem on my Creative labs Riva TNT and my new PNY GeForce 4/MX420 card and they asked me to send back my goggles for a replacement while I was waiting for the new nVidia drivers. I recieved the replacement lasses and have loaded the latest Detonator Drivers from NVIDIA and was having the same problem. After reading a few threads here about IRQ conflicts, I surmised that I had 6 items on IRQ 11, with no way to change it. Per Microsoft, Win2k DOES NOT allow manual setting of IRQ's and my BIOS doesn't allow me to assign IRQ numbers to individual PCI slots. SO I used the hardware profile feature under Win2k to disable each one, and guess what? IT WAS MY NIC CARD. Well I cant very well play network games in stereo without a nic card so I disabled ACPI interface in win2k by changing the ACPI driver under device manager-->computer, to STANDARD PC. The next time I booted, My GeForce card was on IRQ10 and the NIC was on IRQ11. Well I thought, that should have fixed it...BUT NO!!!! The flickering was less often, but still there. So AGAIN I disabled the NIC, and it went away. So then I disable my com ports and lpt ports so that I wasn't sharing ANY IRQ's ANYWHERE, The NIC was on IRQ 7, Video on IRQ 10, and STILL had the same problem. The obvious assumption here is that my NIC card is causing the flickering no matter WHAT irq it is set to. Hope this helps someone... Christian Reynolds | ||
| Michael Parker Rating: N/A |
Hi Christian The PCI bus supports shared Interrupts so the fact that you have a number of devices on the same Interrupt is not necessarily a problem. When more than one device is sharing the same physical interrupt the interrupt handlers are responsible for recognising their own device. When any physical interrupt fires, the operating system calls each interrupt handler in turn until one of the handlers claims the interrupt. If the device drivers don't handle interrupts correctly you can get problems, another good reason for keeping your drivers up to date. Just out of interest, have you run one of the refresh rate fixers for Win2K, to cure the 60Hz default refresh rate problem? Mick |
