Re: Running dxdiag
Hi Mike, Dumping the headers is necessary for stupid installers that map DLL files manually and rummage around in the headers to figure out versions and stuff ... simply having an empty file isn't enough for all of them I'm afraid :( This isn't enough for new installers, either :( I have an MSI-based InstallShield installer that's looking for shdocvw.dll to see if IE6 is installed. (It isn't, but that's how it's looking for it.) Trouble is, how would this work with the native/builtin thing? Right now all our builtins don't live in the system directory, so we can always override whatever native dll happens to get dropped there. If we put a little stub PE header in there, what's to stop an installer from overwriting it? Or, would this cause a problem? --Juan __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail
Re: Running dxdiag
--- Mike [EMAIL PROTECTED]: Well, if the little stub is overwritten by a correct native DLDLLhen there is no problem at all. If some install overwrites it with an older version than what apps expect (or Wine provides) then that might be a problem, but that's just the generic DLDLLell the windows library design implies. Windows XPXPas this nice new feature of Side-by-Side AsAssemblieshat is a .Net concept. It combined with Windows File Protection has in effect ended DLDLLell. Maybe we should look at implementing some sort of side-by-side system in Wine. Thanks Steven __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250
Re: Running dxdiag
Somebody needs to write a program that dumps the NT headers of each winelib DLL to the appropriate place in the virtual drive C when it's first created (in wineprefixcreate). Why can't wineprefixcreate just make links to the dlls? Ivan.
Re: Running dxdiag
On Fri, 14 Jan 2005 19:33:19 +0100, Ivan Leo Puoti wrote: Why can't wineprefixcreate just make links to the dlls? Like I said originally: Dumping the headers is necessary for stupid installers that map DLL files manually and rummage around in the headers to figure out versions and stuff ... simply having an empty file isn't enough for all of them I'm afraid :( The DLLs wine ships aren't actually PE DLLs so symlinking to them directly won't do the trick.
