Hello Mike,

Wednesday 30 July 2003 20:30, Mike Luther wrote to All:

ML> So is the smart thing to do is to whomp out the entire #:\emx\emx
ML> directory setup, whomp out the entire CONFIG.SYS line segment which
ML> has to do with what the compiler put there?  Then next go whomp out
ML> the entire #:\PJGCC directory which is there?  We then run UNIMAINT
ML> and maybe CHECKINI and so on and watch for fireworks?  Then .. start
ML> all over with the new GCC321 install routine?

ML> Ever seen a puppy going round and round a turtle contemplating
ML> something? Ever notice the difference in the puppy's demeanor if the
ML> turkle is a SNAPPING turkle?

After installation:

You can also take everything out of config.sys and put all that's to do
with a particular software in a separate .cmd file that gets called when
that software is to be run. In that .cmd file you put commands to temp add
to the path and libpath the needed directories. Check out BEGINLIBPATH and
ENDLIBPATH in the COMMAND REFERENCE.

Here is an example with Virtual Pascal (VP):
------------------------------
{at}echo off
SETLOCAL
rem SET HELP=%HELP%;C:\VP\;
SET PATH=C:\VP\BIN.OS2;%PATH%;
SET BEGINLIBPATH=C:\VP\BIN.OS2;
VP2 %1
ENDLOCAL
------------------------------

Above is handy for many files which belong together for software that's not
used all the time.

Another approach is to stick all files into appriopriate directories which
are already in your respective paths (so not use the install routine that
comes with that software but instead put all files in the respective
directories by hand). I did this with the EMX files. This is handy for
not-many files.



  Greetings   -=Eddy=-

netmail: 2:280/5003.10  1:261/38.3
  email: e.thilleman{at}freeler.nl
         e.thilleman{at}hccnet.nl

... Will someone please explain this conversation to me? -- Bashir
--- GoldED/2 3.0.1