Path: utzoo!censor!geac!jtsv16!uunet!pyrdc!grebyn!ckp
From: ckp@grebyn.com (Checkpoint Technologies)
Newsgroups: comp.sys.amiga
Subject: Re: New Agnus
Message-ID: <14028@grebyn.com>
Date: 10 Nov 89 16:28:05 GMT
References: <3707@nigel.udel.EDU> <127660@sun.Eng.Sun.COM> <3755@nigel.udel.EDU>
Reply-To: ckp@grebyn.UUCP (Checkpoint Technologies)
Organization: Grebyn Timesharing, Vienna, VA, USA
Lines: 17

In article <3755@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>I think the original question was how to detect the presence
>of an "uninstalled" New Agnus. Obviously, if the New Agnus is
>properly installed then you will boot with more than 512K 
>of CHIP ram.  But what if the new agnus is in a machine that
>originally had the old agnus in it but had the old agnus pulled
>and the new agnus inserted without any other changes?  How does one
>detect that?    -- Darren

    Some previously 'undefined' bits in one of the custom chip registers
have now been defined as an "Agnus Version" value. There is another
location which will give you the "Denise Version" value. I don't have
the docs right with me, or I would post those custom chip register
addresses. At any rate, it should be a simple program to write, which
would inspect these locations and report the Agnus and Denise versions
installed. (KS 1.4 does this automatically, and sets some values in
ExecBase, I believe.)