Create DLL stub files in c:\windows\system

[Andreas Mohr]

Hi,

On Tue, Sep 07, 2004 at 09:58:44AM +0100, Mike Hearn wrote:
> >It's not that the app wants the dll to be empty, it's that it can deal
> >with the file not being there at all, but it can't deal with the file
> >being there but empty (since that would never happen on Windows). So
> >in many cases creating empty files makes things worse than not having
> >the files at all.
> 
> What would the app do if it found the DLL but it was empty? Do you mean 
> that it maps it and rummages around the headers manually?
> 
> Well, we seem to be in a bit of a quandry then. Some apps require the 
> DLLs to be physically present, and others can't deal with it if they are 
> but empty. So the only solution seems to be to actually have real PE 
> DLLs in the virtual windows drive, but this would mean huge changes to 
> Wine.
> 
> Hmmm. What about if the files aren't empty, but just contain the headers 
> - would that make the apps you're thinking of happy?
Probably. That's why I wrote a helper to create full-featured NE/PE file
headers already more than 4 years ago, before my Codeweavers internship,
but it got lost when I accidentally deleted that Wine tree instead of
the local one (the one right there in the terminal window instead of
the one about some 5000 miles away in the other terminal window ;-).
I just said something like "oops, that surely must have been wrong". ;-\
Needless to say I didn't feel too inclined to recreate the tool from scratch
at that time, and I didn't bother later either.

It'd be cool if you actually did it now - just make damn sure to not make
the mistake of deleting the wrong Wine tree ;-)

Andreas Mohr