A multiboot computer on every desktop! It's my vision!

The expanded directories of driver packages are getting comical. 95,98,ME,NT,2000,XP.

Let's see if we can list them in order:

1) Windows 1.0 - the only usable program was "Clock".

2) Windows 2.0 - the only usable program was "Clock", but you could have a game of "Reversi" partially obscure the clock.

3) Windows 3.0 - sorry 3.1 - this is a famous Microsoft trick - they sell people broken stuff and then fix it almost immediately, a tactic that occurs over and over again.

"Clock" is better than ever - big grey letters for testing that new video driver acceleration and graphi- oh oh, the clock stopped.

4) Windows 4.0 - 95 - oops! It's broken, sorry! We made 95b just for you! See how reponsive tech support is?

For some strange reason, Microsoft decides to cede the "Clock" market to OS/2, reducing the app to a small afterthought in the bottom corner. For an extra fee, you can purchase the "Clock Migration Resource Kit" which transfers the license, code, and runtime libraries for the 3.1 "Clock" to your new installation. There is a special 16bit mode specifically made for backward "Clock" compatibility.

5) Meantime, in the colonies, we have...

Windows NT 1.0 - er - 3.1. Oops, darn it all! It's broken! Here's 3.51! See how responsive we are?

The main advantage of Windows NT 3.51 is that is can run a shitload of "Clocks", each in its own Windows 3.1 emulation mode - oh no, the clocks are all slowing down...hmmm.

Etc. etc.

Is two per desktop enough?

5) Windows