<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Frank,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Don't worry. You are friendly compared to how I
treat my users when they mistreat my creations....</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I did some testing. Path behaviour is different for
dll's than for .exe:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For executable, it first takes what is in
the application directory. Then it searches through the paths sequentially.
So if the system directory is at the end of the path statement, it will be
searched last.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For DLL's, it first takes what is in the executable
directory. Then looks in the system directory. Then the rest of the path
statement.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So it seems that only for DLL's does the system
directory take presedence of the other paths.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Jacob</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>-----Original Message-----<BR>From: Frank Warmerdam
[mailto:warmerdam@pobox.com] <BR>Sent: 20 October 2004 12:35<BR>To: Jacob
Delfos<BR>Subject: Re: [UMN_MAPSERVER-USERS] Installation Failure with Proj.dll
entry Problem</FONT></DIV>
<DIV> </DIV><FONT face=Arial size=2>
<DIV><BR>Jacob Delfos wrote:<BR>> Frank,<BR>> <BR>> Don't get me
wrong, it wasn't my intention to make your life as a <BR>> developer
difficult. I was only trying to help out someone who was stuck <BR>> (and I
did; he mentioned to me that it worked).<BR>> <BR>> If the dll's are
in the same directory as the executable, these will be <BR>> used rather than
those in the system directory. </DIV>
<DIV> </DIV>
<DIV>Jacob,</DIV>
<DIV> </DIV>
<DIV>Perhaps I have been mislead. My understanding is that DLLs in
the<BR>working directory of the process take precidence over the ones in<BR>the
system directory, but that the system directory takes precidence<BR>over the
PATH. I also didn't *think* that the directory the executable<BR>was in
took precidence over the system directories though of course<BR>for many folks
the directory the executable is in is the system<BR>directory.</DIV>
<DIV> </DIV>
<DIV>Am I wrong?</DIV>
<DIV> </DIV>
<DIV>Hmm, now that I look through my distribution, the one executable
that<BR>isn't the same directory with all the DLLs is python.exe. Perhaps
if<BR>I just dumped it in the bin directory with all my other executables
I<BR>would have a lot less conflict problems with users of OpenEV_FW.</DIV>
<DIV> </DIV>
<DIV>Also, sorry if I came across as being crabby and I can sympathize with
how<BR>hard it is to get PATH environment variables into cgi programs and
other<BR>odd places. I have had this too. It's just the soup of DLLs
scares me.</DIV>
<DIV> </DIV>
<DIV>Best regards,<BR>--
<BR>---------------------------------------+--------------------------------------<BR>I
set the clouds in motion - turn up | Frank Warmerdam, <A
href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</A><BR>light and sound -
activate the windows | <A
href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</A><BR>and watch
the world go round - Rush | Geospatial Programmer for
Rent<BR></FONT></DIV></BODY></HTML>