pulsar2 win 2k driver
-
- Posts: 32
- Joined: Wed May 23, 2001 4:00 pm
just show patience
they wanted to upload the public beta at the begin of this month, but ingo raven said that there have been unexpected problems (and don´t think, they´d tell us, which ones
)
so i´d guess, it´s again a few weeks. no problem for me.
have fun (at least with win9x
)
Mo
<font size=-1>[ This Message was edited by: Mo on 2001-07-05 10:18 ]</font>

they wanted to upload the public beta at the begin of this month, but ingo raven said that there have been unexpected problems (and don´t think, they´d tell us, which ones

so i´d guess, it´s again a few weeks. no problem for me.
have fun (at least with win9x

Mo
<font size=-1>[ This Message was edited by: Mo on 2001-07-05 10:18 ]</font>
http://www.creamware.de/en/download/sof ... efault.asp
Download the beta and go do some beta testing you guys... I'll be over in Win9x land making music until Logic comes out under 2000, and my MOTU driver comes out of BETA
Well actually I'll be testing Win2k too on another machine 
Download the beta and go do some beta testing you guys... I'll be over in Win9x land making music until Logic comes out under 2000, and my MOTU driver comes out of BETA


issues with Pulsar2k beta
so far, I only have a bluescreen problem, when closing a project containing a STS5000.
The Timeworks EZVerb had to be installed manually, the Timeworks Installer doesn't seem to work with W2k. I just copied the dsp's and the dev to W2k. It works!
The STS5000 seems to work pretty well though, despite the readme-warnings concerning time-stretch functionality.
I found my sts stretch'n time pretty well...
(up to factor +/-6)
Also, I did the PCI-related change to "Standalone PC" (oh man, what a thrill to install all drivers again..) as recommended in the readme.
Has anybody some info on this "Standalone PC" setting (see the Pulsar2kbeta Readme) ?
What is it, in technical terms..?
<font size=-1>[ This Message was edited by: jw on 2001-07-29 02:55 ]</font>
so far, I only have a bluescreen problem, when closing a project containing a STS5000.
The Timeworks EZVerb had to be installed manually, the Timeworks Installer doesn't seem to work with W2k. I just copied the dsp's and the dev to W2k. It works!
The STS5000 seems to work pretty well though, despite the readme-warnings concerning time-stretch functionality.
I found my sts stretch'n time pretty well...
(up to factor +/-6)
Also, I did the PCI-related change to "Standalone PC" (oh man, what a thrill to install all drivers again..) as recommended in the readme.
Has anybody some info on this "Standalone PC" setting (see the Pulsar2kbeta Readme) ?
What is it, in technical terms..?
<font size=-1>[ This Message was edited by: jw on 2001-07-29 02:55 ]</font>
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
Hey, I also installed Pulsar W2K, and every thing seems to work fine for me, don't need more than one wave (window standard project), so this isn't an issue.
Take care people to backup your scope.rgy before installing !!! Cuz, after install, I had to copy back the scope.rgy since it did not updated this file correctly on first startup.
Well, I don't know if it's supposed to be like that, but I'm having trouble with midi, cannot setup midi correctly. Before in winME, in devices manager, when i'd click on Pulsar, i could set the number of midi port available for window, now this doesn't exists no more.
And for the 'Standard PC' hack, it worked, but it's scared me as hell since all window devices were re-detected and re-installed, and couple of them installed twice (cd-rom especially), i had to go into devices manager again and delete all double entries.
I was used to have the little 'Windows Pulsar Mixer' available at <url>http://members.tripod.de/blueflameman/p ... ix14b.html </url>, but it doesn't work in win2k at all.
Other than a couple error windows pops up once in a while, when starting or closing the Pulsar soft, but seem pretty stable.
Can't wait now for Pulsar v3.0!!! I've completly removed WinME, and installed W2K exclusivly for Pulsar+Luna+Logic+Reaktor.
In conclusion, IT WAS ABOUT TIME WE HAD W2K DRIVERS !!!!!

<font size=-1>[ This Message was edited by: marcuspocus on 2001-07-28 12:01 ]</font>
Take care people to backup your scope.rgy before installing !!! Cuz, after install, I had to copy back the scope.rgy since it did not updated this file correctly on first startup.
Well, I don't know if it's supposed to be like that, but I'm having trouble with midi, cannot setup midi correctly. Before in winME, in devices manager, when i'd click on Pulsar, i could set the number of midi port available for window, now this doesn't exists no more.
And for the 'Standard PC' hack, it worked, but it's scared me as hell since all window devices were re-detected and re-installed, and couple of them installed twice (cd-rom especially), i had to go into devices manager again and delete all double entries.
I was used to have the little 'Windows Pulsar Mixer' available at <url>http://members.tripod.de/blueflameman/p ... ix14b.html </url>, but it doesn't work in win2k at all.
Other than a couple error windows pops up once in a while, when starting or closing the Pulsar soft, but seem pretty stable.
Can't wait now for Pulsar v3.0!!! I've completly removed WinME, and installed W2K exclusivly for Pulsar+Luna+Logic+Reaktor.
In conclusion, IT WAS ABOUT TIME WE HAD W2K DRIVERS !!!!!


<font size=-1>[ This Message was edited by: marcuspocus on 2001-07-28 12:01 ]</font>
to your question, jw: NT uses a kernel, like any other serious os (MS calls it Hardware Abstraction Layer = HAL). There is one with the ability for ACPI powermanagement, installed whenever the mainboard is capable. The Standard PC setting does not contain this. Anyway, main reason for CW to recommend the standard kernel is that this one does not share IRQs. The ACPI kernel has all devices usually with IRQ 9. If you change the kernel to standard all devices that do not use IRQ 9 have to be reinstalled with their appropriate IRQs.
Happy pulsaring
Micha
Happy pulsaring
Micha