Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cis.ohio-state.edu!ucbvax!pasteur!bonsai.Berkeley.EDU!karlson
From: karlson@bonsai.Berkeley.EDU (Eric Karlson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Symbolic info in .EXE files
Message-ID: <13948@pasteur.Berkeley.EDU>
Date: 3 Jun 91 17:59:53 GMT
References: <1991May31.054718.15255@atlas.abccomp.oz.au>
Sender: news@pasteur.Berkeley.EDU
Reply-To: karlson@bonsai.Berkeley.EDU (Eric Karlson)
Organization: University of California at Berkeley
Lines: 10

I believe that you will find that there is a variable amount of space between
the EXE header and the begining of the actual code in an EXE file.  There
is are fields in the header that indicates the size of the header, the size of
the relocation table, the start of the relocation table and the start of
the executable code.  By properly manipulating these fields you can open
up a space in the file following the header or relocation table which should
be ignored by the EXE loader.  I've never looked at my EXE files that have
symbolic information in them, but I suspect that this is where it has to be.

							Eric Karlson