Slashdot Mirror
Windows XP-64 Delayed Into 2005
vincecate writes "Although
Windows XP on AMD64 was demoed at ComDex in 2002,
Microsoft is now
delaying the release till the first half of 2005.
Given Microsoft's history on this product, it could be
even more than a year before it is really released.
At least
one person at Intel says they did not ask Microsoft to delay
the release.
In any case, for the near future if you want to run a 64 bit operating
system you will either be using
one of the free Linux versions
or the
free download of Windows XP-64 beta.
Though Sun started well after Microsoft, they are
progressing well on their Solaris port to AMD64 and could well release earlier."
"In any case, for the near future if you want to run a 64 bit operating system you will either be using one of the free Linux versions"
There are supported linux versions available as well. I know Red Hat and SuSE have released versions supporting the amd64 and I think Mandrake does as well
Besides Linux and Windows, you can also use FreeBSD, for which amd64 is in tier 1 (full support), along with i386. Other BSDs of course support it :
NetBSD
OpenBSD
Not a full 64-bit OS, at least at the moment.
Mac OSX 10.3.4 does not run in 64-bit mode on my G5.
Uh, you are wrong. For the early XBox 2 dev kits, Microsoft has a version of the NT kernel running on a slightly modified G5 system. Not an x86 architecture there.
Hmm, why is this modded as Informative? Windows NT ran on MIPS (I've seen it running on modified SGI Indy boxes), PowerPC, Alpha and x86. The HAL makes it possible. Windows 2000 Beta was running on Alpha. What makes you think Windows is an x86-only product?
Mike Bouma
While you're right, Windows definitely was available for a variety of architectures, unfortunately there was a _serious_ shortage of software for Windows NT for PPC, MIPS and Alpha/AXP. A few Microsoft packages, like BackOffice, Visual C++, and a few other things, were available; most third-party software, however, was not ever built for anything but x86. The only reason the Alpha/AXP version had a longer lifetime, and apparently more software, was due to the FX!32 dynamic translation software that Digital developers created to run x86 binaries on Alpha. There was no real technical limitation to speak of, just momentum of Windows on x86.
Sam: "That was needlessly cryptic."
Max: "I'd be peeing my pants if I wore any!"
Yes, as soon as Tiger is released, you'll be correct. The current OS X release, however, is not 64-bit native.
Sam: "That was needlessly cryptic."
Max: "I'd be peeing my pants if I wore any!"
Windows NT wasn't originally designed for x86. Hell, initially it was developed for a CPU that didn't even exist - when it was first being developed, it was targeted at Intel's i960 RISC architecture. However, because the i960 RISC chip was plagued with delays, it was ported to another architecture (I believe the first one was MIPS32). Dave Cutler's clean OS design (one of the major designers of DEC's VMS operating system, hired away by Microsoft) made this possible relatively quickly.
And by the way, the original NT moniker was actually a reference to the CPU simulator - named N-Ten - that the first i960-native builds of what became Windows NT ran on.
Sam: "That was needlessly cryptic."
Max: "I'd be peeing my pants if I wore any!"
WOW64, if you're not familiar with the acronym, means windows on windows 64. It's basically their "emulator" (it's more of an interpreter) to run code not compiled for 64 bit. Instead of going the FreeBSD route and allowing for both 32 and 64 bit programs to run at the same time (props for freebsd), Microsoft decided to go with an emulator - which happens to suck horribly, and freeze alot.
Lies.
Windows and FreeBSD both do exactly the same thing, which is to let 32-bit programs run at full-speed, natively, on the cpu. Practically the whole point of AMD64 architecture is backwards compatibility. The world didn't need another Itanium.
WOW64 Implementation Details