when i open up doubledawg, i can only see my graphics card on the list of pci cards.. not my scope cards??
anybody??
thanks!
problem with doubledawg?
-
the19thbear
- Posts: 1499
- Joined: Thu Feb 20, 2003 4:00 pm
- Location: Denmark
- Contact:
-
the19thbear
- Posts: 1499
- Joined: Thu Feb 20, 2003 4:00 pm
- Location: Denmark
- Contact:
-
hubird
Smaller values of 'Scope latency' make the PCI bus stress more.
'Latency' in relation to the PCI bus is a different kind of 'latency', as explained by Astroman recently.
Smaller 'PCI latency' disstresses the bus, as smaller chunks of data to transmit are easier to handle than large ones when it's busy.
You have to find the right balance between both values, depending on your pc system.
Correct me if I'm wrong guys
'Latency' in relation to the PCI bus is a different kind of 'latency', as explained by Astroman recently.
Smaller 'PCI latency' disstresses the bus, as smaller chunks of data to transmit are easier to handle than large ones when it's busy.
You have to find the right balance between both values, depending on your pc system.
Correct me if I'm wrong guys
-
Music Manic
- Posts: 1743
- Joined: Wed May 15, 2002 4:00 pm
- Contact:
Set your BIOS pci latency timer to somewhere between 64 and 128 (96 usually works for me). The actual best setting really depends on your system and what other devices 'live' on the PCI bus in it. It's good to remember that this works like a priority level and determines the amount of time a device is given when its interrupt is being handled by the cpu. So it's a bit like a time 'window', values can be too high or too low, you want to aim for the 'sweet spot' in between.
The point of doubledawg specifically is: many modern graphics card drivers will set your graphics card latency somewhere between 248 & 255 which is entirely too high! When the graphics card's irq is served on the CPU it will be very unforgiving about giving up its 'time slice' which limits the performance of your Scope cards, sometimes even causing pci overflows due to inability of the cpu getting around to serving the Scope card's irq in time.
So Doubledawg allows you to change that value for the graphics card back down to something reasonable. Setting your graphics card to a low enough priority usually will mean you don't have to even fiddle with your BIOS setting. I don't even have to worry about doubledawg usually here until I want to squeeze the last few drops of performance from my systems.
Setting the PCI latency timer to 128 and then using doubledawg to set the graphics card to something even lower (like 96) might resolve issues with problematic chipsets..
The point of doubledawg specifically is: many modern graphics card drivers will set your graphics card latency somewhere between 248 & 255 which is entirely too high! When the graphics card's irq is served on the CPU it will be very unforgiving about giving up its 'time slice' which limits the performance of your Scope cards, sometimes even causing pci overflows due to inability of the cpu getting around to serving the Scope card's irq in time.
So Doubledawg allows you to change that value for the graphics card back down to something reasonable. Setting your graphics card to a low enough priority usually will mean you don't have to even fiddle with your BIOS setting. I don't even have to worry about doubledawg usually here until I want to squeeze the last few drops of performance from my systems.
Setting the PCI latency timer to 128 and then using doubledawg to set the graphics card to something even lower (like 96) might resolve issues with problematic chipsets..