When you ported the program over to Windows 7 did you recompile everything to make it 64bit? There was a bug floating around MSDN wrt Windows 7 and calling 32 bit dlls. The bug resulted in an error however, I think it was "invalid image file" or something like that.
Originally Posted by anduril462
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
Do you get any error message or crashed? How is the dll linked to your program? Do you load it dynamically, if so, was it found and was the entry point found?
Did you recompile the executable with a newer compiler when changing systems? The STL and most other libraries can't be mixed, all executables and libraries need to be compiled by the same compiler (including version) to function.
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
So much for C++'s claims of portability....
What's the error returned by GetLastError when you fail to LoadLibrary or GetProcAddress? If you don't have control of the loading code, grab Process Monitor to see what it's trying to load and the error, or grab DebugView and wade through the loader's debug spew.
Sounds to me like there's a bug in the app or the DLL. Thus explaining both "it changes when moving to another platform" and "at least once, it magically worked." I seriously doubt this has anything to do with DLLs, loading of DLLs, administrator permissions, or OS version. Just a bug somewhere.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
