32-bit vs 64-bit
- From: "Allan" <allanwkf@xxxxxxxxx>
- To: <"Undisclosed-Recipient:;"@freelists.org>
- Date: Sat, 21 Apr 2007 02:15:48 +0800
dear all, since there still someone can't make a correct decision whether to
get a 64-bit system or just a 32-bit system, here i
have a short note that might help you. i'm apologies if you receive this
posting multiple copy because i'm sending this to a few
lists, sorry for the inconvenience. to the moderators, please allow this post
send to the list, because this may help some of us
fellow members.
-------------------------------
One of the more common questions I hear about Vista is which bit version of
Windows Vista should one get. Do we go with x86 32 bit
edition or x64 64 bit edition? I'm going to try to clear that question up as
best as I can and explain the pros and cons of each
choice.
First we must understand a little background on what x64 is. X64 is the 64
bit extension technology that AMD invented (AMD64) to
seamlessly migrate the 32 bit x86 (as in 286, 386, 486 compatible
microprocessors) world into a 64 bit era. Intel in partnership
with HP had refused to extend the ancient x86 platform and had already
committed to its all new pure 64 bit IA-64 Itanium
architecture. While Itanium was fundamentally superior, its x86 emulation
provided inferior performance for existing applications
and the adoption rate was very slow. Intel had hoped that the market would
leap to the new platform but there was no seamless way
of making that migration, and Itanium failed to gain widespread adoption. AMD
took the opportunity to extend the existing x86
architecture with 64 bit capability by handling 64 bit CPU registers and adding
a lot more registers, and it was immediately greeted
warmly by the market. In a reversal of roles, Intel found itself copying AMD64
(permitted by an AMD-Intel cross-licensing
agreement) and calling it EM64T. The two x64 technologies are essentially
identical except for a few minor differences in the
implementation.
Microsoft initially created a version of Windows XP called XP 64 bit Edition, a
pure 64 bit operating system that ran on IA-64
Itanium and only supported x86 applications through emulation. There was even
a Windows 2000 Server version for IA-64 as well. The
problem was that the adoption rate of IA-64 was very slow, and when AMD created
AMD64-with Intel having no choice but to
follow-Microsoft created the x64 edition of Windows XP as well as Windows
Server 2003. The x64 editions were hybrid 32/64 bit
operating systems that could natively run 32 or 64 bit code at full speeds
without software emulation, whereas the 64 bit edition of
Windows XP relied on software emulation to run existing x86 32 bit code. With
the release of Vista, Microsoft simultaneously
launched the 32 bit x86 and the 64 bit x64 editions. The retail editions
contain both the x86 and x64 editions, while the OEM
versions contain one or the other and you have to decide before you order. Now
one of the most common questions people ask is
whether to run 32 or 64 bit Vista. The first thing you must do is to make sure
your particular CPU supports x64.
list of 11 items
* Almost all new servers sold within the last two years from AMD or Intel will
have x64 capability.
* Most mid- to high-end desktop processors from AMD or Intel within the last
year have x64 capability.
* Some higher-end Semprons have x64; lower-end Semprons do not.
* No AMD Durons have x64.
* All AMD Opteron processors have x64.
* All AMD X2, FX, and Athlon64 chips have x64.
* All Intel Pentium D and Celeron D chips have x64.
* All AMD Turion notebook processors have x64.
* All Intel Core 2 processors (mobile, desktop, and server) have x64.
* No Intel Core Duo notebook processors have x64.
* No Intel Pentium M notebook processors have x64.
list end
Drivers are the death of x64.
The second thing you must check is to see if all your hardware has x64 Vista
driver support, either included in the OS or
downloadable from the hardware vendor. At this point, many motherboard makers
have failed to include the latest 5.1 sound and
network drivers, and you might have to look to the chipset maker for drivers.
For example, you can find for Gigabit LAN and 5.1
audio support.
NVIDIA has
ATI (AMD) has
Creative has
but its x64 support is sorely lacking, and it's either missing or in beta.
While these are the fundamental hardware drivers you'll
need, the killer for Vista x64 edition is finding drivers for obscure hardware
like cameras, printers, scanners, and other
accessories. You don't have to worry about 32 bit software compatibility in
Windows Vista or XP x64, since they run natively and
seamlessly, but drivers are an absolute killer. If you happen to find 32 bit
drivers for your device but no 64 bit drivers, you're
out of luck if you're running x64 Windows XP or Vista. For this reason, x64
edition for a typical consumer is usually not very
practical because there are simply too many hardware peripherals you won't be
able to use. Getting the computer itself to work is
relatively easy; it's the one or two obscure devices that stops you dead in
your tracks if you must have that device working. For
this reason, no PC maker (that I'm aware of) will pre-load x64 edition of
Windows on its PC because it will be a support nightmare.
The bottom line is that you have to look at your own hardware limitations
before you can make any kind of a transition. If all the
hardware you want to use will work on Vista x64, it's well worth the transition.
Warmest Regards,
Allan Wong
3M Technology
--
JFW related links:
JFW homepage: http://www.freedomscientific.com/
Scripting mailing list:
http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
JFW List instructions:
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
