Michael Kaply wrote:
> DuaneC wrote:
>> it really only takes ONE CMD file ;) off the top of my head...
>
> That may be great for you "techie" uesrs, but not everyone wants that.
well the user doesn't have to do anything... the installer can simply
copy this CMD to a directory already on the path (tcpip/bin, /os2, etc)
> All applications should give users the option of adding thing to LIBPATH
> and PATH.
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.
truthfully, the SET BEGINLIBPATH can be set as the WPS icon argument...
eliminating the need for this too.
--
|\
__| \ ___ Duane Chamblee
/ |__/ President
\__| \___ dAcDigital Co.
