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

    • illegally? Proof of that? Seems you are posting misinformation or well a pure straight up lie cause there is zero proof of such a thing. But I get it...
    • KillerPDF 1.6.0 by Razvan Serea KillerPDF is a lightweight, portable PDF editor for Windows built for users who want full control without subscriptions, installers, or telemetry. It runs as a single executable, making it ideal for USB use and field work. You can view PDFs with smooth PDFium rendering, navigate quickly with thumbnails, zoom, and shortcuts, and reorganize pages using drag-and-drop. It supports merging multiple PDFs, splitting documents, and extracting selected pages. KillerPDF also allows inline text editing with font matching to preserve the original layout, plus annotations like text boxes, freehand drawing, highlights, and reusable signatures. You can search full text, copy content easily, and print documents with flattened annotations. Designed as a free and open alternative to bloated PDF tools, it works fully offline on Windows 10/11 x64. No runtimes install. Everything needed is inside the EXE (targets .NET Framework 4.8, which ships with every supported Windows release). KillerPDF key features: High-quality PDF rendering via PDFium Edit PDF text inline (double-click to modify text) Page thumbnails and fast navigation with zoom and shortcuts Merge multiple PDFs into one Split PDFs and extract selected pages Drag-and-drop page reordering Font matching to preserve original document appearance Text boxes for notes Freehand drawing tools Highlight overlays with adjustable color, size, opacity Undo actions and clear per-page annotations Create, draw, and save reusable signatures Click-to-place signatures anywhere Full-text search with highlighted results Drag-select or Ctrl+A to copy text Print with annotations flattened Portable single-file app (~15 MB) No installer, no admin rights required No account, no telemetry KillerPDF 1.6.0 changelog: A big release: major new features, a full visual refresh, and an internal rewrite. New Tabbed documents - open several PDFs at once, each restoring its page, zoom, and view OCR built into the exe (Tesseract) - OCR a page or dragged region to the clipboard, make a scan searchable, or extract all text; extra languages download on demand Digital signatures with a cloud certificate (Certum SimplySign), reusable signatures, and click-to-sign form fields Transform tool - rotate, scale, flip, and straighten a crooked scan, with live preview Edit existing text by double-clicking a line (the original is cleanly covered) Line tool, refreshed draw/highlight bars, resizable word-wrapping text boxes, and a full RGB color picker with eyedropper Print options (scale, position, margins, two-sided), page-number stamping, folder/.zip import, Document Info (F12), and recent files with file-type icons Translations: Bengali, Turkish, Simplified Chinese, German, French. Changed New logo, icons, fonts, and colors throughout Six themes with per-theme accent colors; sidebar docks left or right; toolbar style picker Internal rewrite: the ~15,000-line main window split into ~40 focused files (no behavior change) Fixed True 300 DPI printing, encrypted/damaged PDFs open on a background thread with a repair fallback, form fields render in every view mode, and undo is one item per press Download: KillerPDF 1.6.0 | 14.6 MB (Open Source) Link: KillerPDF Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • They'll get cheaper RAM but they won't drop the prices.
    • Did you go into settings > engines and switch some more stuff on. The more you enable the slower it will get but the better the results will be
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      500
    2. 2
      +Edouard
      221
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      69
  • Tell a friend

    Love Neowin? Tell a friend!