The Win95 advapi32 cannot work, but the NT one can.
Is there ever a time when we would want to use the native NT advapi32? I just sent a patch to make sure only the builtin advapi32 gets loaded, so that probably won't be committed if this is the case.
On Thu, 30 Sep 2004 10:16:26 -0700, Alexandre Julliard julliard@winehq.org wrote:
James Hawkins truiken@gmail.com writes:
err:vxd:VMM_VxDCall Using the native Win95 advapi32.dll is no longer supported. err:vxd:VMM_VxDCall Please configure advapi32 to builtin.
If we don't want any user using a native advapi32.dll no matter what the circumstances, shouldn't the default override for advapi32 be *advapi32=b (no matter whether it's in a config file or the registry or whatever)?
The Win95 advapi32 cannot work, but the NT one can.
-- Alexandre Julliard julliard@winehq.org