On Mon, 23 Sep 2002 21:35:52 -0500, Michael Kaply <[EMAIL PROTECTED]> wrote:
> Nicky Morrow wrote: >> PATH and LIBPATH ? Why? Please don't... > > Believe it or not, some people want to be able to run the browser from a > command line and don't want to write a million CMD files. A million? One surely? IMHO, this DLL business is a major design flaw in OS/2. Why could the default search path for DLLs not start with the same directory that the .EXE file is in? This would solve 99% of this LIBPATH crap. Adding every application's paths to PATH, DPATH, LIBPATH and HELP is not the way to go. Would it not be better to write a small launcher program that has no DLL dependencies, that could then change to the correct directory (i.e. the one it is running from) before starting the real program? This seems like a much better idea to me...
