Wine issues on slackware
 

I'm trying to get the Watchtower Library 2007 to work under wine in Slack 12. I tried the package 0.9.52. Eventually I discovered
winetricks vcrun2005 to fix the msvcr80.dll problem it barfed on
cd /home/dec/drive_c/windows/system32 stopped it barfing there
lndir ../../Program\ Files/Watchtower/MEPSCommon improved missing dll errors
winetools to install the msttcorefonts and a few other touch ups.
But it still barfs after the splash screen with noise on the rebar, x11drv, & font WINEDEBUG threads. It fails to draw the bounding box for the display
The error is that it can't shrionk a bounding box.

No other distro has these issues. The program is gold rated in the appdb and runs in Fedora 5 which I also have _with _no_tweaks_at_all_ from the desktop icon, where all the errors go to /dev/null.
http://appdb.winehq.org/objectManage...estingId=18656

I thought it might be video issues, but I reinstalled from scratch with DRI and 2200 FPS on glxgears and it's the same. I also tried a 0.9.52 source install,

I can spare you all the trouble:
There will be no rapture. What you are reading has been written by man. Get out of this cult, and spend your life doing something meaningful.

Despite my usual policy of intolerance, I'll throw in on this one.

I have noticed as well that Wine under Slackware is not Wine under most other distros. Programs that worked fine for me under 64-bit Kubuntu wouldn't work in the same version of Wine on Slackware. I suspect it has something to do with some libraries, although I have found that different packages of Wine give differing results as well. Ken Zalewski's package (www.linuxpackages.net) works differently with some programs than Samiel's (www.slacky.eu) which again is different from Robby Workman's (www.slackbuilds.org).

I have no clue what would make such a difference between the distros. If I did, I'd do a little digging and compiling until I had the answers.

Oskar - if you cannot add something useful to the thread, please refrain from posting. This is a technical issue with an app, not a reason to open a flame war.

Spinlock ./configure --help

wine really is a black box, it sometimes works and sometimes doesn't and there really is no clear logical explanation for why, at least sometimes, or most times.

Usually the thing I would do is try out different versions, if I use wine, which I don't like to, then I usually keep multiple versions of it around, just because support for some programs breaks between versions. Also on the AppDB make sure to read the install notes further down (scroll down), and to do them absolutely exactly as they are stated or it just won't work. It's magic :), black magic

I have the same problem.
Some simple app work fine in Wine. Some more complex app such like starcraft do not work.

Maybe it's my graphics driver issue. The error message shows that occurs in the intel i965_dri.so
The driver of intel i965GM X3100 is poor!

Well folks, at least I know my experience is not unique. Let me thank most of you for your comments. On the strength of them, I'm going to clear off and rebuild the kernel, taking a very good look at threading options. Then I'll go back to wine and try there. As someone who did LinuxFromScratch a couple of times I am very familiar with ./configure --help, but usually do it as ./configure --help |less. I'll be back with any change of results.

Try several different versions of wine : I'm running 0.9.39 for a while now because I use it to run Excel and fore some reason, when I upgrade wine to newer version, it tells me I need to reinstall Excel (reinstallation fails of course, otherwise it wouldn't be fun). If I revert back to my old 0.9.39 wine package, Excel starts again to work properly.

I'm no wine expert, but there were some threading changes recently enough in wine. This for one thing caused it to break with uClibc, and asks questions of the way the kernel and glibc were installed. uClibc is vainly trying to catch up.

It sounds like you may need to install the Visual C++ 2005 or 2006 redistributable files (2005 is vcredist_x86.exe). They are downloadable from Microsoft.

I noticed that on some distros like the *buntus that often WINE programs use separate wineprefix folders for every program. This makes sure special settings and replaced dlls don't affect other programs. Other than that, I am not sure what the main differences are.

For me, using the slackbuild to build WINE has given me a setup that works with most programs I run on it. However there are a couple that work better on Ubuntu.

As previously stated, sometimes you have to keep trying different versions of WINE as the newest isn't always the best (there are regressions sometimes). You might consider creating a entry at the AppDB if there isn't already one. Sometimes a WINE developer might help you if they find time (though the most popular apps usually get attention first).

Done. To get the splash screen in Slackware I
installed those files you mention.
Symlinked in all dlls in MEPSCommon into c:\windows\system32
fixed the Desktop icon
Loaded up winetools and installed all msttcorefonts
Tried on xorg's 'nv' and proprietary nvidia drivers (Another nightmare)
and wtlib 2007 barfs after the splash screen.
For the correct file versions, what you suggest is now best done by

winetricks vcrun2005 which downloads with wget & installs.

What galls me is that Fedora 5 needed none of this messing for the 2007 version. I was able to install the 2006 version in slackware, and that functions enough, but I lose the data from 2007.

I hope I'm not into recompiling glibc. How would one even find the configure line slack used for glibc?

Thank you!
So, he's using kernel headers-2.6.16. I wonder how wise that is.
There's been a fair bit of change since 2.6.16.
I'll go off and see.