From: jpr@sun4.lri.fr (Jean-Pierre Riviere)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Path *and* ALIAS for Workbench
Date: 24 Jul 92 07:42:11 GMT
Organization: Laboratoire de Recherche en Informatique


In article <jbickers.0bss@templar.actrix.gen.nz>,
jbickers@templar.actrix.gen.nz (John Bickers) writes:
|> Quoted from <1992Jul22.083156.16631@lri.fr> by jpr@sun4.lri.fr
|> (Jean-Pierre Riviere):
|> 
|> > Hey, all of you who answered. First thanks you for this. But then,
|> you
|> > forgot the
|> > *real need* for an handling of *alias* for the *workbench* !
|> 
|>     I did NOT forget. That was the main reason I wrote wbres - the
|>     path and resident stuff were just extra. I had a text reader
|>     called "ty" that I wanted to use when going through Fish disks,
|>     because the version of "Less" on those disks at the time sucked
|> -
|>     I also wanted to use "ty" on a number of other PD disks, where
|>     they had used tools like "most", "muchmore", etc.
|> 
|>     Then I wanted to use Carolyn Scheppner's "display" program to
|>     show pictures, instead of "ShowILBM", "ViewILBM", "ShowPic",
|> etc.
|> 
|>     So I set up aliases from these names to "ty" and "display",
|> wrote
|>     a script to set everything up when I started Workbench, and etc.
|> 
Do you really mean it does (with pre-2.0) what I wish 2.0 did ? Wow, I
didn't
get that! Any way to port it to 2.0 (in a more efficient way (see
further)) ?

|> > Now I can tell you that I still use 1.3. Thus I  was not aware of the
|> > new PATH handling of 2.0.
|> 
|>     Then check out wb-back, a set of CLI tools that broke up WBRes
|>     into seperate programs. I made that lot free (I think).
|> 
|> > |>     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
|> 
|> > Beside, I already have LoadSeg patched cause of Powerpacked-library
|> > executables.
|> 
|>     You don't need to patch LoadSeg to run PowerPacked binaries. If
|>     you are, you're going about it the wrong way. You only need it to
|>     load PowerPacked DATA into programs that don't understand

Right for *data*.
BUT my executable file which are *crunched* with PowerPacker with the *small*
bootcode wich *requires* this patch to be *effectively* loaded. Sure, this is
a pain, especially in the making of one's startup-sequence. But thiss
way, I can
gain one block for each powerpacked file, and with a 20Mb HD, I have no
real choice.

|>     PowerPacker - and you don't even need that for most utils. MODs
|>     can be played back with Multiplayer, pictures can be displayed
|>     with programs that use the iff.library (and thus XPK), anims have
|>     ppanim, text files have ppmore and the newer version of MuchMore,
|>     etc.
|> 
|>     Explain more about why you're using PowerPackerPatch, and perhaps
|>     people will be able to suggest better applications.

See previous paragraph.
|> 
|> > That might explain a little more why none has registered...
|> 
|>     Yeah well. WBRes existed some time before PowerPackerPatch. I
|>     always thought the reason no-one registered is because the people
|>     who typically use Workbench didn't understand what it did. :)
|> 
|> >   Jean-Pierre RIVIERE
|> --
|> *** John Bickers, TAP, NZAmigaUG.        jbickers@templar.actrix.gen.nz ***
|> ***    "Radioactivity - It's in the air, for you and me" - Kraftwerk    ***
-- 
  Jean-Pierre RIVIERE        |     ///
  LRI - Universite Paris Sud | \\\///
  e-mail : jpr@lri.lri.fr    |  \///
Newsgroups: comp.sys.amiga.misc