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

    • Go for a Echo Dot or Pop instead. These Echo shows just advertise to you.
    • NetSpeedTray 1.3.3 by Razvan Serea NetSpeedTray is a lightweight, open-source Windows network monitor that shows live upload and download speeds directly on the Taskbar. Designed for efficiency, it quietly sits in the system tray, conserving CPU and battery with dynamic updates. It blends seamlessly with Windows 10/11, adapts to light/dark themes, and auto-positions to avoid overlaps. Features include accurate interface detection, customizable display, optional mini-graph, color coding, granular font and unit control, detailed per-interface history graphs, safe data management, and easy CSV export—bringing the network monitoring Windows forgot. NetSpeedTray key features: Lightweight & Efficient Runs quietly in your system tray without consuming resources. Features a "Dynamic Update Rate" that lowers refresh frequency when the network is idle to save CPU and battery life. Native Look & Feel Blends seamlessly with Windows 10/11 UI. Smart detection for light and dark taskbar themes ensures text is always visible. Intelligent & Adaptive Positioning Automatically finds empty space next to your system tray and shifts to make room for new icons, preventing overlaps. Seamless OS Integration Behaves like a native Windows component. Hides instantly with auto-hiding taskbar Hides when a fullscreen app is active Smart Network Monitoring Accurate by Default: Auto mode identifies your main internet connection and ignores noise from VPNs or virtual adapters. Easy Interface Selection: Switch effortlessly between Auto, All, or Selected network interfaces via intuitive radio buttons. Total Visual Customization Free Move Mode: Unlock and place the widget anywhere on your screen. Optional Mini-Graph: Real-time graph of recent network activity with adjustable opacity. Color Coding: Customize colors and speed thresholds to quickly see network status. Granular Display Control Text & Font: Adjust font family, size, weight, and alignment. Units: Automatic (B/s, KB/s, MB/s) or fixed Mbps display. Precision: Set decimal places and always show them for uniform appearance. Detailed & Intelligent History Graph Smart Scale: Logarithmic scale shows low-level traffic and large spikes clearly. Per-Interface Filtering: View speed history for specific adapters (Wi-Fi, Ethernet, VPN). Safe & Efficient Data Management: Adjustable retention, automatic cleanup, optimized database. Easy Data Export: Export raw data to .csv or save high-quality graphs for reports. NetSpeedTray v1.3.3: The Updater Fix A stabilization release that repairs a critical regression in v1.3.2: the app shipped without OpenSSL, which silently broke every HTTPS request — including the built-in update checker (the "Could not check for updates" error many of you hit). This release restores it, hardens the build so it can't happen again, and fixes a startup crash plus four other reported bugs. Changes: Fixed update checking — Resolved a critical issue that prevented the app from checking for updates ("Could not check for updates"). Fixed startup crash with Auto-Cycling — The app no longer crashes on launch after enabling Cycle display mode. Fixed incorrect network speeds on 10GbE adapters — Multi-gigabit network cards now display speeds correctly instead of being stuck at 0. Improved color coding — Default color is shown when idle, and color/threshold changes now apply immediately without restarting. Fullscreen visibility fix — The widget now correctly stays visible over fullscreen apps when Keep Visible is enabled. Improved AMD Ryzen temperature detection — More reliable CPU temperature monitoring for Ryzen processors. Cleaner upgrades — Installer now removes outdated application files during upgrades, preventing DLL/version conflicts while preserving user settings. Improved stability — Fixed potential DLL loading issues by excluding critical OpenSSL and NumPy components from UPX compression. Better settings window — Scrollbars removed and layout improved for a cleaner experience. Localization improvements — Updated translations and completed missing UI text across all supported languages. More reliable releases — Added regression tests covering recent critical fixes, bringing the test suite to 196 passing tests. [full release notes] Download: NetSpeedTray 1.3.3 | 87.9 MB (Open Source) Download: NetSpeedTray Portable | 101.0 MB View: NetSpeedTray Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Why Delta Chat is the best decentralized messenger you have probably never tried by Paul Hill There is no shortage of messaging apps out there; we have WhatsApp, Messenger, and Telegram, just to name a few. While Meta has taken steps to incorporate encryption into Messenger and WhatsApp, they still leave a lot to be desired. If you are in the market for a messaging app that promotes security, privacy, and optional anonymity, you'll want to read what I have to say about Delta Chat. For those not familiar with Delta Chat, rather than relying on centralized servers as you do with Facebook Messenger, it relies on email. Essentially, it is a chat interface that feels like a messaging app, but secretly in the background, it is firing off emails. In the past, you used to have to sign in with your email account. When you sent messages to people, it would just be sending encrypted messages to their inbox, which their Delta Chat client would decrypt. When I first learned about Delta Chat, it required users to sign in with an email account, but I was pleasantly surprised upon trying it in 2026 that this is no longer a requirement, or the preferred method was to use the app. Recently, I’ve tried UAD-ng on my old Nokia 3.4 to disable most of the Google apps because the bootloader is locked, and this is the next best option. While finding replacement apps in F-Droid, I came across Delta Chat again, and it has undergone quite a big change since I last used it, with its new chatmail relays, which no longer require you to sign in to your own email account, providing anonymity, and they offer greater security. Android and Desktop Delta Chat apps. Not only does it run on my de-googled phone, but it also works on desktop computers and iOS, making it truly ubiquitous. For me, Delta Chat is a wonderful alternative messenger because it gives you more control. It supports switching between different profiles, which you can set up super quickly; you don’t register a username, you don’t register a password. The only thing you do have is a random string email address on a chatmail relay (which you don’t have to memorize). To maintain access to your profile, you just need to add a second device to your account via QR code or make a backup of your account, which you can restore later. Fail to do these, your account is gone - as it should be if you don’t want to leave accounts that could get hacked later on. My decision to block Google stuff on my Nokia was done for practical reasons; the device sucked when it launched, and it sucks even more now. The nice thing about F-Droid and the apps within is that they’re usually lightweight, free of bloat, and work well on that device. What was inconvenient for me was that it was hard to send messages from that device, say if I wanted to copy a code over to my main phone or send family members a link from that device. That’s when I decided to look at the available chat apps and saw Delta Chat. Another nice thing about Delta Chat is its notifications. Some messaging apps rely on Google’s ecosystem for notification transport on Android; however, with Delta Chat, it can use Google’s solutions if you have Play Services or MicroG installed. Otherwise, it is able to keep a background connection to the chatmail relay server so that you can get notified when you receive a message. As free software, the code of Delta Chat is open for all who want to take it and build upon it. In the future, if the developers of Delta Chat make a catastrophically bad decision and take the app in an undesirable direction, users can take the code and fork the project. This contrasts with closed-source apps from corporations that can take their products in any direction they like. By relying on free software instead of closed-source programs, you actually control your computing. I’ve spoken at length about how running this type of software is like owning your own home rather than renting it. The same applies here; if you use Delta Chat, you don’t need to worry about it going away in the future. Whether it is Telegram, WhatsApp, or Messenger, you are required to register a username and password to use these services. A major flaw in this design is that anyone can try various passwords and potentially break into your account with your complete chat history intact. Sure, there is encryption in Messenger, where you need a second PIN and two-factor authentication in Telegram, but breaches happen all the time. Unlike before, when you used to sign in to your email account to send and receive messages, the primary way to do it now is to create an account on a chatmail relay. The resulting email address is a random string followed by the name of the relay you pick. This means you can start and begin adding contacts Without a username and password, you either need to ensure you have a backup or at least one device running your Delta Chat profile. The primary way to log in on another device is to go to the settings and add a second device. Then, you’ll just scan a QR code with your new device, and it’ll log in to your account and sync all your chat history and contacts. To end users, Delta Chat just looks like any instant messenger; however, it is really sending your messages as encrypted emails to your contact. This is pretty cool from a censorship perspective, as it makes the service more difficult to block. Previously, the main way to use the app was by logging in with email, but nowadays, it’s recommended that you use chatmail relays. Chatmail relays temporarily hold messages in case your device is offline. They are cheap, simple servers that don’t store data as group states. Other information, like your name and avatar, only exists on your device and the devices of those you share your contact information with. The relays are also decentralized and operated by various groups and individuals. It is even possible to set up your own chatmail relay, but most people will want to use one hosted elsewhere. To keep your messages secure, Delta Chat uses a secure subset of the OpenPGP standard that gives you automatic end-to-end encryption. It also uses Secure-Join to exchange encryption setup information through QR-code scanning or invite links. Autocrypt is also used to automatically establish end-to-end encryption between contacts and all members of group chat, but sometime this year Autocrypt v2 will be rolled out, bringing post-quantum resistant encryption and forward secrecy. The Delta Chat FAQ is an interesting read that explains many more details about the app. Credit: Pexels Delta Chat is unique among messaging apps because it is built on email, a technology that’s decades old and isn’t going anywhere soon. What’s more is that email is not centralized either, so it’s far more difficult for any authoritarian regime to disrupt the Delta Chat app. I haven’t spoken too much about features yet, so I will do that now. Delta Chat allows you to do one-on-one chats, group chats, and create channels. It also supports file sharing and making audio and video calls when chatting one-to-one, but it’s not available for group chats right now. At the time of writing, the calling functionality is disabled and can be enabled in Settings > Advanced > Debug Calls. I have used the video calling feature, and the quality is excellent. It works over WebRTC, another open standard. The app also lets you send voice notes, enables disappearing messages, and has its own app ecosystem. I did try playing chess one time there, but it was a bit spotty; though, we did manage to complete the game with a victory for me. To add people to Delta Chat, you can either give them your Delta Chat link or your QR code to scan. These are the only ways to add users, so you won't have any spam bots bothering you. If the people you want to chat with don't have the app yet, just send them your link, and it will take them to a webpage where they can install the app and then add you. It's really quick for them to install it and get started, which is nice. Credit: Microsoft. The Majorana 2 quantum chip unveiled in 2026. I do not think quantum computers are too far out now, and I do hope that Delta Chat is able to push out Autocrypt v2 sooner, rather than later, so bad actors do not attempt to collect encrypted communications and then decrypt them in the future using quantum computers. By getting people’s messages post-quantum-safe now, users won’t have to worry when quantum computers start cracking legacy encryption. Overall, I would recommend this app to people who are already past WhatsApp and Messenger and have perhaps begun using apps like Telegram or Session. It shares a lot of characteristics with these apps and goes a lot further than Telegram in terms of security. By being based on email, it is also resistant to censorship, and the lack of a username and password makes you anonymous (if you want to be) and safe from brute force password cracking attempts. Let me know in the comments if you’ve tried Delta Chat recently. Do you think it's a good bulwark against governments that are tightening their grip on the internet?
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!