Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!cs.utexas.edu!sun-barr!ames!attctc!jolnet!caw
From: caw@jolnet.ORPK.IL.US (Chris Wichura)
Newsgroups: comp.sys.amiga
Subject: Re: Problems with Ares
Keywords: ARP Manx Lattice
Message-ID: <2616@jolnet.ORPK.IL.US>
Date: 31 Dec 89 00:48:18 GMT
References: <7200176@m.cs.uiuc.edu>
Reply-To: caw@jolnet.UUCP (Chris Wichura)
Organization: Jolnet, Public Access Unix, Orland Park (Joliet), Ill.
Lines: 17

This is a problem that you will probably find with both Lattice and Manx
programs, both.  It has to do with the requirements of a resident program.
If a program was not specifically designed to be resident (does things  like
duplicating its data hunk on each invocation, etc) then ARes will complain
about a checksum error the next time you try and use it because the program
has altered memory in its data storage area.
 
Now, as to why it should cause your system to GURU I haven't the foggiest.
I have never had such a problem.  All the commands I use ARes on, though,
are written to be re-entrant and if I get a checcksum error then I know the
program has been condemed to being loaded from disk and use ARes' remove
command to get rid of it.

-- 
Christopher A. Wichura
u12401 @ uicvm.uic.edu  (my home account)
caw @ jolnet.UUCP       (my Usenet feed)