RE: [DUG]: Solution to a Theory

[Jeremy Coulter]

Yeah its not that I am trying to "Stop" someone finding out what DLL I am using, its also a bit of a safegaurd that the DLL wont be accidently deleted ot what ever also.   Also its not really a copy protection thing either, its just something I was wanting to try out.   I will take a look at your suggestions tho.   Thanks Jeremy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nello Sestini Sent: Sunday, 19 August 2001 18:22 To: Multiple recipients of list delphi Subject: Re: [DUG]: Solution to a Theory two possibilities   1.  start your app from another applett that first     creates the DLL and then runs your app as a daughter.   2.  change your app to not statically bind to the DLL -     load it dynamically on startup and do GetProcIDs     on all the functions you call.   neither of these is going to fool someone seriously interested in your use of the supersecret DLL.   they can always power off the computer while you're running and then look at the file left over after they reboot.   -ns   ----- Original Message ----- From: Jeremy Coulter To: Multiple recipients of list delphi Sent: Sunday, August 19, 2001 1:04 PM Subject: [DUG]: Solution to a Theory Hi All. I have an app. that requires a DLL. Now I dont nessicarily want people to know that it needs this DLL, IF I can help it.   I have a unit that uses early binding to call the functions and procedures in the DLL. I thought I could inclused the DLL in a resource file for the EXE, and then before all the application bits in the project file of the EXE, extract the DLL. BUT because of the early binding, Its looking for the DLL before the app. runs.   Can anyone suggest a solution?   Thanks, Jeremy Coulter