Well, a reference to the COM server(mtdll) will be in memory. COM servers aren't the same as regular dlls(like C++ dlls)that are just libraries of functions.
>Well, what I try to do is avoid REFOX or other tools. The main idea is encapsulate the real application inside another application which expands on memory at run time. It is based on double-click or a launch of the protected application but transparent to the user.
>
>For my knoweledge, I can see two scenaries: a DLL has inside functions that can be called but after this DLL is loaded; and a DLL usually must be registered.
>
>I need to think about that, but for the moment I can guess that the idea it will be encaspsulate the real DLL on other DLL. And in this case the user must call a function on the protected DLL so the original one became to be expanded and registered in this moment. In this case you will need to add lines of code to do that. WWF-VFP was thought on the idea that the user does not need to modify any line of code.
>
>As you know, there is nothing impossible if you can imagine, it's only a matter of time.
>
>I will work on it. Hold the line.
>
>For the moment, due you have been working on MTDLLs a question to you: do you know if once the MTDLL is loaded in memory is it available for other applications? If the answer is yes, it will be easy to implement the protection scheme, due the application or DLL which encapsulate the orginal file, can make a call to a dummy function of the orginal MTDLL, lefting this DLL on memory available to the rest of applications.
>
>Sincerely,
>
>Jorge Grundman
>http://mp3.com/grundman