rvp There are two types of dlls to mind, when talking about WINE.
There is "native" and "built-in". WINE can use both; however the ones you mentioned can only work using WINE's "built-in" dlls. The actual Windows "native" dlls, core system files, cannot work. WINE can allow you to preference which dlls are used, in the case of none core system dlls. It can even try one, and then fall back to the other.
In this instance, WINE's "own provided" dlls cannot be found. I hope that this clears it up. The dlls I am referring to, are dlls included within the WINE package. They are built with, and part of, WINE. It is a normal, expected, and required part of WINE's functionality.
But, yes, the application does work on Linux WINE.
If you were to use the windows application "Dependancy Walker" you would find that all of the dlls you listed are heavily depended on.
WINE also provides many non core dlls, and over the years this has become fairly complete.
This is another problem with this WINE port, working on NetBSD. However, after seeing the fix you first pointed out, I cannot say it this is a problem with this port of WINE, or with NetBSD (at least in i386).
I imagine the issue with the 64bit port, would be 32bit application installers. That was an issue with Linux, too. But WOW64 has come a long way.
This new problem, on the surface, seems like an issue of locating the dlls (thats the actual error). I checked the WINE path, and everything looked good there. Example: "wine cmd" and then "echo %PATH%". WINE's dlls (the ones it lists not being about to find) are populated in .wine, where they should be.
Is anyone using the 64bit port? It would be nice to know if it is an issue there, too.
