Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga
Subject: Re: Problems with Ares
Message-ID: <9485@batcomputer.tn.cornell.edu>
Date: 31 Dec 89 00:28:58 GMT
References: <7200176@m.cs.uiuc.edu>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 17

In article <7200176@m.cs.uiuc.edu> schwager@m.cs.uiuc.edu writes:
>On files that appear to be compiled with Aztec C, Ares (of Arp fame)
>complains about checksum errors in the file.  Also, some (DMake, for
>instance) will guru my machine regularly if I try to make it resident.  Am
>I hosed, or is Ares?  Can anyone explain this behavior?

Ares is not designed to make arbitrary programs resident.  It only works
for "pure" programs--programs that don't modify global or static data.
If you make a program resident that does modify its data segment, you
will get complaints about checksum errors and you are risking crashing
your machine.  Generally, programs have to be very carefully written
in order to be pure, although Lattice 5.0 does come with startup-code
and special smarts in the linker that makes creating pure programs
very easy.

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell University