Dmitry wrote:
> Do you see the problem? Kernel32.dll is loaded AFTER the whole
> initialization process while the initialization itself uses
> functions from kernel32 AND FROM OTHER dlls (such as registry
> functions from advapi32.dll).
I don't think this is a problem; kernel32.dll is special anyway,
and it isn't possible to use the native version is any case, so
we have kernel32 just as a part of the Wine core (libwine) itself.
This means that all kernel32 routines are available during startup.
Of course, you must not call routines from *other* DLLs, e.g. advapi32.
But registry functions don't count, the implementation of those must
sit in the innermost core anyway, while advapi32 contains only wrapper
routines to be used by applications ...
[ This is actually currently not quite implemented correctly, which is
why advapi32 doesn't build as stand-alone module. That should be
simple to fix, however. ]
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
