home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!waikato.ac.nz!comp.vuw.ac.nz!actrix!templar!jbickers
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: a Path for Workbench
- Message-ID: <jbickers.0bms@templar.actrix.gen.nz>
- From: jbickers@templar.actrix.gen.nz (John Bickers)
- Date: 21 Jul 92 19:05:41 PST
- References: <1992Jul20.124014@hp10.lri.fr>
- Organization: TAP, NZAmigaUG
- Lines: 25
-
- Quoted from <1992Jul20.124014@hp10.lri.fr> by jpr@hp10.lri.fr (Jean-Pierre Riviere):
- > I think that Workbench needs a path handling, just like a shell. That
- > would ease the
-
- > What do you think about it ?
-
- I had something like this, for KS 1.2. It did a path, aliases and
- resident programs.
-
- I looked at doing it for KS 2.0 (in principle it would have been
- easier, because SetFunction()ing DOS is much more straightforward,
- and various shell things exist to make life nicer), except for one
- problem. The new Workbench tries its own path mechanism - if you
- watch it with a slick tool like SnoopDOS, it CDs to each directory
- on its path, then tries to LoadSeg() or somesuch the file from
- that directory.
-
- My 1.2 program worked by trapping LoadSeg(). Under 2.0, this means
- my patch would get called many times for a single user invocation
- of a program, which I think sucks. Also, it doesn't help that the
- 1.2 version was shareware, which no-one registered... :)
-
- --
- *** John Bickers, TAP, NZAmigaUG. jbickers@templar.actrix.gen.nz ***
- *** "Radioactivity - It's in the air, for you and me" - Kraftwerk ***
-