Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!sunybcs!bingvaxu!leah!wfh58
From: wfh58@leah.Albany.Edu (William F. Hammond)
Newsgroups: comp.sys.amiga
Subject: Re: The A-590/2091 FFS problem
Summary: look, poke, look, lock, look
Message-ID: <3398@leah.Albany.Edu>
Date: 25 Jul 90 22:27:29 GMT
References: <2085@gould.doc.ic.ac.uk> <6600012@okcusr.UUCP> <1449@nyx.UUCP> <1581@nyx.UUCP> <1990Jul16.023510.12197@uncecs.edu> <907@pccuts.pcc.amdahl.com> <32023@cup.portal.com> <139472@sun.Eng.Sun.COM>
Reply-To: wfh58@leah.albany.edu.UUCP (William F. Hammond)
Organization: Dept of Math & Stat, SUNYA, Albany, NY
Lines: 27

In article <139472@sun.Eng.Sun.COM> cmcmanis@stpeter.Eng.Sun.COM (Chuck McManis) writes:
>In article <32023@cup.portal.com> (Patrick John Horgan) writes:
>>I too get this string.  I got it before I switched to the fast-file
>>sytem, though.  Wish I know why:(
>
>Because someone puts it there. Boot a virgin workbench and see if you
> . . .

First, as far as I am concerned, the longword at location 0 belongs to
Commodore-Amiga.

Having said that, let me say that a friend was having trouble with an
item and became concerned about this issue.  So we concocted a "look"
utility to see what's there and a "poke" to zero out the longword at
location 0.

It seems to be the case that using the "lock" command to change the
write protect status of dh0: (vanilla 2500/30 with A2091) will cause
the hex value 0B000008 to be placed in the longword at location 0.
I don't know why, and I don't know whether there are other ways to
provoke it.  I have never seen any other non-NULL value sitting there.

----------------------------------------------------------------------
William F. Hammond                   Dept. of Mathematics & Statistics
518-442-4625                         SUNYA, Albany, NY 12222
wfh58@leah.albany.edu                wfh58@albnyvms.bitnet
----------------------------------------------------------------------