#NTFS って #Windows2000 になるときに断絶があった (そのための #WindowsNT 4.0 SP6a) 認識だけど、その後って断絶がないんですか? #Windows
#WindowsNT
Ah, yes, the groundbreaking revelation that #WSL2 is basically just a VM with delusions of grandeur 🤯. In a thrilling 9-minute dissertation, we're reminded that Windows NT subsystems are like the hipster cousins of VMs, still cool but desperately trying to convince everyone they’re not just living in the basement. 🖥️🧠
https://ssg.dev/isnt-wsl2-just-a-vm/ #VirtualMachine #WindowsNT #HipsterTech #GroundbreakingRevelation #HackerNews #ngated
🖥️💾💿🕹️💾 Una distribuzione fatta per i "nostalgici" grazie a ReactOS
Un tuffo nel passato con un sistema operativo moderno! 💾 Ti ricordi Windows 95? ReactOS ti offre un'esperienza simile, ma open source e completamente gratuita. Scopri questo incredibile progetto!
https://youtu.be/LUmDIlm8l5I?si=Hvq1EiiyHVXPm360
#opensourceitalia #unolinux #gnulinux #distro #ita #opensource #reactos #windowsnt
🚨 Breaking News: Windows 95 #UI Code Sneakily Invades Windows NT! 🎉 Turns out, Microsoft developers didn't have enough legacy code to juggle, so they decided to sprinkle some vintage UI magic dust on NT for nostalgia's sake. Meanwhile, the rest of us are still wondering if Visual Studio will ever run without needing an exorcism. 🧙♂️
https://devblogs.microsoft.com/oldnewthing/20251028-00/?p=111733 #Windows95 #WindowsNT #MicrosoftLegacy #Nostalgia #VisualStudio #HackerNews #ngated
How did the Windows 95 user interface code get to the Windows NT code base?
https://devblogs.microsoft.com/oldnewthing/20251028-00/?p=111733
#HackerNews #Windows95 #WindowsNT #UserInterface #TechHistory #Microsoft #DevBlogs
My analytics for MarkWrites.io show a surge of Windows NT visits. Over the past 24 hours it says 43% of my visitors are using that system.
That can’t be right. I thought maybe it was bots, but I’m not seeing an influx of those. And I have a huge bot blocking list as well.
Any ideas? Has anyone else seen this?
Windows NT 4.0 (and 3.51) finally gets a native NVMe storage driver!
After using Task Manager in Windows NT 4.0 for the first time and then going back to Windows 98, my life just wasn't the same. I now knew there was a better way to live. Even if that way meant sacrificing Device Manager.
Furthermore, #VMS pioneered advanced fault-tolerant, distributed computing with VAXcluster technology, which allowed multiple systems to share a single file system and management domain, establishing VMS as a leader in high-availability enterprise computing. These innovations influenced later designs, including Cutler’s subsequent work on #Microsoft #WindowsNT.
Via @unix_byte
@tantacrul At least the #developers of #finale had the honesty to understand that their software wasn't salvageable due to being stuck under rocks in a hard place.
I wished #Microsoft had the same honesty when it came to the #XboxOne or #WindowsNT Version 11 - both being objectively garbage from day 1!
@DarvenDissek @sebsauvage The fun part is that #QDOS stood for "Quick and Dirty Operating System" and was a one-person project by somebody who built a CP/M alternative by himself.
#Microsoft bought it for small money, relabeled it as #MSDOS and made their first Millions with it.
Furthermore: #Windows was a rip-off from macOS. And #WindowsNT was a dirty hit in the back while MS was (co-)developing #OS2 for IBM.
Most people don't even know about #Excel and (partly) #Word being a 3rd-party software bought by MS.
The main contribution by MS was not as a software developing company. Their core competence was taking money for something that was for free and widely shared and improved by all sorts of people before. They invented proprietary software, software licenses and mandatory software bundles with hardware with no option not to pay for it.
Whatever software decisions were made on top, were mostly really poor decisions IMO.
A 29th year birthday retrospective on Windows NT 4.0.
https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/
For my retro hobby, NT 3.51 is my preferred version because of its Windows 3.1-like UI, but in 1999, 4.0 was the first version I encountered in the wild.
The 1990s are still alive and feebly kicking. #windowsnt
I'm grateful for my first contact with the #GNU #Linux world in 1998, in the college #computer lab... despite the #WindowMaker #WindowManager hehehe
The previous year we used the #lab of another #college in the same #university running #Microsoft #WindowsNT 3.51
In 1999 I tried using Linux on my personal computer, and since 2001 I definitively used the #Brazilian #distro #Conectiva (now defunct)
I've pushed myself a bit and tossed a rough tutorial on cross-compiling for #Windows3, #WindowsNT, #Windows95, and #MSDOS with #OpenWatcom up on the web zone: https://indigoparadox.zone/tutorials/watcom.html
It's late, so I don't trust my proofreading, but I've been asked about this enough where a quick and dirty tutorial has become a practical consideration. Hopefully it's useful!
:windows95: They flipped the order, but nearly 30 years later it's almost the same UI.
First: Windows NT 4 (1996), Second: Windows 11 (2025)
Well, yes. It's Windows NT.
Everything in the Native API always returns an explicit NTSTATUS separately from (mostly via "out" parameters) actual result values.
OS/2 was the same, and it's one of the things that Microsoft and IBM did right. Albeit that POSIX Threads got this right, too.
The dates on all of those show that by the late 1980s people already knew that one could do better than setting errno or the result from one value according to a flag bit.
Did you know that the 'NT' in Windows NT stood for "Nine Ten"?
The intended core platform for the OS was the then-expected Intel i910 RISC processor, which was to be the rebranded moniker for the i860 that can be found in the wild. *
It never came to be due to the i860s terrible handling of context switching -- a capability that a CPU for a multitasking, multiuser workstation OS must be able to do _very_efficiently_. The i860 wasn't.
https://www.youtube.com/watch?v=WTkFGZqVCM8&t=459s
*** EDIT: Several have pointed to sources indicating differently that NT stood for N10, which was the codename for the i860, so -- N10, N-Ten > NT.
#TIL #WindowsNT #Windows #Intel #i860 #i910 #vintagecomputing #retrocomputing #OS #techhistory #RISC #x86 #processors #computers #computinghistory #Microsoft
In the meantime, Microsoft tried to ruin everyone's fun by making Windows NT 10.0 be the same version number as used by the marketing people.
But it's alright. It has slipped again. Windows NT version 10.0.26100 is is not called that by the marketing people.
One is not immune in the non-Microsoft world, though. Place these in the correct order:
Buster
Etch
Forky
Jessie
Potato
Sarge
Sid
Wheezy
Trixie
(-:
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst