PlanetZ forums - scopeusers.com

You know it would be very easy to pass the path as a variable and call this batchfile from SC's installer, so that every install completed with this step (hint to SC at a quick fix), or even just run their own file attribute & permissions check after the rest of the install finishes. Of course the right approach would be either to look at where the file interactions are getting out of step (outdated libs for file ops?) but since this issue has persisted forever...

I don't think that this 'copy protection violation' message is always or purely related to a messed up install though Valis. I get this message occasionally while building something in the sdk. It just appears for no apparent reason other than possibly dsp distribution going t*ts up. A restart of the sdk usually fixes the issue.

Tried the batchfile.Still no worky....
Ralf will send me another keyfile,i hope that will fix it.
Any other suggestions?

Shroomz~> wrote:I don't think that this 'copy protection violation' message is always or purely related to a messed up install though Valis. I get this message occasionally while building something in the sdk. It just appears for no apparent reason other than possibly dsp distribution going t*ts up. A restart of the sdk usually fixes the issue.

I skipped to the second page and just saw the batchfile, and replied to that alone. I didn't have time to read the whole thread, sorry!

I haven't actually had prompts for copy protection issues unless I was missing a key or Scope was confused about board id's.

according to reports (long ago) these messages sometimes used to popup related to multiprocessor systems and virus protection software in the past...

cheers, Tom

Thanks for the tips so far.I am going to uninstall antivir.
Wiered thing is that the system worked fine with 3 cards before.Could something in the cset ini be really messed up?
Its a P4 2.8 with 2 gb ram..never had that before and somehow i doubt that the new keyfile (havent recieved it yet) will help much

you probably have 2 1GB memory modules - remove one
if nothing changes - replace with the one removed
if nothing changes - oops

is there anything else you have changed between the time the system was running and CP messages appeared ?
OS updates ?

cheers, Tom

Ok i write exactly what i did.
Opened pc and pulled out old p1>closed pc and checked if i got the right one out(plugs etc) Everything was working as expected showing 10 dsps.
waited for the scope pro.
Scope pro arrived>opened pc,pulled out both cards Pulsar 2 was in pci slot 3 pulsar 1 was in slot 2.Reseated Pulsar 1 in slot 3 Pulsar 2 in slot 2 scope pro in slot 1.
Started pc,found new hardware aka pulsar 2 and scope pro.Installed drivers all looks good.
Started sfp showed 25 dsps as expected all cards are on different irqs nothing shared.
edited cset to show the scope pro srb as first card then p2 then p1.
Old projekts load fine no problems as before with 14 dsps.Have almost double the power now.
then as the copyright window kept popping up while pulling in plugs from the mix n master package(scope pro) i pulled out the scope pro and the p2 and exchanged pci slots.Scope pro in middle slot 2 and pulsar in slot 1.
Still getting that error.
both stdm cables are well seated first stdm connects all cards second stdm only scope pro and p2.
The system can load 12 masterverbs as to 10 before.
Its 2 gb of ocz platinum and memtest showing no errors.
Do you think i still should pull out 1 stick?I also have ht on as it was running perfect with 3 cards before and..its kinda running perfect now too except the plugin issue...
under registry in sfp i see all keys but its still asking for em and gives the error.I can select the p2 when it asks for keys and its the same error but its also showing import sucsess....
I am pretty much out of ideas now.
I will try to deinstall antivir as the pc isnt connected to the internet at all.
then i maybe take out aq stick of ram and disable ht but somehow i doubt that its going to help BUT thank you for that tip..didnt thought of that.

Uninstalled anti vir and spybot...disabled unused ports etc..uninstalled all 3 cards and reinstalled...NOTHING WORKS...And honestly its starting to PISS me off.
I am really close to uninstall everything clean all reg edits and start again but i have the feeling that it wont solve it..MEH..what a stupid error..grrrrrr

Here is my cset.ini
http://www.yousendit.com/download/Y2ovV ... cFUwTVE9PQ

I was putting it out of the folder and it created a new one but it messed up everything:P including cant start scope hardware error 0001....

I think i wait for the new keyfile as i can only guess now...i maybe need to do a complete un/reinstall.

stardust wrote:cset.ini looks very similar to mine (including cubase vst folder )

there was a hint in the printed manual that in case the blocksize is too small it could crash.
256 is not small. But setting it higher might be worth a try....

What do you suggest? 512? I mean it doesnt crash...just that copy right violation error..its driving me NUTS.
Thanks for the tip i will try it tomorrow or maybe later..i cant be arsed with that right now...

...edited cset to show the scope pro srb as first card then p2 then p1...
an srb as the 'main' card isn't a good idea imho
there even is software that won't run at all if there is only an IO-less card
this doesn't exactly apply as you have cards with IO, but there is a performance penalty
I'd mount the P2 IO board to the SRB, it's an easy operation

it's been a while, but I remember I gave up the idea of adding a SRB to my Pulsar One once because there was some kind of trouble to be expected. My original motivation was to improve latency and the SRBs were the most affordable solution back then.

cheers, Tom

astroman wrote:...edited cset to show the scope pro srb as first card then p2 then p1...
an srb as the 'main' card isn't a good idea imho
there even is software that won't run at all if there is only an IO-less card
this doesn't exactly apply as you have cards with IO, but there is a performance penalty
I'd mount the P2 IO board to the SRB, it's an easy operation

it's been a while, but I remember I gave up the idea of adding a SRB to my Pulsar One once because there was some kind of trouble to be expected. My original motivation was to improve latency and the SRBs were the most affordable solution back then.

cheers, Tom

I will try that.I had the p2 as master before with the same results tho.Do you think mounting the i/o board on the srb could fix that?

I just remember a card with no IO as master isn't a good idea except in XTC mode ...

even if you use quality Ram it's worth verifying it's (real world!) operation, if you experience strange errors
a memory test doesn't necessarily detect such modules

anyway, you should be aware that the cp protection stuff isn't just a regular piece of code - such routines often deal with fairly exotic circumstances (no ideas about the details, tho)

cheers, Tom

astroman wrote:I just remember a card with no IO as master isn't a good idea except in XTC mode ...

even if you use quality Ram it's worth verifying it's (real world!) operation, if you experience strange errors
a memory test doesn't necessarily detect such modules

anyway, you should be aware that the cp protection stuff isn't just a regular piece of code - such routines often deal with fairly exotic circumstances (no ideas about the details, tho)

cheers, Tom

Hmm ok.Thanks tho..i guessed that is a pretty hard to fix error..i shall see tomorrow.

valis wrote:I haven't actually had prompts for copy protection issues unless I was missing a key or Scope was confused about board id's.

Board ID confusion was my first thought on this & it might still be the case, but I'm really not sure. I had this error message just last week in the sdk when dropping/moving a new circuit into the parent module of one of my previous projects (It's a fully/properly working stereo effect project that I'm using these days as a core for building effects).

astroman wrote:according to reports (long ago) these messages sometimes used to popup related to multiprocessor systems and virus protection software in the past...

cheers, Tom

As mentioned, I get these messages occasionally on our main Scope/SDK system, but there's no virus protection software on there & it's not a multiprocessor system.

Shroomz~> wrote:

astroman wrote:according to reports (long ago) these messages sometimes used to popup related to multiprocessor systems and virus protection software in the past...

cheers, Tom

As mentioned, I get these messages occasionally on our main Scope/SDK system, but there's no virus protection software on there & it's not a multiprocessor system.

Hmm i try to turn ht off in the bios.
If that doesnt work i completly uninstall scope remove the cards clean the reg then add 1 card after another..i think i messed something up by switching slots and adding the pro srb at once..maybe not that good idea todo that.
But..BUT what if that still does not fix it..thats what scares me a little...

Didnt worked..oh well,will have a busy afternoon tomorrow

I decided to wait for the keyfile.If that doesnt fix it i will uninstall everything.
No idea tho why it still happens,i try to turn off xtc mode later but i am already just shooting in the dark.
Thanks for all the help tho i keep you posted here.

If anyone has more ideas:p Please chime in,gary maybe?
Very thankfull for any bits of help.