how do you copy and paste a V5 keyfile?

[irrelevance]

ok so the format for versions 5 seems a bit different and I'm having no luck copying and pasting so when the reg dialogue comes up I have to import for each device which under xtc is taking ages!!!

the file I have looks like: keyfile_XXXXXXXXX_XXXXXXXXX_XXXXXXXXX_(XXXXXXXXXXXX).v5

If I paste this into the dialogue and try and save it doesn't work.

[kylie]

ever tried to backup your scope.rgy (resp. its counterpart in v5 with a name I don't remember exactly) to a different location and copy your .v5 to that location (renamed of course)?
scope5 should be closed during that procedure.

[irrelevance]

Yeh I have backed up my keyfile before but I haven't been able to find the scope.rgy equivalent for v5.

[kylie]

Yeh I have backed up my keyfile before but I haven't been able to find the scope.rgy equivalent for v5.

there is one. just yesterday I copied mine over the existing one (0 byte in size). I just can't remember what it was named like. it's still in \scope\app\bin\

[irrelevance]

Ahh ok. So if I copy across the keyfile with the format I have indicated above and remove the keyfile.v5 file from the scope pci/app/bin folder do you think that would work?

[irrelevance]

Ok update. Deleted keyfile.v5 and replaced with my keyfile (format above). Doesn't make a difference. Everytime scope is launched a new keyfile.v5 is placed into bin folder anyway. tried renaming my keyfile to keyfile.v5 but no joy here. Isn't anybody else experiencing this behaviour?

[Fluxpod]

Have you opened the keyfile with as example the editor and choosed "always open with"? If so delete the file extension for windows and try again.Happened to me too one time...super annoying and i truely pulled my hair out till i got it.

[irrelevance]

Aha you have cracked it fluxpod! I wasn't sure how I was going to rename the file but I did a right click windows dialogue and chose properties and there was a message saying that "this file has come from another computer and is being blocked." I clicked the button to unblock and relaunched cubase and it found all the plugs straight away. So I didn't have to rename anything but this was a windows issue/annoyance.

[Fluxpod]

Ahhhh right! Had this one aswell.... Good that it works now.

[kylie]

nice. so the renaming "trick" did it, anyway..!?

[irrelevance]

No I didn't have to rename. It seems windows (xp) recognised that the file originated from another computer (sonic core) so decided to block access to it. I only found out when I right clicked and went into the file properties.

[kylie]

no, I just wanted to know if renaming the keyfile(xxxx_xxxx-xxxx....).v5 to (obviuosly it is) keyfile.v5 did it, after all.
I wonder if scope5 looks for any file with the .v5 extension and imports it during startup...

[irrelevance]

no, I just wanted to know if renaming the keyfile(xxxx_xxxx-xxxx....).v5 to (obviuosly it is) keyfile.v5 did it, after all.
I wonder if scope5 looks for any file with the .v5 extension and imports it during startup...

That didn't work. Posted this above:

Deleted keyfile.v5 and replaced with my keyfile (format above). Doesn't make a difference. Everytime scope is launched a new keyfile.v5 is placed into bin folder anyway. tried renaming my keyfile to keyfile.v5 but no joy here.

*When the file is renamed scope doesn't recognise it or at least it doesn't try and load it.

[kylie]

mh ok. but whenever you ended up with a new empty keyfile.v5, did you try to load a device and then imported your whatever-named keyfile?
I messed with a file once (merged 2 instances) and introduced a blank character at the end of one line. when I tried to add an activation key
this key was inserted every time I tried to load it, and I was was always asked for the key when trying to load. I had the line for the device
6 or 7 times in my keyfile, and still I could not load it. I had the idea there could have been something similar. well, I have my scope4 running on 2k,
and v5 on xp, but even when I completely reinstalled 2615 I just swapped the keyfile and it worked out of the box. what program did block file access?
xp itself? I can hardly imagine that...

[irrelevance]

mh ok. but whenever you ended up with a new empty keyfile.v5, did you try to load a device and then imported your whatever-named keyfile?

Yes but the only thing that would work was to import my keyfile every time

what program did block file access?
xp itself? I can hardly imagine that...

Neither could I but yes it was xp blocking the file.

A forum discussion on the topic:

http://episteme.arstechnica.com/groupee ... 3006938731

[kylie]

ah, it's ADS. never seen a problem with that, but then, I'm still on W2K...

I somehow suspected an AV scanner to be responsible, hence my disbelief...