http://bugs.winehq.org/show_bug.cgi?id=59571 --- Comment #17 from Alex Henrie <alexhenrie24@gmail.com> --- (In reply to Antoine Le Gonidec from comment #14)
Then there is the problem of twice the storage space being required to generate the WINE prefix, while half of that is never going to be used if only 32-bit software is going to be run (based on my experience with the old mode, I don’t know if it is still the case with the new one).
Another problem with my use case is that many winetricks calls take twice as long to run, sometimes with twice as much user interaction, because 64-bit builds of libraries are being installed despite having no use in that specific prefix.
In 32-bit-only Wine or in old WoW64, this bug is likely unfixable because, unlike Windows, Wine has to have both Windows libraries and Unix libraries in memory at the same time. New WoW64 elegantly solves the memory problem by using 64-bit Unix libraries and placing them above the 4 GiB mark. My guess is that a 32-bit-only Wine that uses 64-bit Unix libraries so as to not clutter the 32-bit address space is theoretically possible, but there is so little demand for it that it will never be a supported configuration. Your best option might be to switch to a copy-on-write filesystem like btrfs so that at least you aren't physically duplicating files between /usr/lib/wine and ~/.wine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.