Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucsd!ogicse!emory!hubcap!lsalomo From: lsalomo@hubcap.clemson.edu (lsalomo) Newsgroups: comp.os.msdos.misc Subject: Re: when (and when not) to exe2bin? Message-ID: <11351@hubcap.clemson.edu> Date: 2 Nov 90 15:22:26 GMT References: Distribution: comp Organization: Clemson University, Clemson, SC Lines: 22 >>One more thought, I see no reason why the loader would put the relocation >>table into memory, all my experience would lead me to believe that that >>in fact is the case. So an EXE2BINed program should not use appreciably >>less space in memory than its non-EXE2BINed cousin. What? Don't try and tell me that the loader keeps the relocation table in memory after it has loaded the program!...Is that what you meant? The way I understand it, and the way MY loader works, is to read the header, allocate a block of memory to read the relocation table into memory (who's size is in the header), then read the code itself into another block of allocated memory. Finally, it goes through the relocation table, patching up the code, deletes the relocation table, and jumps to the starting address. Cheers, Q - the "Q"uestor for knowledge (, a degree, etc.) lsalomo@hubcap.clemson.edu ibmman@clemson.clemson.edu ============================================================================= "Gee Wally, I think there's something wrong with the Beaver." =============================================================================