- Going to edit 'architectural differences' soon. Too much information that is already stated elsewhere. Not sure it even requires its own subheading. T1nk3r3r (talk) 02:49, 18 July 2012 (UTC)
"A win64 WINEARCH is meant to be able to run 32-bit Windows applications as well as 64-bit ones."
Wine seems to treat empty folders as win64 prefix folders, making it confusing to create win32 prefixes in empty folders. It gives the error [wine: WINEARCH set to win32 but '/home/wine/photoshop' is a 64-bit installation]. Perhaps we should add a note about this? See this bugreport http://bugs.winehq.org/show_bug.cgi?id=29661 -- JKAbrams 14:35, 20 Jan 2012 (EDT)
Yup, feel free to add that note. --Svenstaro 12:24, 20 January 2012 (EST)
I have to wonder why the Arch packagers activate WoW64 at all. I might fathom some security benefit? I would think any competent linux user that has a 64-bit Windows app knows to compile from source(and from git). As easy as:
make configure --enable-win64 && make && make install. As far as I can tell from WineHQ: Wine WoW64 support is workable, but further work is low priority. T1nk3r3r (talk) 08:21, 31 July 2012 (UTC)
I resolve the problem with the sound on PulseAudio use of wine-multimedia from AUR
There is an effort to consolidate Pulseaudio support in the new Wine sound system, but it will take time.