Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!tness7!texbell!tness1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: PATH:
Message-ID: <2867@sugar.uu.net>
Date: 20 Oct 88 11:45:42 GMT
Organization: Sugar Land Unix - Houston, TX
Lines: 40

Alas, but Rico Mariani's PATH: device doesn't work for me as a replacement for
the PATH kludge in AmigaDOS.

(edit mountlist, install path-handler)
1> mount PATH:
(system still up, a good sign!)

I note that I can create normal subdirectories in PATH: as well as create
files. It's still a fully functional RAM disk... a nice feature.

(after creating path:s containing sys:s and sys:devs)
1> type path:s/mountlist
(works fine)

(after creating path:c containing sys:system, sys:bin, and sys:c)
1> path:c/ls
Unable to load path:c/ls: stream name component invalid
1> assign c: path:c
1> ls
Unable to load ls: Error code 210
1> why
Unable to load why: Error code 210
1> sys:c/why
Last command failed because stream name component invalid
1> sys:c/assign c: sys:c
1> why
Last command did not set a return code
(phew, at least I can get out of it)

From the posting:
>      This is a mountable device driver that allows you to have search
> paths for any directory, and those paths may include drive names as well as
> volume names, thus fixing one of the most irritating limitations of the
> AmigaDOS PATH command.

Obviously I'm not doing something right. Any ideas?
-- 
		Peter da Silva  `-_-'  peter@sugar.uu.net
		 Have you hugged  U  your wolf today?

	Disclaimer: I accept full responsibility for my own typos.