Total Annihilation in bin32-wine on Arch 64: won't start

I can't run Total Annihilation on bin32-wine. When I try to start it I get:
$ wine totala.exe 2>&1 | tee ~/log.txt
fixme:system:SystemParametersInfoW Unimplemented action: 94 (SPI_GETMOUSETRAILS)
fixme:system:SystemParametersInfoW Unimplemented action: 93 (SPI_SETMOUSETRAILS)
fixme:win:EnumDisplayDevicesW ((null),0,0x33eb50,0x00000000), stub!
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 32 to 8
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x137d28,0x137c70): stub
wine: Unhandled page fault on read access to 0x00000000 at address 0x4ce556 (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 001a), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 001c), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 001e), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0020), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0022), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0024), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0026), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0028), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 002a), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 002c), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 002e), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0030), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 0032), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0034), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0036), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0038), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 003a), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 003c), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 003e), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0040), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0042), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0044), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0046), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 000b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0049), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 004b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 004d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 004f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0051), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0053), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0055), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0057), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0059), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 005b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 005d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 005f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0061), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0063), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 0065), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0067), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0069), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 006b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 006d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 006f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0071), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0073), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0075), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0077), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0079), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 007b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 007d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 007f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0081), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0083), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0085), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0087), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0089), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 008b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 008d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 008f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0091), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0093), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0095), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0097), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0099), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 009b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 009d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 009f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00a1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 00a3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00a5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 00a7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00a9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00ab), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00ad), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 00af), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00b1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00b3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 00b5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00b7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00b9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00bb), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00bd), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00bf), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 00c1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00c3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00c5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00c7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 00c9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00cb), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00cd), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00cf), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00d1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00d3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 00d5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00d7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00d9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00db), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00dd), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00df), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00e1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00e3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00e5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00e7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 00e9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 00eb), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00ed), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 00ef), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00f1), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00f3), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00f5), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00f7), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00f9), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00fb), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00fd), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 00ff), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0101), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0103), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0105), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0107), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0109), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 010b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 010d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 010f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0111), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0113), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0115), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0117), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0119), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 011b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 011d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 011f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 0121), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0123), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0125), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0127), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0129), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 012b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 012d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 012f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0131), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf0384 (thread 0133), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0135), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0137), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 0139), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 013b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 013d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 013f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebf1384 (thread 0141), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0143), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0145), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe5384 (thread 0147), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0149), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 014b), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 014d), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 014f), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0151), starting debugger...
wine: Unhandled page fault on read access to 0x00120024 at address 0x7ebe6384 (thread 0153), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] | <num> | file.mdmp | --help ]
and then nothing happens, it exits, and my screen resolution is changed to something really low.
I had it working perfectly on wine in Slackware a couple of months ago so this regression is really fustrating. Anyone have any ideas?

Similar Messages

Arch won't start , probably due to Catalyst

Hello,
I have a small (Big) problem on my computer , that probleme made me whype my HDD thrice for now , because like said in the title my ARCH setup won't start , so here is the problem : The loading is stuck after those few lines :
//Talking about the number of blocks in /dev/sda3
[ OK ]Reached dhcpcd on eno1
[ OK ]Reached target Multi-user system
[ OK ]Reached target Graphical Interface
[ OK ]Reached target Network
The things I know about this problem :
-First happened when installing Catalyst
-I did a very small install with the base / base-devel / skype / gnome / gnome-extra / xorg and the Unoficial catalyst repo (I think I forget nothing ...)
-It happened with or without xf86-video-ati
-It is stuck there. It won't let me do anything
-Due to the xorg116 bug with catalyst I used the unofficial xorg115 repo each time
Unfortunately each time I did a
systemctl enable gdm
so I can't do any test.
Anyone has a clue of what is happening ? I tried using lxdm for example , but since it did not work very fast , I did not use it , and I had forgoten to add Catalyst that time.
So should I stick with the xf86-video-ati , use lxdm (or an other display manager) or do another thing ?
Last edited by traxys (2014-08-25 16:43:54)

So know , with tying to use the startx command I think I can say that the problem is not GNOME but the drivers ....
Because startx crashed , and the log (http://pastebin.com/tTndn5ep) complains about a "dri3" module that is not found (look at about line 610)
This is a more problematic thing I think
And by the way I don't have the package xorg-twm
EDIT : just saw this :
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58f186]
(EE) 1: /usr/bin/X (0x400000+0x192fc9) [0x592fc9]
(EE) 2: /usr/lib/libpthread.so.0 (0x7f7ef5074000+0xf4b0) [0x7f7ef50834b0]
(EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7ef08b1000+0x155b5) [0x7f7ef08c65b5]
(EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7ef08b1000+0x127dcf) [0x7f7ef09d8dcf]
(EE) 5: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxPxFreeScreen+0x2e) [0x7f7ef13990ee]
(EE) 6: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxFreeScreen+0x64) [0x7f7ef13777d4]
(EE) 7: /usr/bin/X (xf86DeleteScreen+0x5a) [0x47fe8a]
(EE) 8: /usr/bin/X (InitOutput+0xacf) [0x47950f]
(EE) 9: /usr/bin/X (0x400000+0x3ab2a) [0x43ab2a]
(EE) 10: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f7ef3cde000]
(EE) 11: /usr/bin/X (0x400000+0x250fe) [0x4250fe]
(EE)
(EE) Segmentation fault at address 0x14
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
Saw ther is an interaction between intel and ati that goes nuts ?
Last edited by traxys (2014-08-25 19:31:59)

Wine on Arch 64

I cannot get wine working correctly on Arch 64. I am having problems getting some of the required packages that are lib32. I cant get them with pacman. Also I am thinking since wine doesnt have a 64 bit edition I should just go with 32 bit arch.

Lugz wrote:I am having problems getting some of the required packages that are lib32. I cant get them with pacman. Also I am thinking since wine doesnt have a 64 bit edition I should just go with 32 bit arch.
32-bit libraries which "wine" depends on can be found on AUR. Though I got all of those from repositories.
Did you get "wine" from AUR? A package from AUR contains a prepared list of dependencies so you should not normally conjecture which libraries you miss. I personally use "bin32-wine-suse" by ProfessorTomoe http://aur.archlinux.org/packages.php?ID=16531 so can speak only for it.

[SOLVED]Wow in bin32-wine-wow-hardware-cursor need help with patching

Hi all.
I have installed bin32-wine-wow-hardware-cursor from AUR and it's working pretty fine I must say. I still have one important issue. That is, that the cursor acts strange when holding the button pressed down, as you do when turning etc. The cursor then moves to the middle of the screen and shakes, until you release the button.
There is a fix for this posted on the Ubuntuforums, but I don't know how to implement this in Arch. Trust me, I have tried in so many ways possible, but I don't have the knowledge to do this. Please help me, or point me in the right direction.
http://ubuntuforums.org/showpost.php?p= … tcount=172
I have managed to fix this problem myself. If any of you are wanting the same functionality as what i mentioned above, navigate to your mouse.c find the function update_mouse_state, and then make the changes below...
static void update_mouse_state( HWND hwnd, Window window, int x, int y, unsigned int state, POINT *pt )
struct x11drv_thread_data *data = x11drv_thread_data();
char *hwgl;
get_coords( hwnd, window, x, y, pt );
hwgl = getenv("WINE_CURSOR");
/* update the cursor */
if (hwgl == NULL){
if (data->cursor_window != window)
data->cursor_window = window;
wine_tsx11_lock();
if (data->cursor) XDefineCursor( data->display, window, data->cursor );
wine_tsx11_unlock();
Thank you in advance.
EDIT: To clear things out a bit. I am using 64-bit Arch.
Last edited by n4h0j (2010-05-03 20:55:26)

n4h0j wrote:
itsbrad212 wrote:
n4h0j wrote:
Thx for the reply.
However, I don't think that one includes the right patch either. That just looks like the 32-bit version of the bin32-wine-wow-hardware-cursor. And I cannot install that on my system.
When talking about cursor issues there are 2.
1. Getting hardware cursor in OpenGL.
2. Irritating cursor-behavior when pressing down the buttons to turn etc.
The package you refer to solves problem #1, so does the bin32-wine-wow-hardware-cursor. It's problem #2 that need fixing. I would assume, since it is just a cosmetic defect, no one else has bothered before me.
But still, it's solvable in Ubuntu, and I am kind of a perfectionist.
EDIT: Yes, I can see now that the mouse.c is in the archive. I would be able to edit myself. But (silly question) I won't be able to run the PKGBUILD with that source, right?
Well, you could always edit the file then re-tar/bzip it.
The PKGBUILD wiki article states:
Note: If you need to supply files which are not downloadable on the fly, e.g. self-made patches, you simply put those into the same directory where your PKGBUILD file is in and add the filename to this array. Any paths you add here are resolved relative to the directory where the PKGBUILD lies. Before the actual build process is started, all of the files referenced in this array will be downloaded or checked for existence, and makepkg will not proceed if any are missing.
So basically, edit the PKGBUILD and set the source to the location of the newly bziped file you have after applying the patch. Then it should use that one instead
But, that won't be possible on a 64-bit system, right? I can't use the 32-bit source.
Or am I missing some piece of the puzzle here?
I think I'm missing part of the puzzle....
Ok, title of thread: "bin32-wine-wow-hardware-cursor"
That makes me assume 32-bit
Next, source file you downloaded:
wine-wow-hardware-cursor-1.1.43-1-i686.pkg.tar.gz
Again, 32-bit...
I'm confused with what you want now
Last edited by itsbrad212 (2010-05-03 07:17:47)

Bin32-wine vs 32-bit chroot environment

I run Arch x86_64 with bin32-wine for all of my windows applications, however I was wondering if there are any advantages (compatibility, speed, etc.) to running a 32-bit chroot environment for all of my 32 bit apps (which would only be wine).
Currently I only use wine for Office 2007, however I would like to run Deus Ex and Starcraft (maybe others in the future), and I'm currently unable to get Starcraft running. Deus Ex runs in windowed mode with safe mode on, but very poorly.
System specs:
ASUS UL30A U7300 dual core 1.3 GHz
4 GB DDR3
Intel GMA4500 MHD graphics
Any thoughts on this? Thanks in advance

I see.......thank you for the response. I wondered if I had to compile for the chroot or simply use pacman -Syu. That is indeed a large advantage.
I went ahead and completely wiped bin32-wine, all of the dot files, and reinstalled Office 2007, Starcraft, and Deus Ex. That fixed a bug in Office (files with space in file path not opening correctly from dolphin/konqueror/etc).
I also discovered that one of my problems with my games was that I somehow missed a few packages related to opengl. I stll wasn't able to get Deus Ex working just yet.....
I may go ahead and do the chroot, as that seems like an easier way of doing things after the initial setup.
If anyone has anymore input I would be grateful to hear it.

[solved] Office 2007 bin32-wine-suse Problems

I installed bin32-wine-suse from the AUR and then installed Office 2007 per the wiki. I can run applications but I cannot move or resize windows. Any ideas?
Last edited by rbn14 (2010-03-17 02:22:49)

Wow, don't I feel like a turd Thanks, worked perfectly!

64bit and bin32-wine error

I am using Arch64. I installed bin32-wine from both archlinuxfr repo and AUR. But everytime wine did not work.
and
$ winecfg
Could not load wine-gecko. HTML rendering will be disabled.
err:module:load_builtin_dll failed to load .so lib for builtin L"msxml3.dll": libxml2.so.2: wrong ELF class: ELFCLASS64
wine: configuration in '/home/kan/.wine' has been updated.
fixme:jack:JACK_drvLoad error loading the jack library libjack.so.0, please install this library to use jack
err:module:load_builtin_dll failed to load .so lib for builtin L"wineesd.drv": libesd.so.0: wrong ELF class: ELFCLASS64
How can I fix this?

OKAN wrote:$ winecfg
fixme:jack:JACK_drvLoad error loading the jack library libjack.so.0, please install this library to use jack
err:module:load_builtin_dll failed to load .so lib for builtin L"wineesd.drv": libesd.so.0: wrong ELF class: ELFCLASS64
Building/installing the AUR package lib32-esound will address the libesd.so.0 error. http://aur.archlinux.org/packages.php?ID=22826.
You can use one of the many AUR helper applications to download, compile and install if you like.

[SOLVED]bin32-wine 1.1.1 opengl error

Trying to start counter-strike 1.6 on arch64 I get the error
Error initializing gl driver, check that the file 'opengl32.dll' exists
Using xf86-video-intel driver, direct rendering enabled. Used to work with older versions of wine, but no longer...
Last edited by low (2008-07-20 11:58:43)

ok fixed, i installed perfect world to see if it a steam specific error, and it was not, but i got a lot more readable output from the perfect world launcher. turns out lib32xdamage was not installed and is a dependency.... not listed in bin32-wine or the bin32-wine-suse PKGBUILD....

Bin32-wine with srgbtexture patch

Hey there,
it would nice to have a PKGBUILD for bin32-wine with srg texture patch (http://bugs.winehq.org/show_bug.cgi?id=12453)
S.b. could provide it?
thanks

I see.......thank you for the response. I wondered if I had to compile for the chroot or simply use pacman -Syu. That is indeed a large advantage.
I went ahead and completely wiped bin32-wine, all of the dot files, and reinstalled Office 2007, Starcraft, and Deus Ex. That fixed a bug in Office (files with space in file path not opening correctly from dolphin/konqueror/etc).
I also discovered that one of my problems with my games was that I somehow missed a few packages related to opengl. I stll wasn't able to get Deus Ex working just yet.....
I may go ahead and do the chroot, as that seems like an easier way of doing things after the initial setup.
If anyone has anymore input I would be grateful to hear it.

[Solved] Project64 (which runs via wine) won't start w/ an error

I'm on 64 bit arch laptop trying to run project64, but the app won't start. I installed project64 from the repo and it pulled wine as a dependancy. Upon firsst-run I was prompted to install wine gecko and hit the install button. This froze and I force-closed the window which then prompted me to select a language. I got a "Program Error" message saying that pj64 encountered a serious problem and needs to close. I then found and installed the wine_gecko package, but this didn't solve the problem.
The console outputs the following:
wine: Unhandled page fault on read access to 0xffffffff at address 0x7cdb9eda (thread 0009), starting debugger...
Someone please help me.
Last edited by vectorman (2011-08-12 22:11:25)

Make sure you have the correct lib32 drivers for your graphics card, since wine is a 32 bit app. For example,m for nvidia you need the lib32-nvidia-utils package. This seems to be more of a general Wine issue rather than an issue with project64 though, but hopefully installing the correct package should help. I maintain the project64 AUR package though, so I feel like I should do my best to help, and possuibly imporve my package too if something's wrong with it Also, if that doesn't work, try running this, it will give more terminal output that could be useful (by default it uses WINEDEBUG=-all to get rid of the extra debug info and stuff wine outputs by default, but it might be helpful here):
wine "$HOME"/.project64/Project64.exe
Also, IMO, all the Mupen64plus frontends seem to be kinda crappy right now (cutemupen crashesd so I can't even try that one out...), but the one I'va had the best luck with is wxmupen64plus-hg, so give that a shot, though it does still have some issues sometimes, but it lets you configure the controllers and stuff, so that's good And if you felt like using it, you could install version 1.5 (it's in AUR too, but I haven't tested it), since version 1.5 has a GUI and it always worked great when I used to use that
Last edited by doorknob60 (2011-08-12 06:09:19)

Do I need to do a total reset on my 3gs so that it won't keep updating every time it gets near my 4gs?

Do I need to do a total reset on my 3gs so that it won't keep updating every time it gets near my 4gs? I've created a separate ID to use with the 3gs already.
Help...
Thanks!

delores a wrote:
Do I need to do a total reset on my 3gs so that it won't keep updating every time it gets near my 4gs?
It has nothing to do with "getting near: the other iPhone.
They are using the same AppleID for iCloud.
On the 3GS, Setttings > icCloud, delete the iCloud account and turn it on using the new AppleID.
Whatever I have changed on my 4S...notes, apps..etc.
Settings > iTunes & App stores.
Tap your ApleID, sign out then sign in with new AppleID.

TS2529 I am unable to backup my iphone 5 iOS 6.0.1 (connected directly to laptop USB) with my itunes 11 for Win 7 64bits. The process starts and fails to complete giving the error: itunes could not complete backup of iphone because iphone disconnected.

I am unable to backup my iphone 5 iOS 6.0.1 (connected directly to laptop USB) with my itunes 11 for Win 7 64bits. The process starts and fails to complete giving the error: itunes could not complete backup of iphone because iphone disconnected.
I have restarted the PC, the iphone, changed the lightining cable and nothign resolves it: backup never completes.

Hi, I disabled the antivirus and the firewall. Same result
I even deleted the backup folder inside C:\Users\...\Apple Computer\MobileSync\Backup to eliminate any corruption in the old backup files.
Nothing changed: Session either times out or i get the same error message: itunes could not back up iphone because iphone disconnected. It always happens during step 3 out of 4 which is "transfering purchased apps from iphone to PC" and comes after step 2 which is backup.
My iphone 5 is not jailbroken, and is a factory unlocked phone.
Any other suggestion?
Pls help

I have an iPod Touch 3rd gen and while it is recognized by my laptop with Win 8.1, it won't sync with iTunes.

I have an iPod Touch 3rd gen and while it is recognized by my laptop with Win 8.1, it won't sync with iTunes. It worked fine while my laptop had Win 8 but after the update, it quit syncing. Strange though, I downloaded an app directly to my iPod and when I connected it to my laptop again (for recharging if nothing else), iTunes updated itself by including the new app. I also tried syncing wirelessly. Also unsuccessful. I'm about ready to change to an alternate to iTunes if I can't get this situation fixed. Anyone else have this problem and/or a solution?

See
iOS: Device not recognized in iTunes for Windows
- I would start with
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
However, after your remove the Apple software components also remove the iCloud Control Panel via Windows Programs and Featurs appin the Window Control Panel. Then reinstall all the Apple software components
- New cable and different USB port
- Run this and see if the results help with determine the cause
iTunes for Windows: Device Sync Tests
- Try on another computer to help determine if computer or iPod problem

HOW TO FIX HD AUDIO/UNKNOWN DEVICE/DEVICE WON'T START LENOVO H320 Win 7 64-bit

Fix for - HD Audio devices won't start or you can't load correct driver. Lenovo H320 - Win 7 64-bit I-3 processor. 5 series/3400 chipset
Here is a working procedure to fix the problem when you install windows 7 64-bit and can't get the correct drivers installed for the HD Audio devices 1)Realtek AC97 HD Audio device id = HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_17AA3604&REV_1001
and 2)Intel HD Audio device id = HDAUDIO\FUNC_01&VEN_8086&DEV_2804&SUBSYS_80860101&REV_1000 Regards >>> Sucromatic
For an IBM LENOVO 320 with Windows 7 64-bit Home Premium Version download these drivers to a directory in a second partition to prevent this nightmare from happenning in the future.
1)AC 97 high def audio version
Realtek HDA 2.67found on http://wikidrivers.com/wiki/Main_Page or at www.realtek.comon right of screen on homepage and
2) Intel HD GRAPHIC and HD Audio version
Intel GMA 15.22.52.2559 (Vista/7) 14.46.8.5387 (XP)
found on
http://wikidrivers.com/wiki/Main_Page.
Select your OS and and whether 32 or 64 bit. I recommend the .exe version as it works very smoothly. Uninstall HD AUDIO DEVICE or whatever it is called maybe "unknown device" with ac97 device ID "HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_17AA3604&REV_1001." Afterwards install AC 97 HD Audio Driver.
After install reboot and wait till computer completely starts.
Now uninstall Intel HD Graphics or your graphics device. When you get the uninstall box open, select delete the driver software for this device and then OK. When prompted to reboot select NO and Immediately start the install of the Intel GMA driver. Which installs both the Graphics Adapter and the Intel HD Audio. Reboot when finished and all HD Audio devices will be functional (hopefully). You will now have these versions installed. As shown in device manager/device properties/Driver tab
Now uninstall Realtek AC97 driver you first installed to delete annoying Red Lexmark/realtek icon in Notification area (If your computer shows it after reboot) and windows driver update will install a microsoft driver (shown below)that works without the stupid lexmark red icon. See below. You will now have these versions installed. As shown in device manager/device properties/Driver tab
High Definition Audio Device
Driver Provider: Microsoft
Driver Date: 11/19/2010
Driver Version: 6.1.7601.17514
Digital Signer: Microsoft Windows
IntelR) HD Graphics
Driver Provider: Intel Corporation
Driver Date: 1/10/2012
Driver Version: 8.15.10.2622
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Intel (R) Display Audio
Driver Provider: Intel(R) Corporation
Driver Date: 8/23/2011
Driver Version: 6.14.0.3086
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Voila. Now go to intel and run a driver update scan and it will likely correctly identify your Intel pieces and offer downloads for any that are not current. Good Luck!

it is a user to user forum without any intervention from apple information-wise.I think this question appears and being discussed in another thread
http://discussions.apple.com/thread.jspa?threadID=2411685&tstart=0

11g DB Control service won't start on Win XP Pro

Hi all,
In installing my 11g database, the DB Control service won't start so the database config fails prior to doing the EM stuff. The system event viewer says:
The OracleDBConsoleorcl11p1 service terminated with service-specific error 2 (0x2).
Querying further, I find the following:
SERVICE_NAME: OracleDBConsoleorcl11p1
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1066 (0x42a)
SERVICE_EXIT_CODE : 2 (0x2)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Researching the error code 1066 simply says it is a vendor-specific error code. Anyone out there ever come across such a thing?
Cheers,
Jim Greetham

Jim,
Were you able to figure out the problem why you were getting 'service specific error occurred:2'?
I have the same issue.
DB version: 11.1.0.6.0
OS: Win XP (latest patches and updates applied)
The database and other pieces are working just fine.
Thank you,
Taj

Total Annihilation in bin32-wine on Arch 64: won't start

Similar Messages

Maybe you are looking for