4 ms·
You're right. I'll change it to "Windows XP or later".
by thingfish 1y ago
You're right. I'll change it to "Windows XP or later".
- bandrami 1y agoIDK, I wouldn't be surprised if it ran on Windows 2000 (still the best OS Microsoft ever made)
- heavensteeth 1y agoright, I suspect "NT" is the category they're looking for.
- guerrilla 1y agoWhat's wrong with 2003?
- actionfromafar 1y agoA bit bloated. I think NT 3.51 is the coolest, extremely stable.
- chuckadams 1y agoThe NT 3.x series might have had stricter userspace separation than 4.x did where they moved things like GDI into kernel space, but it still fell over hard at even the faintest whiff of fuzz-testing the native API. It wasn't until 5.x (Win2K) that they started taking that sort of thing seriously.
- tomrod 1y agoIt's worse than 2000, IMO, bloated and not super stable like 2000. Using Windows 2000 is like using a well-crafted Linux distro. Things just work.
- yellowapple 1y agoIf Microsoft had just iterated on Windows 2000 forever instead of continuing with XP/2003 and beyond it's quite possible I wouldn't be a Linux desktop user today.
- bayindirh 1y agoWindows 2000 was not developed for x86 directly. It first started on Alpha, then ported to x86, so its codebase is "double-brewed" in a way. I also remember 2000 as the only rock solid Windows release, and I never had to reinstall it. XP was very close to that after it fully matured, but nothing feels like 2000. [0]: https://en.wikipedia.org/wiki/Windows_2000 https://en.wikipedia.org/wiki/Windows_2000
- adra 1y agoThe two OS kernels and API are super close (outsider perspective). I used win2k for like 10 years mostly on the back of applications and games supporting XP for so long. I can't recall the big API differences. Maybe XP has UAC and there were APIs to check for it? Anyways, I still have fond memory of manually patching out API calls hard coded into EXEs to bypass XP only parts which were almost always superfluous.
- bayindirh 1y agoYes, I'm aware. Normally they shouldn't behave wildly differently, but the new GUI and userspace features made the system a bit flaky at first. Also, XP became a bit more finicky about drivers over the years, and this broke stuff, too. 2000s kernel was one of its better features, but lack of blingy GUI was also helping in its stability IMHO.
- chungy 1y agoThat's not really quite accurate. Windows NT began life on the i860, and then was ported to i386 and MIPS, and very shortly after the initial release, ported to Alpha. A year after that, PowerPC. Through the life of Windows NT 4.0's life span, MIPS and PowerPC died early, and Alpha support was axed just before the very end. In Windows 2000's development, i386 and Alpha were the only ports left, and Alpha was axed before it could make it to final release. x86 and Alpha lived simultaneously for most of its development. It wasn't done "first" on Alpha (quite the opposite).
- creatonez 1y agoTrue, but the flexibility that two attempts at porting to botched architecture introduced also resulted in 2003 becoming Microsoft's first x86-64 operating system. The very next day after the 2003 release, they released Windows XP Professional x64 Edition based on the 2003 codebase, which a user could run on their brand new x64 computer without much of an issue -- that is, if they had even heard of it... it was under-marketed because they needed to save the hype for Vista. So the struggle and failure may have been worth it in the grand scheme of things.
- tomrod 1y agoHilarious that this was literally my exact thought.
- haglin 1y agoYeah, Windows 2000 was probably the best operating system Microsoft ever produced. It had no crashes, a snappy/intuitive/sleek user interface, and DirectX support for games. I am currently running Mac OS X because I never liked Windows XP/Vista/10/11. In hindsight, the progress Microsoft made in the ten years between Windows 3.0 (1990) and Windows 2000 seems incredible. They transitioned from a 16-bit shell running on top of DOS to a fully-fledged operating system with a hardware abstraction layer, preemptive multitasking, permissions, a registry, proper device drivers etc. Twenty-five years later, there has been basically no progress. At a minimum, I would have expected something like the Knowledge Navigator https://www.youtube.com/watch?v=umJsITGzXd0 https://www.youtube.com/watch?v=umJsITGzXd0
- musicale 1y ago> a fully-fledged operating system with a hardware abstraction layer, preemptive multitasking, permissions, a registry, proper device drivers etc. Windows NT, which was developed by people (Dave Cutler et al.) who knew how to design and build operating systems (VMS, etc.).
- fuzztester 1y agothere is a book about it, called "inside windows nt". I had read it back in the day, it is by helen custer. it talks about dave cutler's work on it, apart from other stuff.
- p_ing 1y agoGot a copy sitting right next to me! Along with Inside The Windows NT File System (and The Design and Implementation of the 4.4 BSD Operating System). 'Windows Internals' series is the successor to Inside Windows NT.
- fuzztester 1y agoha ha, mark russinovich is one smart dude. and so is charles petzold before him.
- zoobab 1y ago"later" is for lazzy developers. Better list the complete list of versions where it has been tested, like "Windows XP/7/8/10/11"...
- zoobab 1y agoThe frontpage says now: "It runs on Windows NT, version 2003/XP/Vista/7/8/10/11." Victory!
- tomrod 1y agoWin2k?
- dimava 1y agoAlso you are confusing Visual Studio and VSCode