Path: utzoo!attcan!uunet!cbmvax!heimat!sneakers
From: sneakers@heimat.UUCP (Dan "Sneakers" Schein)
Newsgroups: comp.sys.amiga
Subject: Re: Lock fails on DH0: with A2090A
Message-ID: <5820.AA5820@heimat>
Date: 14 Jan 89 12:59:34 GMT
Followup-To: comp.sys.amiga
Organization: Sneakers Computing
Lines: 34

In Message <1176@esunix.UUCP>, blgardne@esunix.UUCP (Blaine Gardner) writes:

>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.

  Sounds alot like what I do....

>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.

  I havent read this anywhere, but from my tests it looks like "LOCK" only
  works on FFS devices. To test this just try locking a floppy or ram: -=-
  then mount a FFS version of RAD: and try locking it!

  Sneakers


--
Dan "Sneakers" Schein          {pyramid|rutgers|uunet}!cbmvax!heimat!sneakers
Sneakers Computing
2455 McKinley Ave.                     Of course heimat is an Amiga.
West Lawn, PA 19609           Doesn't everyone run UUCP & UseNet on an Amiga?

   Call: BERKS AMIGA BBS - 60+ Megs - 24 Hrs - 12/2400 Baud - 215/678-7691