On Sat, 31 Aug 2002, Jas Sandys-Lumsdaine wrote:
Some application will work better with the native (Windows) libraries, and some others with the builtin (Wine) libraries.
Assuming native Windows dlls etc are correct (by definition of what Wine's APIs are trying to copy), doesn't this imply the Wine framework (excl. built in dlls) still has issues.
Otherwise, what else could be going wrong when an app fails to run?
Windows libraries (e.g. comctl32, shlwapi, etc) use other libraries (e.g. user32, ole32, etc). So if you use the Windows shlwapi library you may end up making calls to the ole32 or user32 library which are not yet completely implemented, especially if it is an undocumented API.
Obviously Wine libraries tend not to call undocumented and/or unimplemented APIs in other libraries, thus sometimes resulting in better behavior.
You will say "why not use only Windows libraries then?" Simply because for some libraries it is not possible. user32.dll is one such library, ntdll.dll, kernel32.dll, socket libraries, sound libraries and DirectX libraries are some others.
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds