Path: utzoo!utgpu!watmath!clyde!att!rutgers!gatech!gtss!chas
From: chas@gtss.UUCP (Charles Cleveland)
Newsgroups: comp.sys.amiga
Subject: Re: path: & 1.3 (also RAD: recovering)
Message-ID: <286@gtss.UUCP>
Date: 3 Dec 88 00:10:17 GMT
References: <284@gtss.UUCP> <385@solaria.csun.edu>
Reply-To: chas@gtss.UUCP (Charles Cleveland)
Distribution: na
Organization: Georgia Tech School of Physics
Lines: 63

In article <385@solaria.csun.edu> ecphssrw@trantor.csun.edu (Stephen R. Walton) writes:
)                                       I think you'll be happier if
)you simply make path:c read:
)
)	sys:c/
)	rad:c/
)	df0:c/
)	df1:c/
)
)(or something similar) which will then search the mounted drives and
)no others.  You'll still get a requester if there is no floppy at all
)in df0: and/or df1:, but I think that is rarely the case. 

Wouldn't you know it.  At last I find someone who knows what I want better
than I do.  And he's the wrong sex. :-)  Actually I don't want to use the path
device as a substitute for the PATH command at all.  Not even a little, even
if I would be happier.  I just observed the behavior when checking it out
and thought it was awkward.  For what I want to do instead it will be fine,
because that only involves one unmounted disk.

)	I have used PATH: on several other occasions, without any
)trouble, under most 1.3 Omegas and the release.
)
Thanks for the info.  I stopped using my test path device file instead of
the PATH command and my GURU's stopped too.  Must be some odd interaction.

)>This is under 1.3 Kickstart on an Amiga 1000 with a Michigan Insider.
)
)This is why RAD: doesn't recover.  No recoverable RAM disk can survive
)in C00000 RAM, because of the way Kickstart 1.2 (and 1.3) check for
)its existence.  Only true FAST RAM will work.

By God you're right.  I thought RAD:, like vd0:, might survive some boots
like a simple vulcan nerve pinch, but apparently not.  Now I have to decide
whether the speed of RAD: under FFS is better than, say, just using RAM: or
enjoying the sometimes recoverability of vd0:  Well, since my development
programs almost never produce GURUs ;-) ...
)
)Possible commercial announcement:  Bill Hawes says over on BIX that he
)has finished a similar Path-Handler which will come with the next
)update of WShell.  It allows you to simply say:
)	Assign C: Sys:c,df0:c,df1:c
)(for example).  You can also do a Dir C: with his handler, and get the
)result you expect, rather than an infinite stream of "Unknown Packet"
)errors.

Will it support
	Assign L: sys:L, wp:L, Lattice_C_5.0.1:L ?

That is, does the search extend beyond that for commands, but to other
referenced files as well?

)-- 
)Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
)RCKG01M@CALSTATE.BITNET       ecphssrw@afws.csun.edu
)swalton@solar.stanford.edu    ...!csun!afws.csun.edu!bcphssrw

Thanks for responding.
-- 
-  It is better for civilization to be going down the drain than to be  -
-  coming up it.                                        -- Henry Allen  -
Charles Cleveland  Georgia Tech School of Physics  Atlanta, GA 30332-0430
UUCP: ...!gatech!gtss!chas                INTERNET:  chas@gtss.gatech.edu