#windowsnt — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #windowsnt, aggregated by home.social.
-
ReactOS becomes more reachable by introducing a new live boot CD and an improved ATA driver!
#ReactOS #Windows #FOSS #TechNews #TechUpdates #WindowsNT5 #WindowsNT
-
The depressing thing about Windows NT 4.0 is you install it and it feels incredibly snappy compared to Windows 98 SE on the exact same Pentium MMX 233 MHz machine... and then as soon as you install Internet Explorer 4 to make it compatible with later software depending on the DLLs from that the performance immediately goes to shit with visible redraws in Windows Explorer which don't happen under 98 SE. RIP.
also god the IE integration into the shell for rendering the UI was such a bad idea, Electron 20 years before its time (derogatory)
-
Nachschub für die 90er Retro-Software-Sammlung! Heute gibt es die deutsche Vollversion des Betriebssystems "Windows NT 4.0" auf CD-ROM. Natürlich inkl. der kompletten ISO, dem Service Pack 6a und sauberen Scans in 600dpi. Einen Satz kompatibler NT-Bootdisketten habe ich ebenfalls verlinkt.
Ich bin auch heute noch immer wieder begeistert, wie cool diese klassischen Microsoft CD-ROMs aussahen!
https://archive.org/details/nt4_de-sp1_cdrom
Viel Spaß damit! 😜
#WindowsNT #WinNT #Windows #Microsoft #90er #90s #Software #Computing #Retro #RetroComputing #IBMPC #Betriebssystem #CDROM
-
Was Software für meine Retro-Sammlung angeht, bin ich kein allzu großer Fan von OEM-Fassungen, wie sie immer haufenweise diesen Fertig-PCs beilagen, sondern suche mir bevorzugt lieber normale Retail- oder Einzelhandelsversionen. Allerdings sind letztere oft leider echt schwer zu finden und kaum mehr zu bekommen.
Bei Windows NT 4.0 hatte ich jetzt aber heute echt mal Glück! Für nichtmal 9€ konnte ich diese Vollversion auf CD-ROM ergattern. Noch komplett eingeschweißt und neu in Folie. Davon hatte ich bisher auch tatsächlich noch gar kein ISO Disc Image im Netz gefunden...
P. S. Hier nun für alle der Download-Link: https://archive.org/details/nt4_de-sp1_cdrom
#NT4 #WindowsNT #Microsoft #RetroComputing #90s #90er #Retro
-
Was Software für meine Retro-Sammlung angeht, bin ich kein allzu großer Fan von OEM-Fassungen, wie sie immer haufenweise diesen Fertig-PCs beilagen, sondern suche mir bevorzugt lieber normale Retail- oder Einzelhandelsversionen. Allerdings sind letztere oft leider echt schwer zu finden und kaum mehr zu bekommen.
Bei Windows NT 4.0 hatte ich jetzt aber heute echt mal Glück! Für nichtmal 9€ konnte ich diese Vollversion auf CD-ROM ergattern. Noch komplett eingeschweißt und neu in Folie. Davon hatte ich bisher auch tatsächlich noch gar kein ISO Disc Image im Netz gefunden...
P. S. Hier nun für alle der Download-Link: https://archive.org/details/nt4_de-sp1_cdrom
#NT4 #WindowsNT #Microsoft #RetroComputing #90s #90er #Retro
-
Der beste Bluescreen der Microsoft Geschichte.
#WindowsNT #NT4 #Microsoft #Bluescreen #RetroComputing #90s #90er
-
Der beste Bluescreen der Microsoft Geschichte.
#WindowsNT #NT4 #Microsoft #Bluescreen #RetroComputing #90s #90er
-
Yeah... I got Windows NT 4.0 running with Service Pack 6a incl. drivers and all the latest updates from 1999 and even managed to install a few games: Windows Entertainment Pack, SimCity Classic and Age of Empires II. This is quite nice! Although I remember from back in the day that NT 4.0 only supported a very limited selection of games. That's why I always used it as part of a dual-boot setup with Windows 9x.
#RetroComputing #RetroGaming #Retro #Gaming #Windows #WindowsNT #Microsoft #90s #90er #PCGaming
-
Oh, wow.. also NT 4.0 hab ich jetzt echt schon lange nicht mehr installiert. 😉
#RetroComputing #90s #90er #Oldschool #Retro #Microsoft #WindowsNT #Windows
-
I am also quite impressed by Windows NT, as I learn more about its workings. For example, its desktop and session architecture is something Linux desktops could learn from.
...and then I remember what became of it :flan_despair:
-
I finally located the version for Windows NT 4.0. Firefox 2.0 used IPv6 automatically!
#RetroComputing #WindowsNT #IPv6 -
thinking about getting a lower back tattoo for my birthday...
#windowsNT -
Free to a good home: Crossword Construction Kit on 3 1/2" floppy for WIndows 95/NT. 💾 💾 💾 :win:
#FreeToAGoodHome #RetroComputing #VintageComputers #floppydisk #crossword #Windows95 #WindowsNT
-
Free to a good home: A Browser Mouse install floppy for DOS, Windows 3.1, 95, 98, NT 3.51, and NT 4.0. 💾 :win:
#FreeToAGoodHome #RetroComputing #Floppy #Mouse #DOS #Windows95 #Windows98 #WindowsNT
-
#NTFS って #Windows2000 になるときに断絶があった (そのための #WindowsNT 4.0 SP6a) 認識だけど、その後って断絶がないんですか? #Windows
-
#NTFS って #Windows2000 になるときに断絶があった (そのための #WindowsNT 4.0 SP6a) 認識だけど、その後って断絶がないんですか? #Windows
-
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 -
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 -
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 -
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!
-
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 -
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
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!
-
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!
-
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!
-
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!
-
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
-
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
-
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
-
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
-
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
-
Those who fail to understand Unix are doomed to forever keep trying to turn it into Windows NT.
#Unix #UnixPhilosophy #simplicity #OneJob #systemd #Windows #WindowsNT
-
I kinda just tend to assume that everyone has a copy of VirtualBox, #pcem, and a multi-TB stash of ISOs from winworldpc.com on their NAS... but I'm occasionally reminded that this is not the case. If this is not you, but you need access to real #WindowsNT or #Windows95 or #Windows31 for an experiment or two, consider this a reminder that https://copy.sh/v86/ exists. #RetroComputing #VintageComputing
-
I kinda just tend to assume that everyone has a copy of VirtualBox, #pcem, and a multi-TB stash of ISOs from winworldpc.com on their NAS... but I'm occasionally reminded that this is not the case. If this is not you, but you need access to real #WindowsNT or #Windows95 or #Windows31 for an experiment or two, consider this a reminder that https://copy.sh/v86/ exists. #RetroComputing #VintageComputing
-
I kinda just tend to assume that everyone has a copy of VirtualBox, #pcem, and a multi-TB stash of ISOs from winworldpc.com on their NAS... but I'm occasionally reminded that this is not the case. If this is not you, but you need access to real #WindowsNT or #Windows95 or #Windows31 for an experiment or two, consider this a reminder that https://copy.sh/v86/ exists. #RetroComputing #VintageComputing
