On 07/18/10 01:26, Ranguvar wrote:
On Sat, Jul 17, 2010 at 20:49, Isaac Dupree
<[email protected]> wrote:
On 07/17/10 18:54, Sven-Hendrik Haase wrote:
Why is it called "wow64"? Why not something descriptive like
"wine-32-and-64"
or
"wine"
?
In particular does it have anything fundamentally to do with "wow" (I guess
that's "world of warcraft"?)
-Isaac
http://en.wikipedia.org/wiki/WoW64
:)
...wow. (a bad pun to express how I feel about that naming. But:)
Thanks for that link, it actually explains what wine-wow64 is doing a
bit better than I was able to make sense of from the original message...
this wine-wow64 is copying some particular oddity of Windows 64! (I
wonder, Maybe it could still be called just "wine" though..I haven't
been tracking upstream Wine closely enough to see what their thoughts on
64-bit have been recently. But, not if "wine" refers to a wholly
different package in Arch Linux (i686 only - which I can't find out much
about because I've never had an i686 Arch system but I thought something
fishy was going on - normally packages are equally available on all two
arches))
oh, so more info at http://wiki.winehq.org/Wine64 , it says 64bits
version "is not yet fully functional", and for 32bit part of WoW64 "The
32-bit side of such a Wow64 build is in theory supposed to work
identically to a stand-alone 32-bit build. Currently this is not quite
the case, any help is welcome." so... it may not be ready to replace
bin32-wine if the upstream wiki-page is up-to-date (last edit this
April..so maybe it is)
