Hi everyone--
I finally decided to make the jump from Win98SE to Windows XP in the hopes of getting better performance and the ability to use Cubase SX. Unfortunately, my Pulsar card seems hesistant to join me.
I downloaded the updated Scope Fusion installer for XP from the Creamware website and installed the latest Adaptec ASPI layer as recommended. After installing the Pulsar driver, my system froze immediately. I rebooted in safe mode, uninstalled the driver, rebooted in normal mode, and attempted to reinstall several more times using both the install program and directly through Windows Device Manager. Same results -- computer locks on bootup when the Pulsar drivers load.
Has anyone else experienced this kind of issue and solved it? I installed XP on a brand-new drive, so it's a clean install. I haven't yet tried to turn off other drivers and devices yet to see if there is a conflict -- I'm hoping there might be a simpler solution.
I didn't have any problems with the Pulsar in Win98, with all the same hardware that's in there now: two CD drives, an NVidia GEForce graphics card, and an older Asus motherboard with a Pentium III. Nothing fancy.
As for software, pretty standard stuff: Microsoft Office, Photoshop, Dreamweaver, Norton Systemworks, ZoneAlarm.
I'm stumped! Would appreciate any feedback.
Thanks,
David
Pulsar driver freezes Windows XP
Are you disabling Norton before install of Pulsar drivers?
I had this problem the first time I tried to use Pulsar on WXP, but after reinstall of XP all was well. I also experienced problems with Matrox and Pulsar conflicting ( don't know about Geforce). Try disabling antivirus, optimizing for audio (see tips and tricks section) and reinstalling graphics drivers after Pulsar drivers. Hope this helps as I'm not much of a tech head, butit worked for me.
I had this problem the first time I tried to use Pulsar on WXP, but after reinstall of XP all was well. I also experienced problems with Matrox and Pulsar conflicting ( don't know about Geforce). Try disabling antivirus, optimizing for audio (see tips and tricks section) and reinstalling graphics drivers after Pulsar drivers. Hope this helps as I'm not much of a tech head, butit worked for me.
"I downloaded the updated Scope Fusion installer for XP"
Where do you find this? I will also be making the jump to hyperspace here soon. Want to make sure I have all my ducks in order before I begin. Sounds like a lot of people have had installation problems. I assume these problems are all due to lack of understanding of the new OS? Or maybe just due to hardware conflicts? Well, I'll be doing this shortly. Will let you know what my results are like.
Where do you find this? I will also be making the jump to hyperspace here soon. Want to make sure I have all my ducks in order before I begin. Sounds like a lot of people have had installation problems. I assume these problems are all due to lack of understanding of the new OS? Or maybe just due to hardware conflicts? Well, I'll be doing this shortly. Will let you know what my results are like.
PROBLEM SOLVED!
But not easily. Way in the back of the Pulsar manual, there was a suggestion for XP users to set up XP so that it assigns IRQs based on the system BIOS, not on Windows' assignments. I thought this was a long shot, but sure enough, it worked. Not exactly clear why, as there were still other devices sharing the Pulsar's IRQ.
As for the location of the updated driver, go here:
http://www.creamware.de/en/download/sof ... 31c_pc.asp
This is a "universal" driver that supports many, if not all, of Creamware's products. You will need to register on their site, if you haven't already, in order to get the keyfile to unlock all the software. You'll need your card's serial number.
Creamware needs to improve their documentation! All this XP info should have been grouped together in the installation instructions! I spent probably 5-6 hours getting this working -- bad user experience.
--David
But not easily. Way in the back of the Pulsar manual, there was a suggestion for XP users to set up XP so that it assigns IRQs based on the system BIOS, not on Windows' assignments. I thought this was a long shot, but sure enough, it worked. Not exactly clear why, as there were still other devices sharing the Pulsar's IRQ.
As for the location of the updated driver, go here:
http://www.creamware.de/en/download/sof ... 31c_pc.asp
This is a "universal" driver that supports many, if not all, of Creamware's products. You will need to register on their site, if you haven't already, in order to get the keyfile to unlock all the software. You'll need your card's serial number.
Creamware needs to improve their documentation! All this XP info should have been grouped together in the installation instructions! I spent probably 5-6 hours getting this working -- bad user experience.
--David
Glad to hear you got it resolved. I still don't understand what you mean by updated driver though.
The link takes us right to the SFP download page where you can download the latest version of SFP, along with links to the Adaptec ASPI updates, etc.
Anyway, I'll remember this when I upgrade to XP in the coming days.
As far as the manual and documentation, I agree it's a bit funky in places. Still better than some user doc's I've seen. It tends to become a bit of a scavenger hunt to find everything you need but I suppose that's true for everyones software these days. Thankfully, that's why PlanetZ exists. The braintrust we have here is wonderful. If you run into any more problems/solutions, please let us know.
The link takes us right to the SFP download page where you can download the latest version of SFP, along with links to the Adaptec ASPI updates, etc.
Anyway, I'll remember this when I upgrade to XP in the coming days.
As far as the manual and documentation, I agree it's a bit funky in places. Still better than some user doc's I've seen. It tends to become a bit of a scavenger hunt to find everything you need but I suppose that's true for everyones software these days. Thankfully, that's why PlanetZ exists. The braintrust we have here is wonderful. If you run into any more problems/solutions, please let us know.