PlanetZ forums - scopeusers.com

1 time out of three or four Scope asks at startup some activation keys and I just load every time the sfk registry file to solve this.
Can someone detect the cause ?
Regards,
Dimitrios

poorly seated card?

dirty contacts? ever touched the contacts with fingers? it'll take 99% or better alchohol to clean them(or a contact cleaner like hexane).

Try the cleaning like garyb said. I was having some similar problems, it kept getting worse and it turns out I had to send my card for repair. Hopefully you don't have to do that.

might be related to dual core or hyperthreading - I've had that recently right out of the blue when I plugged 2 cards in a dual CPU machine.
Just to mention the possibility - not that i really believe in it - I didn't examine or try to track the source deeply.

cheers, Tom

Try the cleaning like garyb said. I was having some similar problems, it kept getting worse and it turns out I had to send my card for repair. Hopefully you don't have to do that.

I wonder if this is an early symptom of the creamware card going bad?

Jah Servant, did you ever get your card repaired? How long did it take you? I'm waiting to hear about what's going on with mine....

My pulsar 1 card has been doing that for a year now, every 3 or 4 times asking for the key, I now have the key permantly on my desktop so I can import it straight in! maybe its time to clean the contacts then!

(thats on a hyperthread PC - oh yes btw Martin Walker the PC man at sound on sound magazine reckons pulsar should work fine with hyperthreading, but I seem to find it doesnt)

I've had that same problem with my PowerPulsar which has been sent for repair since it eventually decided to not let me get passed through registration process. And yes my machine's running on HyperThreading with normal Windows XP installation...as in I let Microsoft do whatever necessary to get it installed, I know 'a bold leap of faith' hehehe.
I still have my old workforce the original Pulsar Plus & Pulsar SRB from 1999 or so. Nothing in my system has changed other than taking out PowerPulsar and all seems to work okay so far, even with HyperThreading. Of course, I haven't been able to test registration of plug-in's that have been registered to PowerPulsar HW/SN...we'll see about how that goes when I get my card back from CreamWare, hopefully sooner than later...didn't think I'd have such a withdrawal with DSP power.

But I must say HyperThreading has not been an issue with me yet. Can't confirm anything on dual-core though.

yeah, it's a bit confusing indeed - it seems to be related to specific releases of the old boards.
I have 3 Pulsar Ones and never had problems with my 'main card' which has all the keys to it.

The last card I bought for 50 bucks on eBay (no warranties, for DIY), so I took the opportunity to 'challenge' it a bit when I tested a HP Dual CPU workstation of which I wasn't sure if I should keep it.
Only then I noticed this behaviour to present the registration dialog, and it wasn't even for the Scope system software, but obviously for some trivial device (mixer or so) in the startup project.

cheers, Tom

hyperthreading definitely works with scope, but it can make problems and the advantages are minimal to none, so i always disable it.