🚀 go-pugleaf

In article <Bs7nEp.JLt@knot.ccs.queensu.ca> dmurdoch@QueensU.CA
(Duncan Murdoch) writes:

>Those are both quite dangerous.  Plenty of people use PKLITE or LZEXE or
>another .EXE compressor to modify .EXE files; if you blindly go reading
>and writing at a specific location, you'll mess up badly.

I would have thought look for the string you're changing, then when you
find it, replace it with the new version (which, of course, would be exactly
the same length).

>A better
>solution is to append the data to the .EXE file; the unbuggy compressors will
>think it's an overlay, and leave it alone, or refuse to work.  You
>should also be sure to put a signature in the record, so you can double
>check that whatever calculation you end up with is correct.

someone suggested this via e-mail, too....  but, if all you do is
tack on the text at the end of the .exe, how does the program access it?
does it have to then read the binary for itself every time it runs?  or
is there then a way of getting this into some data structure?

probably a dumb question, but then, I don't claim to know the format of
the compiled binary, either....have never needed to worry about it before.
:-)

>If you want to be really nice to your users, you'll give them the option
>of reading the config info from a config file, too.  That way it's easy
>to maintain multiple different configurations.

that is already there....all configuration is via an ASCII file.  the part
I'm thinking about is for registration.  sorry, should have mentioned that
in my first post.  several people have asked that....

>A nice way to do this (both ways) is using a Turbo Vision resource file,
>if you're using Borland's Pascal or C++.  It's very easy to use a config
>file if present or your .EXE if not, and all the signature checking is
>built in.

Turbo Vision?  I'm using Borland's Turbo C++ (version 1.0), but don't recall
reading about that.  is this something that got added when Borland dropped
the ``Turbo'' bit from the name?

thanks....
   --jim

\input std_disclaimer                     % 73 DE N5IAL (/9)
------------------------------------------------------------------------------
"[...] the plural of `mongoose' ought to be `polygoose'." [Jargon file 2.9.10]

INTERNET:  jim@n5ial.chi.il.us  |  grahj@gagme.chi.il.us  |  j.graham@ieee.org
UUCP:  gagme!n5ial!jim@clout.chi.il.us
AMATEUR RADIO:  n5ial@n9hsi (Chicago.IL.US.Earth)
------------------------------------------------------------------------------