PlanetZ forums - scopeusers.com

Hello,

During installation of the Scope 4.0 software (completely new installation, no previous versions on this PC) for my Pulsar 1 card, I experience the followong problems:

1.) When installing the driver, Windows XP tells me the driver is not certified. When I click the driver is installed. About 15 seconds after that, the PC is completely blocked. I use the Win2K driver as supplied with both the Scope 4.0 and Scope 4.5 packages.
After restarting the machine, sometimes the machine hangs and sometimes it starts up with the Scope installation program. The Scope installation program tells me that the installed driver is not valid for use.

2.) When I disable the driver through to get the Scope Platform installed anyway, the installation package asks me for the Scope Registry Keys. I use the Scope Keyset as received from the support center. No matter which type of installation I use (Home, Scope M, Scope S, Professional) the keyset simply won't be accepted, without any messages whatsoever.

Since I've redone the installation at least a dozen times, I'm getting a bit annoyed
Therefore I kindly ask for your assistance and expertise in solving the abovementioned problems.

Cheers

the driver not being certified is perfectly ok! lot's of hardware from even major manufacturers has hardware drivers that are not certified. the certification process is expensive and silly. if you choose "continue anyway" and the machine stops working, you have another problem. the lack of certification will NOT make problems in ANY way....

there is no point disabling the driver to install the software. the card is worthless without the driver and , if the card is installed fully into the slot and the pc is not broken somewhere else, the driver MUST install. yes, it should be the win2k driver.

just trash the scope folder from the aborted install and the installer will work. in some circumstances when there is already a scope folder from a bad install, the installer won't accpt keys. removing the scope.rgy file(and the cset.ini for good measure) will fix that, i believe. you can also rename the current scope folder to "xxx" or something else that works for you, install scope into a fresh directory and then copy over any custom files/folders(like presets, dsp, vxd and devices) if you are repairing an old previously good install......