Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes:
when an application is run in a directory, where there is also a kernel32.dll, and this is _not_ the system directory, MODULE_GetLoadOrder doesn't strip the path and therefore crashes when native kernel32.dll is loaded.
While the header of MODULE_GetLoadOrder talks about "any path is stripped", the function only strips the path for "16 bit modules or if the module resides in the system directory "
Is this intended behaviour?
Yes, there can be multiple versions of a 32-bit dll with the same name in different directories, and we have to be able to configure them separately.