Path: utzoo!attcan!uunet!lll-winken!lll-ncis!oodis01!uplherc!esunix!blgardne
From: blgardne@esunix.UUCP (Blaine Gardner)
Newsgroups: comp.sys.amiga
Subject: Lock fails on DH0: with A2090A
Message-ID: <1176@esunix.UUCP>
Date: 7 Jan 89 19:51:55 GMT
Organization: Evans & Sutherland Computer Corporation
Lines: 36

I have the A2090A autobooting an ST506 drive. DH0: is a 136K partition
used to boot the system, and hand off to my first FFS partition.

When I lock either of my FFS partitons it works fine, but 

"Lock dh0: on"

returns the message

"Attempt to change lock failed"

Any ideas why this happens? I'd prefer to keep DH0: locked at all times
since there is no valid reason for anything to write there most of the
time. With the new virus, any bit of added security would be most
welcome.

Here's my DH0: startup-sequence.

c:SetPatch >NIL: ;patch system functions
Sys:System/FastMemFirst
c:mount FF0:
c:mount FF1:
defdisk FF0:
c:cd sys:
execute startup-sequence

The startup-sequence on FF0: (my FFS SYS: partition) does all kinds of
strange and wonderful things, but there is no reference to DH0: in it.

It the lock failure on DH0: because the A2090A has done something
magical to it during the autoboot process?
-- 
Blaine Gardner @ Evans & Sutherland    580 Arapeen Drive, SLC, Utah 84108
Here: utah-cs!esunix!blgardne   {ucbvax,allegra,decvax}!decwrl!esunix!blgardne
There: uunet!iconsys!caeco!pedro!worsel!blaine
"Nobody will ever need more than 64K."    "Nobody needs multitasking on a PC."