🚀 go-pugleaf

I think i am only left with two options by the looks of it, either create my
own encrypted data file to go along with the exe file, or to create a header
and data section and tag the data to the end..
I have actually done it before but not with tagging image data to the end ,
but it sounds like dirty programming somehow, but then i suppose its been
working for me on a program i wrote 2 years ago....


"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> wrote in message
news:4011e537$1@newsgroups.borland.com...
>
> "borland" <rogersmail@ntlworld.com> wrote in message
> news:4011d110@newsgroups.borland.com...
>
> > The problem i have is that he doesn't want the image to be
> > available to other to allow them to either replace or change it..
>
> If you are installing the program on an NT-based system (NT4, 2K, or XP),
> you could always just make it so that non-admin users can't touch/modify
any
> files that the application is dependant on.
>
> > The only ideas i have come up with so far it to write a header
> > preceeded with a magic number at the end of the stream which
> > will give the image and data sizes to read and offsets to the
> > magic nunber..
>
> That wouldn't stop someone fom altering the data if they really wanted to,
> once it was determined what you were actually doing.
>
> > Is it possible to create a dll at runtime and fill it with data
>
> In theory, yes.  You would have to have intimate knowledge of how DLLs and
> the PE format work in general, though.  Alternatively, you could create a
> pre-compiled stub DLL that does not include the actual data, but is set up
> to look for the data at the end of the stub.  Then you could simply copy
the
> stub to a new file when needed and append the desired data to the end of
it.
>
> > so i can at least ask if he will  be happy with an exe and one dll..
>
> That won't stop someone from simply replacing the DLL with another one,
> though.
>
>
> Gambit
>
>