https://bugs.winehq.org/show_bug.cgi?id=45212
--- Comment #13 from Dave gcos7@yahoo.com --- Nope - don't know anything about it and never claimed I did. It just seems to me that SOMETHING in wine is intercepting this even with the replacement dll. Why? Because the developer says it runs fine in Windows XP on up. It obviously doesn't work in wine. So again it comes back to the message about the call to get the pallette - which I do know actually contains all kinds of information about the image - fails on type 3 not being implemented. This causes the connection error since nothing is returned about the image - it returns a null pointer.
I don't have access to a Windows Xp, Windows 7 or Windows 8 installation media to try to extract the dll from. Obviously Windwos 10, and perhaps earlier, uses their own mini-xp environment to run XP programs.
I downloaded the dll from ddl-files.com as that was where I was told a reliable image could be found. I am aware of the inherit dangers in downloadeing from unknown sources, but in this case I'm only trying to help someone else. I can remove everything wine when this is over.
I'm just looking for a way to solve this. I am not alone in this problem - it's both in the wine forums, ubuntu forums and on the net about people having this error about the connection - which I would bet is prefixed by the type 3 not implemented and thus null pointer error. A lot of these are games, some are other applications.
I would REALLY hate to do it, because I've seen the source and all the pieces that have to be found and included to build wine, bhat in desperation one could always load in the sources for wine and run a search on each one looking for OLEPicture - that onto itself might provide some information. But what about the developers of the wine dll? Seems to me they should be able to trace the error back.