Hi anybody!!!
I just bought new PC with Asus P5b deluxe and intel core2 duo 6400,kingston pair ram 2GB 800Mhz.
I have tryed everthing to make this work with my Pulsar2 and SRB 4dsp but there is not solution....In installed .Windows ACPI mode there is random glitches and strange effects??driver from Creamware is dating from 2002 year???????what f....????
PC work good just with disabled APIC in bios.......... but is there logic to pay for core2 duo and use just 1core from them....
Please if anybody have similar Pc configuration and have solution please help...
Is there chance we get new drivers compatibile with new Core2 duo processors or we must change our platforms [ I have Creamware 5 year and work ok with Asus Cusl2 and pentium3 processor} and bay new audio card??????
Now I work with disabled 1core and waiting for new drivers........
BIG PROBLEMS with Intel Core2 Duo +Asus P5B Deluxe
I would make an install with just the Pulsar 2 - and only after that's finished and running add the 4 DSP SRB.
I've recently installed Scope 4.5 for a Pulsar One under Win2K on an ASUS Tusl - and that was a nightmare, politely spoken...
But I am 99% certain that it was due to the OS - it messed the driver registration to a degree that not even boot into 'safe mode' was possible - and I never had a problem installing under Win98...
anway - the 'driver' is a piece of input/output software, that does nothing but communicating with an abstract interface (on the mobo) according to the PCI standard.
The CPU shifts a few bits and plays supervisor - there isn't even a technical need to 'update' such drivers because of a new model or marketing hype.
I've mentioned it a couple of times that one of my applications used the same network driver to access an Oracle database during 10(!) years, without changing a single line of code, while the (Mac) OS changed from 7 to 9 and to OSX, making 6 major releases.
Most of the update blurb is bs anyway - A comment from a developer who changed from Delphi to dotNet and C# '... it's really easy to write or edit an application, we spare a lot of time... but jeez is that bloated and slow code... you really notice it...
they do have more than enough ways to waste cycles on modern CPUs - and they will use them...
sorry for the OT rant, but sometimes that u-word just brings me up
cheers, Tom
I've recently installed Scope 4.5 for a Pulsar One under Win2K on an ASUS Tusl - and that was a nightmare, politely spoken...
But I am 99% certain that it was due to the OS - it messed the driver registration to a degree that not even boot into 'safe mode' was possible - and I never had a problem installing under Win98...
anway - the 'driver' is a piece of input/output software, that does nothing but communicating with an abstract interface (on the mobo) according to the PCI standard.
The CPU shifts a few bits and plays supervisor - there isn't even a technical need to 'update' such drivers because of a new model or marketing hype.
I've mentioned it a couple of times that one of my applications used the same network driver to access an Oracle database during 10(!) years, without changing a single line of code, while the (Mac) OS changed from 7 to 9 and to OSX, making 6 major releases.
Most of the update blurb is bs anyway - A comment from a developer who changed from Delphi to dotNet and C# '... it's really easy to write or edit an application, we spare a lot of time... but jeez is that bloated and slow code... you really notice it...
they do have more than enough ways to waste cycles on modern CPUs - and they will use them...
sorry for the OT rant, but sometimes that u-word just brings me up
cheers, Tom
Basically what they're saying is that your conflicts are likely a result of too much going on at the hardware level. There's no need to disable APIC/ACPI, you simply need to get the primary Scope card in a slot that isn't shared.
The real issue here is the feature glut in modern hardware, as companies shoehorn in as much as possible to appeal to consumer purchasers.
The real issue here is the feature glut in modern hardware, as companies shoehorn in as much as possible to appeal to consumer purchasers.
Hi!
Thankyou for your fast reply...
Pulsar not sharing IRQ and I have not conflict,with and without midi connected gliches still stay same...With installed Windows in ACPI PC can work ok days and then randomly apear glitches,freezes.....
I trayed 3.1b drivers,same thing again.... problems...
Tested with difrent VGA cards ATI X550 and NVIDIA 7300...With ATI I get more problems and freezing.
Thankyou for your fast reply...
Pulsar not sharing IRQ and I have not conflict,with and without midi connected gliches still stay same...With installed Windows in ACPI PC can work ok days and then randomly apear glitches,freezes.....
I trayed 3.1b drivers,same thing again.... problems...
Tested with difrent VGA cards ATI X550 and NVIDIA 7300...With ATI I get more problems and freezing.
Anybody Asus P5B Deluxe Core2 duo succsseful work....
Please if anybody have succsseful combination with Asus P5B Deluxe and Core2Duo please help and tell tips what is your other hardware,drivers about graphic,ram etc.....
I can not make this PC to work good with pulsar2 and SRB1[I can not in any case with or without SRB1}....
I can not make this PC to work good with pulsar2 and SRB1[I can not in any case with or without SRB1}....
Sharing a slot doesn't necessarily mean there will be a 'conflict' listed. Slots sharing may not be something detectable in windows ACPI mode, since it 'steers' things onto virtual addresses, hiding the sharing from your view. This works in theory with most things, but certain devices (such as our scope cards) are not consumer oriented printers, cameras and addon cards. They're pci bus bandwidth hogs and they don't like to wait around on other PCI devices that can steal their interrupt calls.
Switching to Standard PC is just an easy way to 'see' what is shared. In today's computing world you enough functionality working in this mode that it's pointless do to. Especially with the emergence of multiple cores, you don't want to rely on an outdated option in NT's architecture (you will probably lose a core struggly trying to get it to do 'Multiprocessing PC'). All you're really doing in Standard PC is revealing the actual physical addressing, and since there are other environments tnat you can easily boot into (Cd, USB, Floppy etc) that can reveal the same information and help you juggle your cards around to find an unshared slot.... I think the latter is the best method. THen once you're back in an ACPI supported mode (booted back into youir regular windows) things will work much more smoothly, take my word on it.
However part of the equation here is your motherboard:
http://www.asus.com/products4.aspx?mode ... =11&l3=307
Let's see, there's an additional SATA chipset on the motherboard (JMicron) which might cause issues, especially if in RAID mode. There's 'onboard 6 channel audio with spdif', onboard firewire, gaming features for the PCIe chipset....TWO onboard gigabit lan ports (you only need one and gigabit is a pci bus swamper so it is worth noting where this is connected to the chipset) and how many usb controllers? Oh btw all that fancy onboard cooling that the P5B comes with will need ACPI, I doubt Asus has tuned that system to be compatible with the older hardware monitoring support you have to use with 'standard pc' mode.
So what you need to do first is disable unnecessary onboard devices. The gigabit adaptors, onboard sound etc would all be early suspects on my list if that was my board.
Switching to Standard PC is just an easy way to 'see' what is shared. In today's computing world you enough functionality working in this mode that it's pointless do to. Especially with the emergence of multiple cores, you don't want to rely on an outdated option in NT's architecture (you will probably lose a core struggly trying to get it to do 'Multiprocessing PC'). All you're really doing in Standard PC is revealing the actual physical addressing, and since there are other environments tnat you can easily boot into (Cd, USB, Floppy etc) that can reveal the same information and help you juggle your cards around to find an unshared slot.... I think the latter is the best method. THen once you're back in an ACPI supported mode (booted back into youir regular windows) things will work much more smoothly, take my word on it.
However part of the equation here is your motherboard:
http://www.asus.com/products4.aspx?mode ... =11&l3=307
Let's see, there's an additional SATA chipset on the motherboard (JMicron) which might cause issues, especially if in RAID mode. There's 'onboard 6 channel audio with spdif', onboard firewire, gaming features for the PCIe chipset....TWO onboard gigabit lan ports (you only need one and gigabit is a pci bus swamper so it is worth noting where this is connected to the chipset) and how many usb controllers? Oh btw all that fancy onboard cooling that the P5B comes with will need ACPI, I doubt Asus has tuned that system to be compatible with the older hardware monitoring support you have to use with 'standard pc' mode.
So what you need to do first is disable unnecessary onboard devices. The gigabit adaptors, onboard sound etc would all be early suspects on my list if that was my board.