DuaneC wrote: > most applications should not need this. > > an EXE file when loaded should be able to perform DLL searching, but > also check the directory where the EXE is LOADED (and down) > > basically on init, ask the OS "where am I"... \progs\exepath... > > then load DLLs from there. >
You can't do that. The DLLs are statically linked. They have to be there WHEN the EXE is loaded. The EXE does not explicitly load them. I agree this is a design flaw in OS/2. I'll point out two things here. 1. Using a CMD file or launcher is ugly. 2. Using a CMD file or launcher won't work well with the WPS URL association stuff. 3. The browser is really an integral part of the operating system. 4. There are people that don't have a . in their LIBPATH so we have to do something to even launch from the WPS. 5. Updating CONFIG.SYS will be an option. I'm not going to provide a CMD file to launch the application. If people want to write that for their own use, they can. After installing Mozilla, it will work from the icon as long as you have a . in your LIBPATH. Otherwise you have to reboot or write a CMD file. You guys obviously have no idea how many normal everyday endusers that know nothing install this thing. I want it to work for those people. Mike
