Yeah.. They are DLLs in use. This has worked before under win2k. It would appear that it is failing after installing sp1.
I am putting the files in the system dir derived by calling the GetSystemDirectory api call. I've watched this code work through the debugger.. all the functions return what they should.. The registry entries get written.. but it just doesn't work.
Like I said.. even installshield is failing to get the job done.
It's just broke.

So another question.. if I have a DLL that windows uses in the same dir as my executable for my application. mfc42.dll for instance, will my app use the DLL in the exe dir? or the one windows already has loaded?

>George Tasker said:
>Pure SWAG here. First, from the context of your post, I assume that you're attempting to use the function to install dlls that are currently in use. Is this correct? Is the target directory the system directory under Win2K? If so, it may be that Win2K is preventing this. If your application requires a specific version of a DLL, it should be implemented as a side-by-side DLL and located in a directory on the application's search path. I don't have anything other than this.