I actually updated the WARPZFOL.CMD to add the environment variables to
the desktop objects...
Basically, you can use environment variables in an Object's setup string
but you have to delimit the semicolons in the paths... This means you
have to add the delimiter to the existing ENVs before applying them.
OBJECTID=<WARPZILLAFLDR>;SET BEGINLIBPATH=X:\MOZILLA\BIN;
SET PATH=X:\MOZILLA\BIN^;C:\MPTN\BIN^;C:\IBMCOM^; (etc)
The only real problem with this is that if the program moves, the
environment is wrong.
- Rant on -
Can't the native OS/2 program, as a last resort, fetch the location the
EXE is running from and use that path to load the DLLs?
Why doesn't the MOZILLA_HOME environment variable have a INI setting
instead? There really should be a need to reboot to run a program like this.
- Rant off -
Keep up the good work.
Michael Kaply wrote:
> They certainly can't run at the same time.
>
> In order to have them coexist, set the BEGINLIBPATH bin and
> bin/components directory of the one you are trying to start.
>
> Mike Kaply
> IBM
