Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 beta 3/9/83; site microsoft.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!cornell!uw-beaver!microsoft!markz From: markz@microsoft.UUCP (Mark Zbikowski) Newsgroups: net.micro.pc Subject: re: converting EXE file into memory images Message-ID: <8758@microsoft.UUCP> Date: Tue, 2-Jul-85 15:56:31 EDT Article-I.D.: microsof.8758 Posted: Tue Jul 2 15:56:31 1985 Date-Received: Thu, 4-Jul-85 05:34:11 EDT Organization: Microsoft Corporation Lines: 23 > An obvious problem will be converting the .EXE file produced by the linker > to a format the target machine can load and execute. Currently we are > planning to somehow convert the .EXE file to a memory image which can > then be loaded to a known address by the bootstrap routines. > > -------------------------------------------------------------- > Brent E. Rector - CONTEL CADO, Torrance, CA > { decvax, hplabs, ihnp4, ucbvax, sdcrdcf }!trwrb!cadovax!brent > philabs!cadovax!brent > -- > -------------------------------------------------------------- The obvious and simple way to convert an EXE file into a core image is to load it with DEBUG and save it with the "w" command. Bob Bruck { allegra | hao | ...}!nbires!bob Yikes! Sure, let's have DEBUG do some RANDOM relocation and wonder why the program doesn't work. IBM supplies a program EXE2BIN that does what you expect. If a relocation adjustment is needed, the program will prompt for the value.