THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 03/09/2009 at 09:32, xxxxxxxx wrote:
Cinema 4D Version:
This is probably a silly question, but where does WritePluginInfo() actually write to? The reason I'm asking is that I am currently working on the user serial number functions and I've successfully 'registered' the plugin on my development machine.
What I'd like to do is 'un-register' it so I can try some more options in the code. But how can I do that? Does it write to the Cinema 4D.prf file (I'm a bit reluctant to try deleting that just in case something goes wrong!).
On 03/09/2009 at 23:36, xxxxxxxx wrote:
Afaik on Windows this goes into the registry and on OSX into the user preference *.mcd files.
On 04/09/2009 at 02:20, xxxxxxxx wrote:
Ah, thanks - that seems logical. I don't suppose you would know exactly where in the registry? I've searched for the plugin ID but if that is stored encrypted then that's why I can't find it. It isn't in the main Maxon part of HKEY_LOCAL_MACHINE, that just stores the installation path.
Would the developers know (if it isn't kept confidential of course)?
On 04/09/2009 at 02:30, xxxxxxxx wrote:
It's located under HKEY_CURRENT_USER/Software/MC4D.
On 04/09/2009 at 05:58, xxxxxxxx wrote:
Aha! I was able to find it thanks to that info, thank you. On this machine, it's actually in HKEY_LOCAL_MACHINE/Software/MC4D. It probably ought to be in HKEY_CURRENT_USER, but it isn't here.
Fortunately it's easy to recognise the correct key because the key name contains the plugin ID, so I can delete it and make the plugin 'unregistered' again.
Many thanks for your help.
On 05/09/2009 at 10:29, xxxxxxxx wrote:
this raises a question now for me:
What happens if a user has multiple copies of c4d with different serials installed on his system (for example R10 and R11). As serials seem to be stored by the plugin id, this seems to imply there can always only be one plugin serial in the registry ..
One of my users has problems to make R11.5 accept the plugin serial, whereas it works in R11 (he has these two installed seperately). Which is quite strange, as the plugin serial is the same for R11 and R11.5.
It looks like R11.5 cannot save my plugin serial with writePluginInfo ..
On 06/09/2009 at 01:58, xxxxxxxx wrote:
I'm only guessing here, because I've only got one version (11.0) of Cinema on this machine, but looking at the registry keys they all start with the string 'plINI110_' followed by the plugin ID.
So maybe in 11.5 the prefix would be 'plINI115_'. Like I say, it's just a guess at the moment, but that would allow multiple serials for the same plugin.
On 07/09/2009 at 03:49, xxxxxxxx wrote:
Indeed, the registry entries are prefixed like this "plIN110_". Thus each Cinema version knows which entry to load. But this is only true for major releases (R10, R11). There is no "plIN105_" or "plIN115_". Point releases will load the plugin entries of the last major release.
On 07/09/2009 at 04:17, xxxxxxxx wrote:
That's interesting. Does that mean then, that when you call GeGetSerialInfo() it returns in the SerialInfo structure the serial number of the major version even if you're running a point version? In other words, if you are running 11.5 will the function return the serial number for 11.0?
That's quite important because it would mean that there is no need to issue new SNs for plugins for point versions, just major versions.
On 07/09/2009 at 06:15, xxxxxxxx wrote:
Yes, the serial number is the same for R11 and R11.5. With point releases the customer gets an additional serial number. Basically this is an module number. In other words your customers don't need new plugin serials with point releases.
On 07/09/2009 at 07:01, xxxxxxxx wrote:
Excellent, thank you!