Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!ll-xn!ames!amdahl!dlb!ardent!rap
From: rap@ardent.UUCP (Rob Peck)
Newsgroups: comp.sys.amiga
Subject: Re: REZ questions.
Message-ID: <352@ardent.UUCP>
Date: 21 Apr 88 16:58:51 GMT
References: <8804201502.AA07604@cory.Berkeley.EDU>
Organization: Dana Computer, Inc., Sunnyvale, CA
Lines: 29
Summary: and I guess this means...

In article <8804201502.AA07604@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> >	I too am trying to get REZ to work but have encountered a problem.
> >My normal environment is to have lots of stuff in vd0: including the Manx
> >compiler, ie. 'cc', 'as', & 'ln'.  My idea is to REZ them and then delete
> >them from vd0:.
> 
> 	Remember that REZ intercepts LoadSeg(), so you still must have the
> executables available in many cases just so programs can get locks on them.
> That is, in those cases where the application 'searches' the path for the 
> executable, it usually gets a lock on it before LoadSeg()ing it, and doesn't 
> bother to LoadSeg() it if it can't get the lock....  REZ doesn't come in
> until the application actually LoadSeg()'s it.

Thanks, Matt, for pointing this out.  I would have been tempted to do the
same as the original poster.  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?)

Anyway, ya saved me a lot of hair pulling -- thanks.


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