TTProtect - ttprotect.com

     The added dlls will be embeded into the target application.The dlls will be never written to disk.

Support GetModuleFileName

     If this option is enabled, the GetModuleFileName API can be used. The return is the virtual Path of dll. Only when the applications need to use GetModuleFileName to get the path of dll, this option must be enabled. Otherwise don't enable this option.

Support LoadLibrary/GetModuleHandle

     If this option is enabled, dll can use LoadLibrary/GetModuleHandle API. Only when the application need use LoadLibrary/GetModuleHandle to find dll, then this option need be enabled. If the application need use GetProcAddress to locate dll export functions, please enable this option.  If the dll is refered by static links, don't enable this option.
    The dll must be called by file name without path. Otherwise the dll on the drive would be used instead of the dll in memory.
    For example: LoadLibrary("myname.dll") use the dll in memory. LoadLibrary("c:\\myname.dll") use the dll on the drive. Note that enable this option only when needed.

Note: "Support GetModuleFileName" and "Support LoadLibrary/GetModuleHandle" don't support Win9x.

Module Virtual Path

      The value of virtual path is the return of GetModuleFileName. Subdirectory can be empty. For example: Dll name is myname.dll. Main directory select "Windows Directory". Subdirectories is abc. If the "Windows Directory" is "c:\windows", then the return value of GetModuleFileName is "c:\windows\abc\myname.dll".

Super Process

      Encrypt the application with higher level. Detailed see "Protection Options" and "Advanced Options".
      If the dll has been encrypted, don't enable "super process" then the dll will load into memory without any encryption.