Am 05.12.2011 20:18, schrieb Joe:
On 12/5/2011 1:59 PM, Alan Adams wrote:
In message<4edd1224.3060...@freakyacres.com>
Joe<j...@freakyacres.com> wrote:
On 12/5/2011 1:03 PM, bugzilla-dae...@bugzilla.wpkg.org wrote:
http://bugzilla.wpkg.org/show_bug.cgi?id=258
Rainer Meier<r.me...@wpkg.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #3 from Rainer Meier<r.me...@wpkg.org> ---
Oh, I did not even think about this. But sure this is a good
explanation too :)
Closing this issue.
Is that the proper behavior? Should a 64bit machine be detected as 32bit
because of the client software?
I imagine it is. I would not expect to be able to run a 64-bit
application on a 32-bit OS, which is what would happen if the hardware
determined the architecture type.
Alan
So a 32 bit client running under windows 64 bit on 64 bit hardware
detects as 32 bit?
A 32-bit application always thinks the operating system is 32-bit too,
since it wouldn't work, if this wouldn't be the case.
This is what WOW stands for.
If you like to have full access to an operating system, you need to
install native applications, which match the processor architecture.
You can still install a 32-bit O/S on 64-bit H/W, but all you will get
is 32-bit.
--
Stefan P.
Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
