🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.msdos.programmer
Article #560

Re: changes to exe (binary) file

#560
From: Bob Montante
Date: Thu, 30 Jul 1992 17:35
16 lines
1386 bytes
One approach is to organize your changeable information in a structure
that has some simple tag, such as an ASCII character string, at the
beginning.  (A version I.D. would work well.)  Then your configuration-
changing program can simply search the executable for that ASCII character
string, and make changes at known locations relative to the string.  If
you don't *find* the string, then it's the wrong executable, or it's
been compressed, or something else has changed in it (which probably
means it can't be altered anyway).  As long as you preserve the data
structure, your configuration program should (may) work with subsequent
versions of your executable program.

Claimer:  I thought up this idea for use in my HP-00 calculator program,
and others may have thought of it too; so don't try to patent it.  If
you're really impressed with it, use my name as the ASCII string :-)

-bob,mon.
Technical Details
Message-ID: <1992Jul30.123512.17763@news.cs.indiana.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!rutgers!news.cs.indiana.edu!bobmon@sandshark.cs.indiana.edu
References: <1992Jul29.125540.7401@hou.amoco.com> <1992Jul30.152020.8261@menudo.uh.edu> <Bs7nEp.JLt@knot.ccs.queensu.ca>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!rutgers!news.cs.indiana.edu!bobmon@sandshark.cs.indiana.edu
From: bobmon@sandshark.cs.indiana.edu (Bob Montante)
Newsgroups: comp.os.msdos.programmer
Subject: Re: changes to exe (binary) file
Message-ID: <1992Jul30.123512.17763@news.cs.indiana.edu>
Date: 30 Jul 92 17:35:08 GMT
References: <1992Jul29.125540.7401@hou.amoco.com> <1992Jul30.152020.8261@menudo.uh.edu> <Bs7nEp.JLt@knot.ccs.queensu.ca>
Organization: dyskaryotic
Lines: 16