Path: utzoo!attcan!uunet!cbmvax!cbmehq!cbmdeo!adspdk!hclausen
From: hclausen@adspdk.UUCP (Henrik Clausen)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A590 problems
Message-ID: <1815a80b.ARN03577@adspdk.UUCP>
Date: 21 Oct 90 17:20:59 GMT
References: <1990Oct11.193142.13719@ecst.csuchico.edu> <995@rulcvx.LeidenUniv.n <271cfba7-999.12comp.sys.amiga.tech-1@tronsbox.xei.com>
Reply-To: hclausen@adspdk.UUCP
Followup-To: comp.sys.amiga.tech
Organization: Graffiti Data
Lines: 25

In article <271cfba7-999.12comp.sys.amiga.tech-1@tronsbox.xei.com>, HIM writes:
> ><995@rulcvx.LeidenUniv.nl> [A.J. van Rooijen] (*Masked*@rulcvx.LeidenUniv.nl)

> >The reason I ask this is that I know that the A590 does something with
> >location 0. In my opinion it should not do that.

   Certainly shouldn't. It's a known bug in an early FFS version. I seem
to remember the 1.3.2 update containing a fixed FFS.

> So if a program will not run with location 0 being ANY value in particular ,
> then it is that programmers fault, not the A590's.

   It's a fault on *BOTH* programs - you may call it a binary bug, it takes
another bug to expose the first one. VirusX, JRComm e.a. have this 'using
$0 as pointer' bug that shows when something weird is in $0.

> Report this to the manufacturer. It is a bug.

   So true. VirusX and JRComm where fixed. So is FFS - get it, and you're
all set.

                                                    -Henrik
|            Henrik Clausen, Graffiti Data (Fido: 2:230/22.33)           |
|           ...{pyramid|rutgers}!cbmvax!cbmehq!adspdk!hclausen           |
\__"Do not accept the heart that is the slave to reason" - Qawwali trad__/