http://bugs.winehq.org/show_bug.cgi?id=2944
Speeddymon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1
------- Additional Comments From Speeddymon@gmail.com 2005-06-05 22:07 ------- Hi. First off, I want to say congratulations for fixing your problem before one of us even got a chance to respond :) . To answer your 2nd question..
Basically the .dll.so you are seeing is not a native Windows DLL. It is a DLL created by the wine developers to replace the native one so that you can run the programs in wine. There are bugs, which is why wine doesn't have an official versioning system (yet), and as such, copying DLL's from a native windows install will not _always_ work, even though it did in this case.
Your best bet for now is to copy the original DLL's like you did to the wine DLL's directory, leaving them named as they are, and then edit your wine config/wine registry to tell wine to use the native DLL's instead of the builtin ones. See the wine users' guide for that.
What you also may want to do is send a note to the wine developers requesting someone to start working on a builtin (linux/wine) version of those DLL's that are required to run the program. That way, since you have the program, you can help them bugfix them as time goes on. The first versions of the DLL's will probably not work at all, and require you to help the developers do a lot of debugging to figure out exactly which routines are needed to get it working, but it will be a step in the right direction.
Now don't be surprised if the developers dont get started right away, they have your request in queue, and of course "Your call will be taken in the order in which it was received" ;-). Hope this info helps.
Resolving as the issue being reported was fixed by the user. Please feel free to file a separate bug about the non-builtin DLL's.
-
Wine Bugs