Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cadovax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrb!trwrba!cadovax!brent
From: brent@cadovax.UUCP (Brent Rector)
Newsgroups: net.micro.pc
Subject: MS-DOS .EXE file formats
Message-ID: <679@cadovax.UUCP>
Date: Tue, 25-Jun-85 15:22:38 EDT
Article-I.D.: cadovax.679
Posted: Tue Jun 25 15:22:38 1985
Date-Received: Sat, 29-Jun-85 02:45:41 EDT
Reply-To: brent@cadovax.UUCP (Brent Rector)
Organization: Contel Cado, Torrance, CA
Lines: 30

I am about ready to begin a software development project where we will
be using (probably!) Microsoft C V3.0 and assembler. Although the
development and some testing will be done on XT's, the target system
is not a pc and is not running MS-DOS.

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.

So, has anyone done this kind of thing before? If so, do you have the
source available to the utilities which do the conversion?  Or even, am
I really off base and is there a better way to accomplish what I want?

Assuming I am going where no man (or woman!) has gone before, can anyone
provide some pointers to the info on .EXE file layouts in sufficient
detail to allow me to do the above task?

As always I will summarize to the net if sufficient interest warrants.
Thanks in advance!

--------------------------------------------------------------
Brent E. Rector - CONTEL CADO, Torrance, CA
{ decvax, hplabs, ihnp4, ucbvax, sdcrdcf }!trwrb!cadovax!brent
					 philabs!cadovax!brent
-- 
--------------------------------------------------------------
Brent E. Rector - CONTEL CADO, Torrance, CA
{ decvax, hplabs, ihnp4, ucbvax, sdcrdcf }!trwrb!cadovax!brent
					 philabs!cadovax!brent