Path: utzoo!lsuc!ncrcan!brambo!morgan
From: morgan@brambo.UUCP (Morgan W. Jones)
Newsgroups: comp.sys.amiga
Subject: Re: REZ questions.
Message-ID: <401@brambo.UUCP>
Date: 29 Apr 88 00:33:52 GMT
References: <8804201502.AA07604@cory.Berkeley.EDU> <352@ardent.UUCP>
Reply-To: morgan@brambo.UUCP (Morgan W. Jones)
Organization: Bramalea Software Inc., Bramalea, Ont.
Lines: 32

In article <352@ardent.UUCP> rap@ardent.UUCP (Rob Peck) writes:
>To save space in this case, rather
>than have the executable around, one might just have a teeny file
>having the same name as the executable, somewhere in the PATH, just
>to satisfy the locking requirement.  And that file could be nothing
>more than an assembled/linked version of:
>
>DummyFile
>	rts
>
>(or am I misinterpreting something?)

You're misinterpreting somthing, but you're on the right track.  Since
REZ will stop the file from ever being loaded, a zero length file will
do the trick.  If ram: is in you're path and you've just REZ'd a
program called prog, "cat <nil: >ram:prog" works just great.  The
problem arises in that REZ -r won't clean out this file (a minor
point).

>Rob Peck			...ihnp4!hplabs!ardent!rap

Just making sure:
.
.
.
.
.

-- 
Morgan Jones - Bramalea Software Inc.        morgan@brambo.UUCP
      ...!{uunet!mnetor!lsuc!ncrcan, utgpu!telly}!brambo!morgan
"These might not even be my opinions, let alone anyone else's."