d3dx9 and other dlls are copied to the wrong location for a shared wine wow64 build

[GoogleCodeExporter]

1. run the 32bit wine from the wow64 build like "WINE=~/wine32/wine sh
winetricks d3dx9"
2. the d3dx9*.dlls got copied into system32 directory, it should be syswow64
3. the 32bit executable which is run like "~/wine32/wine Crysis.exe"
(32bit) isn't able to find the correct dll (it uses only wines build in ones)

wintricks 20100317
Fedora 12 64bit
wine shared wow64 setup http://wiki.winehq.org/Wine64

Copying the dlls manually into syswow64 solves the problem.

Attached is a hacky workaround.

PS: However there is another problem, since winetricks garbles the prefix
and 64bit apps shouldn'd be able to access the dlls in system32 because
they would expect 64bit ones and not 32bit versions. (I haven't tried this
one!)

Original issue reported on code.google.com by gurket...@googlemail.com on 10 Apr 2010 at 9:51

Attachments:

• winetricks.diff

[GoogleCodeExporter]

This happens for pretty much all DLL's. I'll look into it.

Original comment by austinenglish@gmail.com on 11 Apr 2010 at 5:54

[GoogleCodeExporter]

More a note to self, but these verbs fail in a wow64/32 shared build:
# dotnet11
# gecko
# gecko-dbg
# ie6
# msmask
# msscript
# msxml6
# richtx32
# vcrun2003
# vjrun20
# wme9
# wmp9
# wmp10
# wsh56
# wsh56js
# wsh56vb
# xact
# xinput

Original comment by austinenglish@gmail.com on 21 Oct 2010 at 7:17

[GoogleCodeExporter]

More a note to self, but these verbs fail in a wow64/32 shared build:
# dotnet11
# gecko
# gecko-dbg
# ie6
# msmask
# msscript
# msxml6
# richtx32
# vcrun2003
# vjrun20
# wme9
# wmp9
# wmp10
# wsh56
# wsh56js
# wsh56vb
# xact
# xinput

presumably the installers know about win64 and want to install that version 
instead.

Original comment by austinenglish@gmail.com on 21 Oct 2010 at 7:20