On 13/10/06, Alan McKinnon <alan@xxxxxxxxxxxxxxxxxxx> wrote:
Here's what I do: Maintain a ~/.wine without winetools Maintain a ~/.winetools with winetools
Sounds reasonable.
If software won't install in .wine but does in .winetools, then start comparing the two to find relevant differences and move them into .wine
Easier said than done, at my expertise level.
More often than not the setting that will make something work is a dll override. Yes, you need to hunt to find cures. Yes, it's hard work. Yes, you will pull your hair out sometimes. This is not wine's fault - the project is successfully doing the (almost) impossible but it will always be somewhat of a round peg and square hole problem. Someone needs to do these comparisons and report up which wine functions now work and do not need the winetools workaround anymore, that person might as well be you :-)
As soon as I finish my degree in mechanical engineering, I'll go get one in computer sciences.
Meanwhile, you need to upgrade wine like Dejan suggested. Your version is 15 months out of date.
I was actually on the latest, and downgraded at Jocheam's suggestion. Hey, what do I know? Thanks. I'll see what I can manage without winetools. Always good to learn. Dotan Cohen http://what-is-what.com/ http://essentialinux.com/ _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
