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

    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
  • 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
      492
    2. 2
      +Edouard
      224
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!