H E L P 2.01 - 3 - 3.01 Update 'hell'

Chadwick · Post by **Chadwick** » Thu Jan 03, 2002 4:01 pm

Hi,
As I want to try John Bowen's Prophet, I'm trying to update from my (previously) reliable version V2.01 to V3.01.
For some reason I thought that because V3 install resided in a different directory, I would end up with a choice of which version of Pulsar I run (2.01 or 3.01), so I figured my 2.01 install was safe if the 3.01 went whacko. I was clearly mistaken.

Having downloaded all the requisite files I installed V3.
Upon reboot I got the following error message:

Installation Error:
Program and driver do not match - this version of the program requires driver version 1.50.0.

Assuming that I had done nothing wrong, and maybe this error was one reason for the existence of the 3.01 update, I installed 3.01 - only to get the same error on reboot.

Paul from CW has made a prompt reply to my call for help and suggested I copy the V3 Win9x drivers into the V2 driver folder, but what I've done has made no difference.

The way I installed was pretty straightforward, so I wouldn't be surprised to hear that several people have had the same experience.

Anyone got a solution? Right now I have an audio PC without audio, so rather than work, I'm off to mow the lawn

Cheers
Rick

LHong · Post by **LHong** » Thu Jan 03, 2002 5:15 pm

Chadwick,
Sorry to hear that:
>>>Installation Error:
Program and driver do not match - this version of the program requires driver version 1.50.0.<<<
I'm not sure where is the problem, but it could be 75% of changed that you have got some corrupted data durring the downloaded or uncompressed process. I hate to tell you that you might re-download it! Here is what I would do as follows:
1> Redo the un-compress files, don't forget that they should be placed in same folder. Then run the new setup (clean un-installed). If it is same behavior, to do the (2)
2> Comparing the file's size from where to download (Creamware?), you might only need to re-download the mis-matched files ONLY. If still seeing no problems, sorry that you might need to re-download them all.

Good lucks,
Long

[ This Message was edited by: LHong on 2002-01-03 17:26 ]

Chadwick · Post by **Chadwick** » Thu Jan 03, 2002 5:26 pm

LHong,

Thanks. I've tried all that, including two separate downloads. Paul has sent me a second email re copying a file called sim.dll from the p3 to p2 directory.

I've uinstalled V3.01 again. Let's hope the third install and these file moves does the trick. (yawn)

LHong · Post by **LHong** » Thu Jan 03, 2002 5:30 pm

Just try to make sure that you have the V3.00 installed sucessfully before V3.01?

JoeKa · Post by **JoeKa** » Thu Jan 03, 2002 6:15 pm

You should first update to the newer drivers in your windows´ hardwaremanager, then install the software. This is the right sequence of the process and your problems should end...
It might be sensible to remove the older drivers before, but this should not be urgently neccessary.
I don´t really think your software package was corrupted.
Good luck!

Chadwick · Post by **Chadwick** » Thu Jan 03, 2002 6:16 pm

Thanks LHong, but the thing is: the V3.0 install suffers the same basic problem (whatever that is).

I've downloaded from Creamware twice, and once from Infinte Vortex.

I've installed and uninstalled three times.

I've copied driver files from the V3 folder to the Pulsar folder.

I've copied the sim.dll file from V3 to Pulsar (but it looks like the file was already there - same day creation, same size)

I took John Cooper's generous advice and used Windows' driver update routine to update the drivers by pointing it at the Win9x driver folder.

My error message has changed to:
'Cannot start software because board(s) or driver not properly installed. Please check installation.

Followed by:
Could not gain access to Creamware hardware!

Don't know what else I can do.

Paul from CW is keeping in touch, but he sounds incredibly busy (hundreds of emails).

Chadwick · Post by **Chadwick** » Thu Jan 03, 2002 6:20 pm

Hey Joe
How do I "first update to the newer drivers in your windows´ hardwaremanager"?

Is this pretty much what I did with John's advice?

I didn't delete any drivers before the update, because I was hoping to be able to run 2.01 and 3.01 alternately.

Silly me thought that if 3.01 was buggy, I might have to fall back to 2.01.

Kind of funny that I can't even get that far, and now 2.01 is dead as well....

JoeKa · Post by **JoeKa** » Thu Jan 03, 2002 6:35 pm

Well, your answer came just at the same time with mine...

Have you tried to completely remove all Pulsarsoftware&drivers, then reboot, install drivers, reboot, install software, reboot, install your extra-plugs? If not, try!
I also had my share of troubles after the update, but no more now.

Chadwick · Post by **Chadwick** » Thu Jan 03, 2002 6:42 pm

I was REALLY hoping to avoid that.

Actually, my Pulsar disk is in the studio, about twenty minutes away. I was hoping to avoid the drive (apart from completely uininstalling Pulsar, which seems extreme).

Thanks for the advice - I'll hang out for another answer from Paul, then bite the bullet.

LHong · Post by **LHong** » Thu Jan 03, 2002 6:52 pm

Chadwick,
>>>I've installed and uninstalled three times.
I've copied driver files from the V3 folder to the Pulsar folder.<<<

I think your windows registry is messy now!
Ok, one possibility is maybe that you forgot to do very "CLEAN Un-installed", regardless of how many times to re-install, the problems still be there! (make sure you were going through the User-Manual about un-installing process, there are some manually remove files and drivers, just double check it!). Don't forget to backup your Pulsar project and Pulsar Device folders.

Good lucks,

[ This Message was edited by: LHong on 2002-01-03 19:09 ]

marcuspocus · Post by **marcuspocus** » Thu Jan 03, 2002 9:40 pm

Go in devices manager, DELETE the drivers for Pulsar by clicking on it, then selecting REMOVE from the button below.

Then reboot, when asked to reinstall driver, CANCEL !!! (you don't want windows to reinstall the old driver from registry)

Then go again in devices manager, double-click on the yellow questionmark (this should be the Pulsar card with no driver), then install, using the second option (selection from a list i think), then choose 'Sound card & game devices', choose again to locate them yourself, go into the directory where you uncompressed the Pulsar v3.01 software, go in the 'driverwin2k' or 'driverwin9x' depending on your OS.

REBOOT AGAIN

THEN reinstall Pulsar v3.0, REBOOT AGAIN

if the background project start, close it BEFORE next step

THEN reinstall Pulsar v3.01

[ This Message was edited by: marcuspocus on 2002-01-03 21:43 ]

Post by **garyb** » Thu Jan 03, 2002 10:37 pm

the sequence marcuspocus described is correct.it should work.the readme mentions that the v3 driver must be installed to run v3.likewise v2 driver for v2.

Chadwick · Post by **Chadwick** » Fri Jan 04, 2002 4:20 am

Thanks heaps guys,

I initially gave up, as I'd promised Paul@CW that I'd wait for his advice, and went off to see Lord of the Rings with the kids.

When I saw what Peter Jasckson could do with a bit of Kiwi countryside, I figured it was embarrassing that I couldn't even install a patch update.

So I took your advice, noticed that the Pulsar card driver section of Device Manager was complaining about missing files, and pointed it to the V3 drivers again. This time - for the first time - Windows did the 'building driver database' thing, and when the machine rebooted, Pulsar ran - and I've been editing audio happily for the last hour and a half!!!

I must say, though, that I think the install setup is pretty crude and messy. I would have thought it would be no big deal to get the V3 installer to look at your old V2 background project and supply a V3 copy of it as the default project when you start Pulsar V3, but no - you get a bunch of disconnected pads and no mixer. A bit 'close enough is good enough' for me.

Regardless, I just want to say thanks to you guys for your help, and have a good New Year!

BTW How do I switch from 3.01 to 2.01 and back again?

JoeKa · Post by **JoeKa** » Fri Jan 04, 2002 5:01 am

switching between V2 and V3 is not possible on a single system because of the different drivers...
But once V3 is running, there´s no need for V2 anymore, I´d say.
Have phun editing and using the new stuff!

dbmac · Post by **dbmac** » Fri Jan 04, 2002 7:11 am

You can run Pulsar v2.01 and 3.01 on the same system. It's a very convenient way to compare setups while you establish all your plugins and other extra stuff in your new system. Lots of us used that facility, and there's many posts in this forum on the topic. If I remember, it requires copying the file sim.dll from v3 (app/bin directory) into v2. Make sure the v3 background project is closed before starting v2.
/dave

LHong · Post by **LHong** » Fri Jan 04, 2002 1:03 pm

>>>BTW How do I switch from 3.01 to 2.01 and back again?<<<
Don't bother the V2.01, try to enjoy the new V3.01x for a while! Unless you really have much troubles on the V3. There is a way but not reliable! There would be some windows-registry issues!

TIP: You could open the V2-project in V3's environment without loosing the connections, such as mixers and other devices (can be done). To do this, you must do another CLEAN installation for the V3 in same V2 sub-Directory pathes, where it was (D:pulsarV2, for example). So, this way, you always have your pulsar projects in backward compatibility (copy the old stuffs over). Don't forget, to do the entire backup. However, later you will need to replace all new devices (new version) as possible to avoid any unfortunately incompatibility problems??? This also be recommended by Creamware.
Have fun, Chadwick.
Long

[ This Message was edited by: LHong on 2002-01-04 13:09 ]