http://bugs.winehq.org/show_bug.cgi?id=12743
--- Comment #6 from Justin Soulia rockinup1231@gmail.com 2008-04-23 18:06:56 --- (In reply to comment #5)
If all you're doing is silencing messages in terminal, please don't use native DLLs. Only use them to workaround *actual* problems.
Sounds like an OLE error, a +ole,+oledlg trace would probably be useful.
I was using it to try to solve a problem. I was assuming that using the native DLL fixed the issue.
Before having read the last post on here, I tried some other things. Like, installing dotnet20, corefonts, riched20, and vcrun2003 with winetricks to see if it made any difference running the program. My reasoning is that some newer versions of this app on the appDB mentioned installing the .NET Framework (which I understand, if it's needed, although I don't recall that being a requirement, it's probably a waste of time to bother with this app until support improves). It didn't make any difference.
So, after starting with a new .wine directory (to get rid of the .NET framework) I tried the +ole, +oledlg trace. It didn't produce any new info about ole, but I did notice something new (see attachment). This time when I installed it, and ran it, the program had to skip over some enviroment variables. I'm not 100% positive since I'm no WINE guru in any way, but I assume that's related to a registry error. If so, that would also explain classes that ole complains about not being registered, and thus be an issue where the installer registers what need be during installation. (So far, the times I have installed the program I didn't bother starting the installer from the terminal because it seemed to be working properly.)