Hide TurboActivate.dll and TurboActivate.dat

Hi Sam/Wyday,

I know that licensing can't stop some people for piracy, But deploy many applications that always come with TurboActivate.* files simply make the target so obvious..

Is it possible or feasible to hide its identity?

- Able to use different name for TurboActivate.dll, ie. Cryptic.dll- Able to alter version/company/appname/etc for Cryptic.dll (is it against your copyright?)- Able to embed/build TurboActivate.dat into DLL or excutable, since this file is always bound to specific Product.

Thanks,w2xl

We have static libraries (libraries that you can build into your C/C++ app). So that takes care of TurboActivate.dll. As far as TurboActivate.dat -- you can name that whatever you want (e.g. FunnyCatPictures.jpg) but you have to use PDetsFromPath() before calling any other TurboActivate function.

Hi Sam,

Thanks for your reply, which is very helpful. I'm now OK with the approach for TurboActivate.dat. As of static library, it's a great way but not easy for users without VC++ environment, especially for .Net developers. What I asked is something like current TurboActivate.dll being able to refer itself properly when its name is changed to cryptic.dll.

I tried to rename all "TurboActivate.dll" reference in the VB.NET sample code, and renamed the actual dll. The test shows it's somehow still trying to find TurboActivate.dll...

Thanks,w2xl

You can name the TurboActivate.dll whatever you want. Rename all instances of TurboActivate.dll in the TurboActivate.vb file.

The only caveat is that you won't be able to use the TurboActivate wizard (TurboActivate.exe).

OK, I was able to rename TurboActivate.dll to something else. I didn't realize that the sample code uses TurboActivate.exe that actually relies on TurboActivate.dll. Without using TurboActivate.exe in my code, everything is good. 🤣

Reply
Discard post