Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ReFox
Message
From
04/09/2007 09:13:43
 
 
To
03/09/2007 14:04:37
General information
Forum:
Visual FoxPro
Category:
Third party products
Title:
Re: ReFox
Miscellaneous
Thread ID:
01251482
Message ID:
01252162
Views:
56
>>>>>What I dont like about Molebox is that you need to include all the VFP dll's in the package. Why can't I just Molebox my VFP exe only and leave the dll out of it.
>>>>
>>>>But you can! Personally I see no advantage by including the runtime DLLs. My setup contains them, of course, but as separate files. And they are also NOT encrypted by Molebox.
>>>>
>>>>You might download Clickwork, run the setup and see what it creates. Only the main exe and the apps are encrypted by Molebox.
>>>
>>>If I add just my VFP exe to the executable field and only the same exe to the package box then my app does not run. What am I missing about Molebox that you can Molebox only your VFP exe and not add any dll files to the package?
>>
>>In this text I explain how an application like Clickwork is ‘moleboxed’. It is currently done with Molebox 2.6.1.
>>
>>I chose for separate files for the main executable, the DLLs and the APPs. A distribution therefore contains the VFP-runtime DLLs, the main executable, various APPs and some other stuff. Such a type of configuration requires some basic principles:
>>
>>A DLL, EXE or APP can be either encrypted or not encrypted. (Consequently, an encrypted EXE can run an unencrypted APP.) If a file is encrypted, then it MUST use the very same key as the other encrypted files! (See the Master Key in Options.) Certain files, most notably the runtime DLLs, are not encrypted in my case. The main EXE and the APPs of Clickwork are encrypted, because they contain source code that I want to protect.
>>
>>The main EXE (as produced by Molebox) does not contain the DLLs and the APPs (in my configuration), but that main executable MUST know the NAMES of the other ENCRYPTED files! These names must have been specified in the ‘Packages List’, see button ‘Configure’. However, in order to prevent that they are included in the main executable, when choosing ‘Pack to Box’ you must only check the box of ‘Default Package (Executable)’.
>>
>>Although I could use another checkbox to only encrypt an APP here, I encrypt them in a different way. That is because they are general and not the property of a single application. They are in a separate place and I don’t want to start Clickwork’s configuration file (the mbxcfg file) merely to encrypt an APP. So, for encrypting a general APP I use a trick. In a separate folder I have created a dummy executable named Dummy_apps.exe and put a copy of the unencrypted APPs. Actually Dummy_apps.exe is a tiny text file. Do the same, select it as the Executable. In the Packages List (button Configure) all APPs should be added. When choosing ‘Pack to Box’ you only check the box of the APP that you want to (re)encrypt.
>>
>>This is the folder structure I use:
>>
>>U:\Molebox\Apps contains Dummy_apps.exe, the unencrypted general APPs and (created by Molebox) dummy_apps.exe.mbxcfg.
>>
>>U:\Molebox\Apps\Encrypted is the place I let Molebox create the encrypted general APPs (see ‘Pack to’).
>>
>>U:\Molebox\Clickwork contains Clickwork.exe and eventual APPs that are specific to Clickwork only. And Molebox creates there ClickWork.exe.mbxcfg.
>>
>>U:\Molebox\Clickwork\Encrypted is the place I let Molebox create the encrypted Clickwork.exe (and eventual APPs.)
>>
>>The same folder structure I use for Clickwork is used for other applications. The consequence of having general (encrypted) APPs is that the applications that use one or more of these general APPs must all use the same key. Well, I can live with that.
>>
>>Hope you give it a try.
>
>I have remembered the problem I had with Molebox - In one app I use Cryptor encryption library and Molebox is not compatible with that dll at this time. I reviewed my emails and I remember back in Sept 2006 I was in discussion with them about this. There were also some other 3rd party dlls it is not compatible with. Sometimes you can get around it by including VFP runtime dlls but that is not a good option becuase each exe file is increased in size with those dll files. That is one reason why I don't use Molebox at this time.

Hmm, so I spent an hour to documenting something you do not need? Hopefully someone else can appreciate it in the future. ;)
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Previous
Reply
Map
View

Click here to load this message in the networking platform