On 7/7/2007 3:25 AM, tuitfun wrote:
> i think normally Windows just look for dll
> files in the current directory and in C:\WINDOWS\system32, right?

>From the documentation for the Win32 API function LoadLibrary (which is
used to load DLLs):

When no path is specified, the function searches for loaded modules
whose base name matches the base name of the module to be loaded. If the
name matches, the load succeeds. Otherwise, the function searches for
the file in the following sequence:


1. The directory from which the application loaded.
2. The current directory.
3. The system directory. Use the GetSystemDirectory function to get the
path of this directory.
4. The 16-bit system directory. There is no function that obtains the
path of this directory, but it is searched.
        Windows Me/98/95:  This directory does not exist.
5. The Windows directory. Use the GetWindowsDirectory function to get
the path of this directory.
6. The directories that are listed in the PATH environment variable.

Windows Server 2003, Windows XP SP1:  The default value of
HKLM\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode
is 1 (current directory is searched after the system and Windows
directories).

Windows XP:  If HKLM\System\CurrentControlSet\Control\Session
Manager\SafeDllSearchMode is 1, the current directory is searched after
the system and Windows directories, but before the directories in the
PATH environment variable. The default value is 0 (current directory is
searched before the system and Windows directories).

-- 
Charles



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users

Reply via email to