🚀 go-pugleaf

In article <EMORENO.93Jan26140004@scheria.NMSU.Edu> emoreno@scheria.NMSU.Edu (Elena M. Castruita) writes:
>
>	Thanks to all who replied about FSF's aout2exe.  I already
>have that.  What I wanted is something that creates an exe file ( out of
>a GCC aout format file ) that DOES NOT use go32.  aout2exe prepends a
>call to go32 to the aout file.  In order to run program hello.exe
>(compiled on machine X) on machine Y, I would need to install go32 on
>machine Y.  That is something I want to avoid if at all possible.  
>
>	Anyone know of anything that will do what I want?

Do this then:

copy /b go32.exe+a.out new.exe

use filenames as appropriate.

Some notes:

This will be slower than using (the supplied) aout2exe.  aout2exe aligns
the appended a.out file on a 4k boundary, which makes for about a 10-25%
increase in paging speed (go32, when it needs to page out something, if 
the victim page is code, it is just discarded and read back in later 
from the a.out file).

This method, if you have several go32 binaries, will eat up a LOT more
disk space. (go32=50430 bytes, stub=6572 bytes)


You can solve the first problem by recompiling aout2exe.  There is a
program someone in the djgpp distribution that filters a binary file
and makes it into a .h file that is all hex.  Usually it's run one 
stub.exe, and aout2exe is built containing all of stub.exe internally.
You should just as easily just use go32.exe instead of stub.  This will
both prepend go32 and page align it for faster execution.



remember, you HAVE to have go32 somewhere in order to run the a.out style
files.   

mrc

-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle@cs.umr.edu     and be right all the time, or not work at all
S087891@UMRVMA.UMR.EDU   and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen