Friday, May 19th 2023

First Test Build of Windows 2000 64-bit Rediscovered

A 64-bit Dec Alpha C compiler was found by Virtually Fun's neozeed earlier this year - the software archeologist has been searching for various test builds of Microsoft Windows NT, including an "AXP64/ALPHA64 port," deemed extra special due to it being the first 64-bit version of Windows 2000 Professional. The small discovery of this obscure compiler was celebrated, but its functionality is ultimately not all that useful - neozeed notes that the items have been sitting within 1999 vintage Windows Platform SDKs: "It turns out that the AXP64 compiler set has been hiding in plain sight for DECADES. I know that it's so unlikely that we'd ever see any public release of a 64-bit version of Windows for the Alpha, but oddly enough the compiler, headers and libraries are all there. YES. You can make full executes for AXP64/Alpha64. Of course with no OS, so it's not like you can run them."

He continues: "Sadly as of today, there is no way to test. There is one surviving machine with Windows 2003 AXP64, outlined in an article by Raymond Chen. It's a great read about how Alpha64 NT port came to be. The machine is still sitting in Microsoft Archives. Hopefully one day someone can dig it out." The story could have ended there, but a follow up post appeared on Virtually Fun earlier this week - courtesy of guest contributor Antoni Sawicki (aka tenox) who has also experimented with the cross-compiler. He provided a little bit more historical context before making an interesting announcement: "The Win64 project for AXP64 and IA64 was code named "Sundown." Sadly, 64-bit Alpha AXP Windows was never released outside of Redmond."
"This was released by Microsoft to allow developers test-compile their programs to see if they are "64-bit ready," ahead of 64-bit hardware being available. However, this was just a cross-compiler and there was no actual way of running any of the binaries. Until Itanium finally came out, after infamously long delays." He mentions that a "generous reader, who contacted neozeed after his previous post, shared a disk image… containing a 64-bit build of Windows 2000 for Alpha AXP! The reader got it from a lot of random hard disks - bought from an e-waste (seller), years ago, and completely forgot about it until they saw the blog post!" Tenox and neozeed managed to get the test build running on an old PWS500 system via very roundabout methods.

Tenox reveals a couple of limitations: "Unfortunately there are no identifying marks that would definitely prove that this is a 64-bit Alpha AXP build. The only way to tell is because there is no WOW, even for AXP32. You can't run any 32-bit Alpha binaries. It will only run executables produced with the ALPHA64 compiler. This also means in practice, there is no native compiler for this. You have to cross compile on 32-bit NT4 or 2KRC. However if you (are) going to build anything for AXP64 I can run and test it for you. For sake of search engines the build number is 2210, the full string 2210.main.000302-1934."

He invites folks to witness the evidence in person: "If you want to see this live in action. We (are) going to be exhibiting at VCF West 2023 in August alongside other NT RISC machines. Come and see us!"
Sources: Virtually Fun, Raymond Chen, The Register
Add your own comment

28 Comments on First Test Build of Windows 2000 64-bit Rediscovered

#1
Chaitanya
Didnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
Posted on Reply
#2
Chry
ChaitanyaDidnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
2000 was based on XP/98 while ME was a whole new thing.
2000 was okay after some updates.
Posted on Reply
#3
Jism
ChaitanyaDidnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
What?

W2000 was quite the stable OS in between 98 and XP out there.

Many people still used W2000 as it was robust and did'nt had the quircks both 98 or XP or even ME had.

Just not 64 bits...
Chry2000 was based on XP/98 while ME was a whole new thing.
2000 was okay after some updates.
It was based on Windows NT - not 98.
Posted on Reply
#4
natr0n
should make an image for safe keeping
Posted on Reply
#5
Sabishii Hito
ChaitanyaDidnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
Windows 2000 used the NT kernel and was a heck of a lot more stable than the consumer OSes until XP (which was also NT kernel).
Posted on Reply
#6
Solaris17
Super Dainty Moderator
ChaitanyaDidnt know Win 2000 got a 64bit treatment
It’s not 64 bit as we know it now, or knew it in windows xp.

this is before that, this is x64 itanium
Posted on Reply
#7
Jism
And Win XP was released with a 64 bits extension added to it as well. Biggest advantage is memory adressing. You could go beyond 4GB memory limit. And apps natively written in X64 where faster then X86.
Posted on Reply
#8
Solaris17
Super Dainty Moderator
JismAnd Win XP was released with a 64 bits extension added to it as well.
They aren’t the same windows xp and consumer OSs we came to know were/are x86-64 (EMT64/AMD64) these were a totally different instruction set. ia64 was not cross compatible and were pure 64bit only. “Windows XP 64bit” worked on itanium but was NOT THE SAME as “window xp pro x64” (x86-64). The only other OSs to support itanium were server OSs until itanium died in like the mid 2Ks. I think some Linux distros still support it designated by the “ia64” in the iso name but I think this is getting ripped out of the kernel now iirc.
Posted on Reply
#9
chrcoluk
ChaitanyaDidnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
Most stable Microsoft OS I have ever used, people often ran it as a server, it was that reliable.

I skipped ME and went straight to it from 98SE and was a clear upgrade in the experience.

Microsoft seemingly used it unofficially as a test bed for NT for consumers, as ME was pushed instead officially, but 2000 did come with consumer features such as DirectX.
Posted on Reply
#10
ExcuseMeWtf
JismAnd Win XP was released with a 64 bits extension added to it as well. Biggest advantage is memory adressing. You could go beyond 4GB memory limit. And apps natively written in X64 where faster then X86.
XP x64 was actually repackaged Server 2003 with Luna GUI and other XP bells and whistles.

I used it for a few years. Was a great system actually, though not everyone provided drivers for it. I didn't have that problem with my hw at the time.
Posted on Reply
#11
Fouquin
Solaris17this is before that, this is x64 itanium
DEC Alpha isn't Itanium, Alpha AXP and IA-64 are completely different ISAs. Itanium as a whole was supposed to supplant Alpha but Alpha came to market in 1992 and Itanium didn't launch until well after the Alpha team had been passed over to Compaq (PRIOR to Compaq merging with HP, so not connected to Itanium's development).
Chry2000 was based on XP/98 while ME was a whole new thing.
95/98/ME are all DOS based.
NT4, 2000, XP are NT based.

None of these were truly their own thing, and ME especially reuses a lot of 98SE's systems because other than a driver repository upgrade it's mostly just 98.
Posted on Reply
#12
Timbaloo
JismWhat?

W2000 was quite the stable OS in between 98 and XP out there.

Many people still used W2000 as it was robust and did'nt had the quircks both 98 or XP or even ME had.

Just not 64 bits...



It was based on Windows NT - not 98.
NT 4.0 SP6... Best Windows ever :love:
Posted on Reply
#13
Solaris17
Super Dainty Moderator
FouquinDEC Alpha isn't Itanium, Alpha AXP and IA-64 are completely different ISAs. Itanium as a whole was supposed to supplant Alpha but Alpha came to market in 1992 and Itanium didn't launch until well after the Alpha team had been passed over to Compaq (PRIOR to Compaq merging with HP, so not connected to Itanium's development).
I know that, I miss my Itanium server even though I got it well after consumer land had more powerful CPUs. I was under the impression Alpha was the grandad of Itanium?
Posted on Reply
#14
Fouquin
Solaris17I know that, I miss my Itanium server even though I got it well after consumer land had more powerful CPUs. I was under the impression Alpha was the grandad of Itanium?
Nope, Alpha was the primary competition that Itanium was trying to disrupt. A lot of people conflate the two because HP worked on Itanium with Intel, and HP merged with Compaq around the time Itanium finally became relevant (and Compaq had cancelled development of Alpha EV8 upon announcing their move to adopt Itanium) so the assumption is that Alpha was the predecessor to Itanium. They aren't even the same underlying architecture, with Alpha being pure RISC and Itanium being a heavily restructured VLIW (coined EPIC). The whole premise of Itanium was based on HP being afraid that RISC was a dead end architecture and they needed something more capable.

Development of Alpha and IA-64 run parallel (MIPS as well) but don't intersect. Alpha's end coincided with Itanium's beginning simply because Compaq was won over by Intel's marketing. That worked out great for them...
Posted on Reply
#15
TheinsanegamerN
Chry2000 was based on XP/98 while ME was a whole new thing.
2000 was okay after some updates.
You got that backwards.

ME was 98 third edition with a bunch of new hybrid 16/32 bit code that was an abomination to handle.

2000 was built on NT4
ChaitanyaDidnt know Win 2000 got a 64bit treatment, I remember it being quite unstable compared to Xp and 98SE(not as bad as ME though).
You got one hell of a memory there. XP at launch was an unstable mess compared to 2000, and 98se could never hold a touch to NT based operating systems.
Posted on Reply
#16
Solaris17
Super Dainty Moderator
FouquinA lot of people conflate the two because HP worked on Itanium with Intel, and HP merged with Compaq
Yes! This is what got me! Thanks for clearing that up!
Posted on Reply
#17
L'Eliminateur
FouquinNope, Alpha was the primary competition that Itanium was trying to disrupt. A lot of people conflate the two because HP worked on Itanium with Intel, and HP merged with Compaq around the time Itanium finally became relevant (and Compaq had cancelled development of Alpha EV8 upon announcing their move to adopt Itanium) so the assumption is that Alpha was the predecessor to Itanium. They aren't even the same underlying architecture, with Alpha being pure RISC and Itanium being a heavily restructured VLIW (coined EPIC). The whole premise of Itanium was based on HP being afraid that RISC was a dead end architecture and they needed something more capable.

Development of Alpha and IA-64 run parallel (MIPS as well) but don't intersect. Alpha's end coincided with Itanium's beginning simply because Compaq was won over by Intel's marketing. That worked out great for them...
don't remind me, fucking HP ruining Compaq when they bought them, and Compaq ruined DEC when they bought them.

They got won over by corrupt intel with their shit itanic, just imagine if alpha had not been cancelled how far could it have gotten..., maybe it would've died later with x86-64 came out, as honestly alpha had no chance to survive in the consumer space.
Maybe it would've worked now for the enterprise space or a niche for the HPC systems, now that compiling is easier across platforms
Posted on Reply
#18
R-T-B
Solaris17It’s not 64 bit as we know it now, or knew it in windows xp.

this is before that, this is x64 itanium
Isn't it not even Itanium, but DEC Alpha?

EDIT: missed some posts
Posted on Reply
#19
Logoffon
natr0nshould make an image for safe keeping
Work is being done for that, but will take quite a while as that build contains identifiable information (such as the name of an MS employee who owned that machine) and that needs to go before it can be uploaded.

In the meantime, have the binaries from that build: archive.org/details/splash_20230516
Posted on Reply
#20
ypsylon
Shame that W2000 never really got 64b support for the masses.

W2K IMHO best Windows OS ever released. No bloat, just rock solid OS.
Posted on Reply
#22
Dr. Dro
Are you positive we're not talking about an obscure Windows XP alpha build for the Alpha system here?

Build 2210 would place it in one of Whistler's early betas, wouldn't it? Whistler being the system which eventually released as Windows XP. At this stage none of the cosmetics had been added in, so it'd just look like and use Windows 2000 branding.

The finalized version of Windows 2000 is NT 5.0.2195, while Windows XP would achieve Gold status with build 5.1.2600.
Posted on Reply
#23
Ruru
S.T.A.R.S.
chrcolukMost stable Microsoft OS I have ever used, people often ran it as a server, it was that reliable.

I skipped ME and went straight to it from 98SE and was a clear upgrade in the experience.

Microsoft seemingly used it unofficially as a test bed for NT for consumers, as ME was pushed instead officially, but 2000 did come with consumer features such as DirectX.
Totally agree here. The only times 2000 crashed on me were either unstable overclocks or a crappy driver.
Posted on Reply
#24
neozeed
natr0nshould make an image for safe keeping
I had been asked to redact a lot of PE on the image, so Ive been working on that, and getting it to boot on another Alpha so I can check that I haven't broken anything.

Considering almost nobody can or will actually run it, I did make the binaries of the platform available.

Alpha64 : Free Download, Borrow, and Streaming : Internet Archive

It has no interesting midi/wav/bitmaps if anyone wonders, the logo is the same as the super early itanium versions with the spraypainted 64 over the 2000 logo.

SDL ported over, not so much outside of zip/unzip. It's very picky.

One interesting observation is that there is a WoW64 layer, but it's tied to the wx86 in house Microsoft x86 emulator! NTVDM from NT4 wont run, but Freecell from Win32s however DOES. The gui tools from SQL 4.21 will not run, but the SQL Server & CLI tools run fine.

Clearly they were far more interested in an i386 WoW64, than preserving an Alpha32 WoW. This also means it cannot run the compiler, requiring me to reboot, which takes ages.
Posted on Reply
#25
Dr. Dro
Welcome to TPU mate!

I was thinking, are there no DEC Alpha emulators available? QEMU doesn't seem to support it. If this really requires real hardware, then it's no wonder it's fallen into that much obscurity. :oops:
Posted on Reply
Add your own comment
Nov 21st, 2024 08:45 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts