Help! Cubase protection dongle - impossible to get it recognized

Bad Disciple

New member
Hi folks and help !!

I've reformatted and re-installed my old but good laptop with Windows XP Pro
and re-installed Cubase SX3 which I always had on it before. This time it just
DOESN'T want to recognize the protection USB dongle! The drivers get installed,
then Cubase gets installed, but when I plug the dongle it goes "found new hardware"
and... it stays there endlessly and freezing the whole system. I tried all different ways.
Antivirus Kaspersky disabled, enabled, in trusted zone, re-installing protection drivers...
I wonder maybe it's because this time I installed Windows XP with SP3, while
in the past it always had SP2.

I need Cubase on my old laptop for additional work. Before the re-formatting
it worked perfectly since ever, now it's a damn mystery...

It has Intel Dual Core 2Ghz, 4MB L2 cache; 2GB DDR2; 320GB HDD partitioned.

Any feedback would be welcome.
Thanks.

BD
 
No I didn't, but I never needed to do that before on that machine.
But I thought of another reason, I recalled that the dongle fell on the (stone) floor few days ago,
and I'm suspecting that it might have been physically damaged after this...
I wonder could that have happened?...
 
Hi back all, and thanks for your feedback. Still...
I downloaded eLicenser and tried to install it but it asks Microsoft's Net.Framework version 2.0
which I also downloaded and when trying to install it it says "can't read database"...
I mean it's a total mess of a puzzle. I'm really fed up...
Any ideas please ?

BD
 
You need to get that MS Net.Framework installed before you can install eLicenser.

Try installing a later version of Net.Framework - like version 3.0 - and then try install eLicenser again.

Cheers :)
 
Hail folks and a-yeyah !
This helped! I first installed .Net framework 3.5.
Then I downloaded the needed Windows updates for it.
Then I installed the eLicenser.
And... wiyonnng! It worked!
I don't know why I never had that problem in the past (before reformatting my machine)
or it might be the SP3 which I installed this time while it was SP2 before.
Anyway, it's ok and great thanks to all of you. I was stuck with that problem for days.
So be blessed...
 
Back
Top