Article View: comp.sys.amiga.tech
Article #3052Re: CurrentDir
From: Darren New
Date: Fri, 23 Mar 1990 18:12
Date: Fri, 23 Mar 1990 18:12
12 lines
1157 bytes
1157 bytes
In article <9965@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu (Daniel S. Riley) writes: >[...] When your process >replies to the startup message (when it exits), workbench cleans up all >the locks in the startup message. If you've already UnLock()ed any of >those locks, bad things happen. Empirically, I have found a way around this. I needed to be able to close all the locks I had open so that I could pull the disk without WB leaving the icon up. 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
Technical Details
Message-ID:
<14801@nigel.udel.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!udel!newReferences:
<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>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!udel!new From: new@udel.edu (Darren New) Newsgroups: comp.sys.amiga.tech Subject: Re: CurrentDir Message-ID: <14801@nigel.udel.EDU> Date: 23 Mar 90 18:12:31 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> Sender: usenet@udel.EDU Reply-To: new@udel.edu (Darren New) Organization: University of Delaware Lines: 12