Amazing 1993 Video of Windows NT 3.1


Recommended Posts



Alot of the features in the first Windows NT 3.1 are still in the Windows we use today, it is really amazing. Windows NT was ahead of its of time back then and so much that many computers could not run it (like Vista)!
Link to comment
https://www.neowin.net/forum/topic/1148884-amazing-1993-video-of-windows-nt-31/
Share on other sites

Only thing that bothered me about Computer Chronicles was how fast the subject changed. Five minutes of Windows NT, segue to a short bit on Mac OS and OS/2, go back to NT applications, etc. The better episodes where the ones that only focused on a single OS or product.

Cool video, though. Seen it before but it's a nice trip down memory lane.

I had no idea that NTFS was so old.

Might even be older than 1993. OS/2 was originally designed to be the powerful, multi-tasking OS that NT would eventually become. It wasn't until the success of Windows 3 in 1990 that Microsoft decided to cease OS/2 development, at which point IBM took over it solely.

Might even be older than 1993. OS/2 was originally designed to be the powerful, multi-tasking OS that NT would eventually become. It wasn't until the success of Windows 3 in 1990 that Microsoft decided to cease OS/2 development, at which point IBM took over it solely.

Amusingly, IBM back then was considered a slow, lumbering, committee-driven conglomerate of suits, yet there's no escaping people who deluded themselves into thinking we would've been better off with OS/2 than Windows.

Amusingly, IBM back then was considered a slow, lumbering, committee-driven conglomerate of suits, yet there's no escaping people who deluded themselves into thinking we would've been better off with OS/2 than Windows.

From what I've read, IBM and Microsoft were opposites, especially in code design. IBM wrote long, bloated code and paid by lines of code. Microsoft went for small, faster code. The documentary "Triumph of the Nerds" had an interview with Steve Ballmer about how IBM didn't seem to follow the mentality of paying a developer more if they were able to write a program in fewer lines, making it smaller and faster.

That, among other technical differences, was a big reason why OS/2 eventually become IBM only. I've never actually played with the Warp releases, but they sure look interesting, from what I've seen demoed.

Windows NT could run OS/2 1.0 applications all the way up to NT 4.0 I believe, as well as supporting the OS/2 HPFS file system.

The OS/2 1.x sub-system was part of NT until version 5.0, better known as Windows 2000. Additionally there was an add-on for NT up to 4.0 IIRC which allowed you to use OS/2 1.x Presentation Manager applications, as shown below.

1265456138.or.105738.PNG

Amusingly, IBM back then was considered a slow, lumbering, committee-driven conglomerate of suits, yet there's no escaping people who deluded themselves into thinking we would've been better off with OS/2 than Windows.

IBM's problem wasn't OS/2, but letting OS/2 flounder while Windows 95 was in development (after the OS/2-NT split).

OS/2 in general, and OS/2 2.x in particular, had an opportunity, even after Microsoft started replacing Windows 3.1 with Windows for Workgroups in shipments to OEMs (starting with Gateway, then followed quickly by Dell and HP) - IBM's OS/2 business had even admitted as such, and released OS/2 for Windows, which let customers add an existing Windows 3.x - even Windows for Workgroups - to OS/2. However, IBM's Systems Group - primarily their mainframe and nascent services business - wanted no part of ordinary consumers, or even SMBs, and starved the OS/2 unit of marketing funds. OS/2 required no more, in terms of hardware than Windows 95 - which itself required little more than Windows for Workgroups. (I would know - I dual-booted the two while Windows 95 was in beta.) True - Windows 95 had an ace in the hole that would not become evident until after it launched; it could run not merely Win32s applications, but even full-fledged Win32 (as in normally targeting NT) applications. That was something OS/2 could NOT counter without hefty royalty payments to Microsoft - and heaping helpings of crow. IBM under Trammel, and then Gerstner, was very prideful - could you see them going back to Microsoft, hat in hand and with a fat royalty check?

From what I've read, IBM and Microsoft were opposites, especially in code design. IBM wrote long, bloated code and paid by lines of code. Microsoft went for small, faster code. The documentary "Triumph of the Nerds" had an interview with Steve Ballmer about how IBM didn't seem to follow the mentality of paying a developer more if they were able to write a program in fewer lines, making it smaller and faster.

That, among other technical differences, was a big reason why OS/2 eventually become IBM only. I've never actually played with the Warp releases, but they sure look interesting, from what I've seen demoed.

IBM was (and still is) heavily enterprise-oriented - a legacy of their mainframe business. They didn't even market LAN Server (the server side of OS/2) very hard. Ordinary consumers and SMBs? They willingly - practically gleefully - steered those to Microsoft and LAN Manager (and eventually NT) before, during, and after the split - they wanted no part of such a plebian customer base. (I had, in fact, personally told IBM Mid-Atlantic's marketing mavens that if they didn't get their act together, Microsoft and Windows 95 would eat their lunch - in June of 1995.) OS/2 - as far back as 2.1 - was a squandered opportunity; OS/2 3.x - and even Warp (OS/2 4.x) were simply more obvious. (Look at eComStation - it is, in fact, OS/2 4.52 at the core. It's as least as viable as any Linux distribution, and supports more hardware than quite a few of them. However, even Ubuntu has a bigger word-of-mouth push then eCS does.)

IBM's problem wasn't OS/2, but letting OS/2 flounder while Windows 95 was in development (after the OS/2-NT split).

OS/2 in general, and OS/2 2.x in particular, had an opportunity, even after Microsoft started replacing Windows 3.1 with Windows for Workgroups in shipments to OEMs (starting with Gateway, then followed quickly by Dell and HP) - IBM's OS/2 business had even admitted as such, and released OS/2 for Windows, which let customers add an existing Windows 3.x - even Windows for Workgroups - to OS/2. However, IBM's Systems Group - primarily their mainframe and nascent services business - wanted no part of ordinary consumers, or even SMBs, and starved the OS/2 unit of marketing funds. OS/2 required no more, in terms of hardware than Windows 95 - which itself required little more than Windows for Workgroups. (I would know - I dual-booted the two while Windows 95 was in beta.) True - Windows 95 had an ace in the hole that would not become evident until after it launched; it could run not merely Win32s applications, but even full-fledged Win32 (as in normally targeting NT) applications. That was something OS/2 could NOT counter without hefty royalty payments to Microsoft - and heaping helpings of crow. IBM under Trammel, and then Gerstner, was very prideful - could you see them going back to Microsoft, hat in hand and with a fat royalty check?

IBM did try to market OS/2 to consumers. The older ones of us will remember the Warp 3-era commercials. Here in .de two of the biggest OEMs at the time - Vobis and Escom - even pre-installed OS/2 Warp 3 instead of DOS/Windows for a while in 1994/early 1995.

One reason which killed OS/2 was the lack of good native applications for it. Ironically you could say Win-OS2 (the Windows 3.x sub-system built in to OS/2 from version 2.0 on) was one cause for this - why would 3rd party developers port applications to OS/2 when you can simply run the Windows version on it?

IBM did try to market OS/2 to consumers. The older ones of us will remember the Warp 3-era commercials. Here in .de two of the biggest OEMs at the time - Vobis and Escom - even pre-installed OS/2 Warp 3 instead of DOS/Windows for a while in 1994/early 1995.

One reason which killed OS/2 was the lack of good native applications for it. Ironically you could say Win-OS2 (the Windows 3.x sub-system built in to OS/2 from version 2.0 on) was one cause for this - why would 3rd party developers port applications to OS/2 when you can simply run the Windows version on it?

Europe in general, and Germany/the Low Countries in particular, were the exceptions that, unfortunately, proved the rule. IBM didn't have a big Systems Group business in Europe - however, they DID have a solid relationship with NIXDORF (a major wheel in the PC business in Europe) which was responsible for a major part of the German OS/2 push.

There was no mirror to NIXDORF in North America, however.

This topic is now closed to further replies.
  • Posts

    • The only reason I want to know where you from is because if you are not from the U.K, then why should you care what we in the U.K do or don't do? Racist I am not, I am fed up with the amount coming over here and feel they can come over here and think we need to support them. Do you know how much it costs this country to support these people coming over here? Even when we give them a place to live it is not good enough. We had a barge that was being used to house immigrants, oh but that was not good enough. A mate said to me at the time, when he was homeless, he would have been happy to live on the barge, instead of ending up sleeping on a bench on the beach. I am not scared to say what my family heritage is, unlike you who is scared to say where they are from or where they live. Father side U.S, mother side Wales, still have family living in the U.S. A mate who sadly died a few years ago, had a load of people from different races recording in his studio, I got on with all of them. Skin colour don't bother me, where they are from don't bother me. Religion don't bother me as long as they don't push it onto me and it is not crazy stuff. I am not religious. But if you are not living in the U.K, then why should you care if we are in the E.U or not? This the problem, too many people poking their noses into where it don't belong. But you believe what you believe, if you think I am racist, then be it, I really do not care. Just grow a pair
    • If he hasn't been able to figure that out, then why is he obsessed with tariffs? Because that's one of the most prominent tools to level the playing field when you have high cost of labor.
    • Microsoft released Windows 11 KB5102558, KB5095615 Setup and Recovery updates by Sayan Sen This past week Microsoft released the newest preview update (C-release) under KB5095093. Alongside those, Microsoft also released new dynamic updates. For those who may not know, dynamic updates bring improvements to the Windows Recovery process in the form of Windows Recovery Environment (WinRE) updates, which are also called Safe OS updates. The dynamic updates also affect the Setup file binaries in the form of Setup updates. These Dynamic Update packages are meant to be applied to existing Windows images prior to their deployment. Dynamic Updates also help preserve Language Pack (LP) and Features on Demand (FODs) content during the upgrade process. VBScript, for example, is currently an FOD on Windows 11 24H2. This time both recovery and setup updates were released for Windows 11. The company writes: "KB5095186: Safe OS Dynamic Update for Windows 11, version 26H1: June 23, 2026 This update makes improvements to the Windows recovery environment (WinRE). After installing this update, the WinRE version installed on the device should be 10.0.28000.2335. KB5102558: Setup Dynamic Update for Windows 11, versions 24H2 and 25H2: June 23, 2026 This update makes improvements to Windows setup binaries or any files that setup uses for feature updates in Windows 11, version 24H2 and Windows 11, version 25H2. KB5095615: Safe OS Dynamic Update for Windows 11, versions 24H2 and 25H2: June 23, 2026 This update makes improvements to the Windows recovery environment (WinRE). After installing this update, the WinRE version installed on the device should be 10.0.26100.8737." Microsoft notes that both the Recovery and Setup updates will be downloaded and installed automatically via the Windows Update channel.
    • The high cost of labor and operating within the US. Donald hasn't been able to figure that out--pathetic.
  • Recent Achievements

    • Conversation Starter
      jessse3334 earned a badge
      Conversation Starter
    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      200
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      62
  • Tell a friend

    Love Neowin? Tell a friend!