Stefan Leichter Stefan.Leichter@camLine.com writes:
Hi Alexandre,
anything wrong with this patch ?
Well, the resource id is 1, so loading it with 0x65 is certainly not going to work. Were you planning to change the resource too?
Am Sonntag, 28. August 2005 18:31 schrieb Alexandre Julliard:
Stefan Leichter Stefan.Leichter@camLine.com writes:
Hi Alexandre,
anything wrong with this patch ?
Well, the resource id is 1, so loading it with 0x65 is certainly not going to work. Were you planning to change the resource too?
Hi,
looks like i was confused by LoadLibraryEx. I found now that when buildin and native version of a dll are present and nothing for the load order is specified LoadLibraryEx loads the buildin version as long as LOAD_LIBRARY_AS_DATAFILE is not specified. But when LOAD_LIBRARY_AS_DATAFILE is specified it loads the native version.
Can this behavoir be change to load the same dll independend of LOAD_LIBRARY_AS_DATAFILE ?
Bye Stefan
Stefan Leichter Stefan.Leichter@camLine.com writes:
looks like i was confused by LoadLibraryEx. I found now that when buildin and native version of a dll are present and nothing for the load order is specified LoadLibraryEx loads the buildin version as long as LOAD_LIBRARY_AS_DATAFILE is not specified. But when LOAD_LIBRARY_AS_DATAFILE is specified it loads the native version.
Can this behavoir be change to load the same dll independend of LOAD_LIBRARY_AS_DATAFILE ?
It can, but it's not clear that it should, LOAD_LIBRARY_AS_DATAFILE doesn't make much sense on a builtin. Anyway, the resources should be compatible, if they aren't that's a bug in the builtin.
Alexandre Julliard schrieb:
Stefan Leichter Stefan.Leichter@camLine.com writes:
looks like i was confused by LoadLibraryEx. I found now that when buildin and native version of a dll are present and nothing for the load order is specified LoadLibraryEx loads the buildin version as long as LOAD_LIBRARY_AS_DATAFILE is not specified. But when LOAD_LIBRARY_AS_DATAFILE is specified it loads the native version.
Can this behavoir be change to load the same dll independend of LOAD_LIBRARY_AS_DATAFILE ?
It can, but it's not clear that it should, LOAD_LIBRARY_AS_DATAFILE doesn't make much sense on a builtin. Anyway, the resources should be compatible, if they aren't that's a bug in the builtin.
Ok,
i will send a patch to make the name of builtin resource compatible with the native one.
-- Bye Stefan
ChangeLog --------------- changed name of the REGISTRY resource to the one of the native dll
Am Dienstag, 30. August 2005 12:09 schrieb Stefan Leichter:
Alexandre Julliard schrieb:
It can, but it's not clear that it should, LOAD_LIBRARY_AS_DATAFILE doesn't make much sense on a builtin. Anyway, the resources should be compatible, if they aren't that's a bug in the builtin.
Ok,
i will send a patch to make the name of builtin resource compatible with the native one.