Chain of Fools : Upgrading through every version of windows (HQ)

2.8M views · 15 years ago · demo · historical

Chain of Fools shows a Windows installation upgraded in place through successive versions, starting from Windows 1.0 and going up to Windows 7. Data and programs carry along the way, though the user's theme gets overwritten by defaults.

HN people hold it up as a sight to behold and as proof of Microsoft's backward compatibility, while also noting what each upgrade resets.

“I remember gaining quite an appreciation for all the work put in over time in Windows”

15 comments from Hacker News

s
@stesch2013 · in “Chain of Fools: Upgrading through every version of windows (up to Windows 7)”
Submitted the video to Hacker News.
RecommendsView on HN
s
@slmbrhrt2011 · in “Imagine if your house had Windows”
Reminds of a video I saw of a guy upgrading through every version of Windows. It's a sight to behold. ▶ this video
RecommendsView on HN
m
@machrider2011 · in “Chain of Fools: Upgrading through every major version of Windows”
Submitted the video to Hacker News.
RecommendsView on HN
M
@ModernMech2026 · in “Oldest GUI application that still runs on Windows 11”
Related: "Chain of Fools : Upgrading through every version of windows (HQ)" (2011), they upgrade Windows 1 through to Windows 7, and demonstrate Doom II and Monkey Island working still at the end. Would be interesting to extend it to Windows 11. ▶ this video
k
@kirb2021 · in “Please don’t theme our apps”
Adding onto your point, I’m reminded of the video “Chain of Fools”, where a machine is upgraded from Windows 1.0 all the way through to Windows 8. Once he reaches XP, the theme he configured back in one of the first Windows versions just disappears and gets overridden with XP’s defaults. Then it happens again and again for every version since then, despite the guy changing the theme back to his custom one before each upgrade. ▶ this video So the phenomenon really started with Microsoft themselves. Sure, the more muted dialog backgrounds and vibrant foreground elements introduced since XP look far better than the Win95-esque greys, but I’m sure people who created their own themes (probably due to disability like color blindness) like their colors better than Microsoft’s.
CitesView on HN
s
@stordoff2021 · in “Internet Explorer 11 (IE11) to be retired on June 15, 2022”
Windows 1 to Windows 7: ▶ this video (set colour schemes disappear at XP, but programs continue to work) Follow up - Windows 1 to Windows 10: link
l
@lmkg2018 · in “The weirdest bug I’ve found in a compiler: MSVC 2017”
The following is a video of someone installing Doom II on DOS, upgrading the operating system in-place 11 times, and running Doom on Windows 7 (around 24 years of upgrades). ▶ this video
b
@b4ux1t32017 · in “An Argument for Why Windows Will Go Open Source”
No, it really doesn't. Windows has had backwards compatibility as a huge priority for a long time, often to their detriment. You can literally update a machine from Windows 3.1 to windows 10, and programs written for Windows 3.1 will still work.[1] [1]: ▶ this video EDIT: TO be clear, this is a video of upgrading to Windows 7, and there is a direct upgrade path to 10 from 7. Also, as per another user's reply, this doesn't hold true for 64-bit. However, that doesn't change the fact that Wine doesn't and really can't run win32 better than win32 does.
CitesView on HN
r
@rogerbinns2015 · in “Intel blames $1B revenue hit on Windows XP's stubborn grip”
They neglected to mention just how hard it is to "upgrade" from XP. If you want to install Windows 7 or 8 then it will only do a clean install. You have to figure out all the apps you have installed, install media, receipts/keys/vendor site logins, do the "upgrade", and then play system administrator for a long time. Approximately no one has backups, so all that needs to be sorted out too, as well as doing a restoration. Then new UI has to be learned. Nothing is where it was. Various apps probably had to be upgraded too, and they'll have new UI to learn too. Then they have to figure out system administration - how do you do updates, make the funky printer work, deal with anti-virus. I didn't even mention figuring out that whole 32 versus 64 bits thing either. The time, effort and money involved, especially for small businesses/organisations and individuals is daunting, not to mention a distraction from what their actual business is. By far the easiest thing for them is to do nothing. Microsoft really screwed up by not making a good upgrade process. They know how to do it, and did it in the past. ▶ this video
CitesView on HN
c
@candl2013 · in “Ubuntu 13.10 (Saucy Salamander)”
Here's a video of a continuous upgrade from ms-dos through every windows version all up to windows 7 (a timespan of ~20 years) that proves it's possible. ▶ this video
R
@RKearney2013 · in “ReactOS: Rebuilding Microsoft Windows from the ground up, fully open-source”
I don't know about you, but I have much, much better luck running executables under Windows than say Linux or OS X. Microsoft puts a ton of work into keeping backwards compatibility. You can watch the YouTube Video[0] of someone upgrading through every Windows version (well, most?). OS X users have to figure out if they need that Intel or PPC binary, or maybe just the larger universal one and call it a day. Then there's not being able to run any of their older PPC-only apps once Apple removed Rosetta from OS X. [0] ▶ this video
CitesView on HN
a
@alexsb922013 · in “Building Photoshop 1.0”
> I often think about how incredibly inefficient modern software is given that we've had roughly the same level of productivity software ability (with varying levels of usability) for a few decades now. I distinctly remember my NT4 system of the late 90's, and how it was roughly as productive as my current machine, and I wonder just how much cruft is inside modern operating systems and applications. As a fellow young person (probably even younger than you), I remember watching this video ▶ this video two years ago when it came out and I remember gaining quite an appreciation for all the work put in over time in Windows and the complexity that it probably brings.
CitesView on HN