http://bugs.winehq.org/show_bug.cgi?id=24924
--- Comment #21 from Jeff Zaroyko jeffz@jeffz.name 2010-10-30 16:46:01 CDT --- (In reply to comment #20)
Sorry about all these posts. It turns out that windows restores mfc40.dll in "c:\windows\system32" after I delete it or replace it with another file...
I guess I cannot reliably test it this way...
For future reference:
http://wiki.winehq.org/FAQ#head-3b297df7a5411abe2b8d37fead01a2b8edc21619
Many applications don't bother to check their own cwd, since 99.999% of the time they are started via a shortcut on Windows which specifies the working directory to be automatically set when the executable is run. Or if they are launched from explorer then the working directory is the folder that is open/displaying the executable which you've clicked on.