Path: utzoo!attcan!uunet!snorkelwacker!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <25990@usc.edu>
Date: 18 Jul 90 16:44:23 GMT
References: <619@cbnewsb.ATT.COM> <5213@darkstar.ucsc.edu> <1500@faatcrl.UUCP>
Sender: news@usc.edu
Distribution: na
Organization: Felsina Software, Los Angeles, CA
Lines: 17

In article <1500@faatcrl.UUCP> jprad@faatcrl.UUCP (Jack Radigan) writes:
>You have to run the 590FIX program or any little utility that resets memory
>location zero to 0.  I still haven't been able to figure out what is doing
>this as MemGuard III does not report a low memory stomp on my A1000.  More
>distressing is that when I stomp on location zero with ZeroMung, it continues
>to work fine on my A1000...  Damndest thing I ever seen...

Stomping on location 0 is a no-no for any application program. This is 
usually the result of an uninitialized pointer.  I believe the hddisk
device (or whatever it is called) for the A590 and A2091 assumed that
nobody would stomp on location zero. I recall a message to that effect from
CATS people a while back.

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=