dualcore issue ; can anyone give me scope 3.1b driver?
Hi Okantah,
please leave AndreD a private message here on planetZ.
cheers
ralf
please leave AndreD a private message here on planetZ.
cheers
ralf
On 2006-09-08 09:55, okantah wrote:
Hi Ali why is it so difficult to have contact with Andre ?
I think his advice for the Asus p5wd2-e premium is more of COMPROMISED to Creamware products,sts crushies all the time.
He's also not available just to inform his customers about complains base on his recommendation.what exactly is the reason & he's advice on his configurations both hardware & the BIOS may be might help.
okantah
Okantah,
I am also using an Asus P5WD2 mobo, with a D930 processor, and it works very well, even with STS. I did have to perform some tricks to get it working, but most is straightforward. In the BIOS, you should enable PnP OS, and disable every device you don't need. In my case, this meant the Onboard audio, LAN (2x), SATA controller and Raid controller. Then, inside Windows device manager, find out what else might be sharing IRQs and disable it: LPT ports, Serial ports, USB controllers, etc.
Another important thing is to edit the cset.ini on the Bin folder of sfp (check out the XTC threads on this):
"Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
whereby x is a values out of 64, 128, 256, 512 or 1024 and translates as follows to the card's latency:
64: latency = 3 ms
128: latency = 4 ms
256: latency = 7 ms
512: latency = 13 ms
1024: latency = 25 ms"
There's another intBlkSize=x line a little bit below that below (under [hw], I think), that should be changed to the same value. I know this is only meant for XTC, but it has helped in solving some problems where the BSOD would appear.
I have two scope cards and an RME hammerfall installed on the PCI bus. One scope shares IRQ with the 1394 controller (which could be disabled, but I need it for external HD) and with the PCI-E graphics bus and board, the other is sharing IRQ with the RME, but everything works normally. MV tests aren't so great, but it's stable and working.
Hope this helps. Best of luck configuring your PC, and be certain that, unless you have some faulty components in there, the P5WD2 will work with scope, and soon you'll be spending hours working or having fun with your setup, instead of banging your head against the wall.
Much peace,
T
I am also using an Asus P5WD2 mobo, with a D930 processor, and it works very well, even with STS. I did have to perform some tricks to get it working, but most is straightforward. In the BIOS, you should enable PnP OS, and disable every device you don't need. In my case, this meant the Onboard audio, LAN (2x), SATA controller and Raid controller. Then, inside Windows device manager, find out what else might be sharing IRQs and disable it: LPT ports, Serial ports, USB controllers, etc.
Another important thing is to edit the cset.ini on the Bin folder of sfp (check out the XTC threads on this):
"Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
whereby x is a values out of 64, 128, 256, 512 or 1024 and translates as follows to the card's latency:
64: latency = 3 ms
128: latency = 4 ms
256: latency = 7 ms
512: latency = 13 ms
1024: latency = 25 ms"
There's another intBlkSize=x line a little bit below that below (under [hw], I think), that should be changed to the same value. I know this is only meant for XTC, but it has helped in solving some problems where the BSOD would appear.
I have two scope cards and an RME hammerfall installed on the PCI bus. One scope shares IRQ with the 1394 controller (which could be disabled, but I need it for external HD) and with the PCI-E graphics bus and board, the other is sharing IRQ with the RME, but everything works normally. MV tests aren't so great, but it's stable and working.
Hope this helps. Best of luck configuring your PC, and be certain that, unless you have some faulty components in there, the P5WD2 will work with scope, and soon you'll be spending hours working or having fun with your setup, instead of banging your head against the wall.
Much peace,
T