SOLVED: Com Plugin stange issue across host versions
Posted: Wed Oct 30, 2013 5:49 pm
Hi everyone.
VMProtect Demo newbie here.
I am protecting a dll that is a plug-in for a 3rd party host application
I have many versions of the 3rd party host application on my disk.
I put my serial.txt in c:\ and am fetching it from that location like so.
char *serial = read_serial((char*)"c:\\serial.txt");
I am not linking with the 3rd party application in any way but my license only
works with the version of the host application that I was using as I waded through the
license system help instructions. in that instance, VMProtectSetSerialNumber(serial) returns
0 as expected
If I run the same protected plugin in a different version of the 3rd party host application
VMProtectSetSerialNumber(serial) returns 2!
I can step through the code, see it open c:\serial.txt just fine.
It it as if somehow some way VMProtect has host app version or otherwise in the serial.
I checked only username and email for protection options as described in the help.
Why might this be happening?
My protected plugin must work under many versions of the host application that are out there in the wild.
:Ron
VMProtect Demo newbie here.
I am protecting a dll that is a plug-in for a 3rd party host application
I have many versions of the 3rd party host application on my disk.
I put my serial.txt in c:\ and am fetching it from that location like so.
char *serial = read_serial((char*)"c:\\serial.txt");
I am not linking with the 3rd party application in any way but my license only
works with the version of the host application that I was using as I waded through the
license system help instructions. in that instance, VMProtectSetSerialNumber(serial) returns
0 as expected
If I run the same protected plugin in a different version of the 3rd party host application
VMProtectSetSerialNumber(serial) returns 2!
I can step through the code, see it open c:\serial.txt just fine.
It it as if somehow some way VMProtect has host app version or otherwise in the serial.
I checked only username and email for protection options as described in the help.
Why might this be happening?
My protected plugin must work under many versions of the host application that are out there in the wild.
:Ron