Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.UUCP (Michael van Elst)
Newsgroups: comp.sys.amiga.tech
Subject: Re: CurrentDir
Message-ID: <673@mpirbn.UUCP>
Date: 24 Mar 90 19:41:35 GMT
References: <00173.AA00173@starsoft.UUCP> <133060@sun.Eng.Sun.COM> <1332@quintus.UUCP> <1990Mar21.082549.9252@santra.uucp> <133343@sun.Eng.Sun.COM> <9965@batcomputer.tn.cornell.edu> <14801@nigel.udel.EDU>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 12

In article <14801@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>...  At least under 1.3 and 1.3.2, it seems safe
>to ZERO the lock field in the startup message for any lock
>you unlock yourself. Then WB will not try to re-unlock it.
>	      -- Darren

Actually, WB even frees the zeroed Lock. Fortunately, this operation
is allowed by AmigaDOS since it uses the zero Lock as a pointer to
the boot device.

Michael van Elst
p554mve@mpirbn.mpifr-bonn.mpg.de