The History of Windows XP
abortretry.fail
abortretry.fail
It should have been represented in this article and it wasn't. Truly that's a crime against those who have not had the opportunity to experience it.
I have the Windows XP tour music. I keep it in my library and listen to it. You can find WAV files if you know where to look. I keep the OOBE music in the same album (both the original and remastered versions).
Through this incredible multimedia presentation I had the opportunity to learn about wizards and how Windows XP is best for business. I think there was also something in there about how to open a window. Also, it had that beautiful compass icon and those unmarked Luna-style colored buttons that were used to select each section of the tour. They were my favorite part.
I miss those days.
In any case as you can see, experiencing this is like seeing the image of God on earth, like stepping into the holy of holies, the innermost part of the temple where God's presence on Earth is present. The Windows XP Tour was handed down by God to Moses and kept in a great ark, and it was lost when the second temple was ransacked. Then in the year 1999, Microsoft employees found it while on holiday and brought it back to the states. The rest is history.
I keep an XP VM in case I need to commune with The Tour.
I modified the WMA file that played during the XP OOBE on an image that was rolling out to one of my Customers. I knew who would be deploying most of the PCs. At a point about halfway thru the piece, when it gets kind of quiet and the melodic instruments fall away (right before the chanting bit, if I remember correctly) I mixed my voice quietly whispering the deployment person's name a couple of times. Sadly, I never heard of they noticed their name in the music or not. People moved on and I never got a chance to ask before they left.
What makes it so surreal is the intro starts out almost as an extension of the intimately familiar Windows XP startup sound (of course, the same person, Bill Brown, composed The Tour music). If you've never heard it before, or are only just young enough to be familiar with the startup sound, it might seem like some lost never-was artifact, an extension of the Windows XP branding you never knew about.
However that would also make you an ignorant fool for failing to be alive or aware of the majesty of The Tour at the time it was released. Thankfully I was blessed by god and his son, William Gates III, with the privilege of being an XP user shortly after it was released. To be fair, you have to have a very high IQ to understand The Windows XP Tour.
That was Windows 2000. Everything else was just downhill from there :) (well, Windows XP SP 2 deserves a special mention)
I hope commercializing reddit, fb, twitter and internet as whole will push people to join smaller forums again.
> Windows Whistler/2002/XP logo design concepts by Frog Design
I like how there's a vestige of “Windows 2002” in the little “Version 2002” on the bottom right of all the XP RTM packaging, which disappeared from the later SP2-integrated boxes: https://www.usatoday.com/gcdn/-mm-/0e422e4a7e951800d133d6d73...
Encarta quite honestly had a beautiful typography heavy, high contrast interface, one that still shapes my design/ui preferences to this day.
If anyone needs a new wallpaper for the week.. https://archive.org/details/bliss-600dpi png and https://archive.org/details/bliss-600dpi_202006 tiff
Neat. That spot on Route 12/121† is one of my favorite places to take people when they visit the Bay Area. My pic from a few months ago: https://i.imgur.com/e2jbdkx.jpeg
One thing that puzzles me though is how the story is always told that Charles O'Rear was on his way from Napa to San Francisco, i.e. westbound on the highway, but having been there it feels like it could only have been the other way around due to the angle of the POV compared to the road and the fact that when you're eastbound there's a big left-hand curve which commands your sightline to the left so it's easy to keep looking past the road and straight into Bliss: https://www.vintag.es/2022/08/bliss.html
†That particular stretch of road is both: https://cahighways.org/ROUTE012.html https://cahighways.org/ROUTE121.html
Windows XP was about the time I started moving away from Windows more definitively, even as a secondary OS. It was the product activation crap. My OS on my computer should serve ME, not be beholden to the vendor after I put it on. Of course, we didn't realize back then how bad things could/would get...
So for that reason, I'm not really nostalgic about Windows XP, or subsequent versions, the way some people are.
Although it is interesting to see what many now consider to be the bad ideas of Windows 8, get their start in "Neptune"...
I haven't looked back switching to Linux back then.
To me, Windows 2000 was peak Windows. Windows XP introduced activation, which I find an annoying hindrance, and weird UI decisions in the form of the Fisher-Price Luna interface and the search dog. It was all downhill from there, though Windows 7 was solid and I greatly appreciate the introduction of WSL in Windows 10.
Exactly! Well said.
It was shockingly better than Win98/ME but not if you were already running NT. Then, it was a step backwards.
Win2k was excellent if it did everything you needed from it, though. XP had some advantages (like better search capabilities) but most of them came later in the form of service packs.
Many of my Windows memories from those days were of running Spybot Search and Destroy for friends and family.
Vista was much better in that regard but had issues in performance of the UI (chasing compositing interfaces that Mac and Linux had for years before) and the annoyance of UAC. Both were good ideas but required buy-in from hardware and software vendors that was slow to arrive.
I remember the regular cleaning sessions I had to do for my mother. Which stopped once I got her a Mac mini.
I liked Windows 2000.
XP was a bloated mess to me (in 2001) and I switched to Linux, and started upgrading a discarded PowerMac I'd been given until it was usefully able to run the shiny new Mac OS X.
10.0, 10.1, 10.2 started to get stable and quick enough to be useful for some tasks, 10.3 sealed the deal and became my full-time desktop.
From that moment on, we could spend a lot more time talking, watching her TV shows, cooking. It's a quality of life issue.
WDM made graphics driver crashes not take down the OS plus no more window tearing
Shadow copies gave you file history (time machine without another drive)
No more running with full admin privileges all the time. Bitlocker was introduced
Yes, compatibility issues affected people to various degrees, and yes it required good hardware to run well. Intel's onboard graphics / 5400 rpm drives we're not kind to it. And there were too many editions
With good hardware Vista was peak Windows. I could go back to Vista but I couldn't go back to XP, there's too much we take for granted now
Still, it is an underappreciated technology even today, the ability to get a consistent/ incremental point in time backup
It's not like they got rid of shadow copy entirely so I don't know why they got rid of the file restoration UI
I'll be sad when they finally kill off wbadmin, I script that for nightly imaging to an external drive. I get multiple snapshots to restore to, I can mount the backups (vhdx) as a disk for quick-and-dirty access, and it is technically possible to do point in time file restore but in typical Microsoft fashion it's artificially limited, I've had to fire up an evaluation copy of Windows Server in a VM to do it. Argh
Conversely, there were plenty of times when volume shadow copy running was the problem.
Talking about my use of home PCs, of course.
I've literally never experienced a moment of "wow, I wish I had a shadow copy in place so I could help solve this problem."
I guess my backup solutions are more primitive, but certainly more predictable in terms of their effect on the system. I didn't turn off volume shadow copy for my own amusement, I turned it off because it was freezing some devices' availability for I/O while it did its work.
* I think it was not in Home Edition, so yes, thumbs down on that
It really wasn't. You can say XP was an enhancement of 2000, but Vista was it's own thing, they reworked a lot of the NT Kernel and moved stuff like audio and video drivers from kernel space to user space, which brough increased security and stability, but broke compatibility on hardware that didn't bring updated drivers which pissed off a lot of early adopters of vista.
- in explorer, Vista could show column headers in all views (not just details) making it easy to sort/group
- you could use the headers to set grouping
- grouping still showed all the files
- the left tree became buggy in Windows 7, it doesn't always scroll to the current folder (I think it's broken to this day)
- the "quick access" shortcuts in explorer (the top list) was its own section (so you could always click it) -- in 7 and later it is part of the tree so you have to scroll back up to use it
- dragging files into a folder in 7+ instantly sorts them in the view, rather than keeping them together until hitting F5
- windows media player got rid of "find in library", "recently added" playlist, "play all", the taskbar miniplayer
- Vista had peak taskbar tray. instead of the current all-or-nothing overflow thing, overflow icons would automatically show themselves and then hide again
- can't run Explorer as administrator anymore to temporarily access protected files
- movie maker gone, dvd maker gone, sidebar gone
> WDM made graphics driver crashes not take down the OS plus no more window tearing
It made it more stable, I don't care about tearing and stuff, but it robbed me of full-screen DOS windows and the ability to toggle a window to/from full-screen with Alt+Enter. I used that a lot.
> Shadow copies gave you file history (time machine without another drive)
But it's no use if the OS isn't stable enough to trust. So I kept my important stuff on servers, so lost this.
The same applies to openSUSE today.
> No more running with full admin privileges all the time.
A small win, for standalone machines.
> Bitlocker was introduced
Life is too short.
> yes it required good hardware to run well.
Never mind that. Nothing except the highest-end premium kit had the specs to run it well. You needed 2GB of RAM for half decent performance but new kit was shipping with 512MB.
> With good hardware Vista was peak Windows.
Nah. Not as bad as generally held, but not great.
> I could go back to Vista but I couldn't go back to XP, there's too much we take for granted now
I did:
https://www.theregister.com/2023/07/24/dangerous_pleasures_w...
It was glorious.
I’m a big fan of XKCD but, in reality, what most people (and employers) worry about is unauthorised third-party access to private data in the event a laptop is lost or stolen (most often by opportunist theft). Bitlocker — and other Full Disk Encryption technology — provide an effective mitigation for this situation.
But what is much more rarely discussed are the costs. There are multiple penalties.
It hurts performance.
It impedes dual-boot.
It impedes setup in general; you lose most of the nice friendly GUI tools, replaced by clunky harder CLI tools.
It makes data recovery vastly harder, which is one of those things people discount until they need it and then realise how critical it is.
It makes troubleshooting OS problems vastly harder. Many it simply prevents: the answer becomes, reinstall your OS and restore from backup. If you have no backups, tough.
It's inconvenient, unless you use modern TPM-backed systems, in which case it dramatically reduces the security benefits, while also severely reducing OS compatibility.
It adds a new vital credential people don't know they have and don't know they need to keep secure backups of.
It generally makes everything worse, to fix a threat that most people simply do not have.
The 2 employers I personally had who insisted on it published all the company info on my machines to Github anyway, making it not even security theatre. More like security pantomime: an act of pretending to pretend to do something.
The answer to all this is, in my experience as tech support type: don't do it. Conduct a proper analysis of who has what secrets and what they need to keep, and use other better-targeted tools just for them.
Because without that, it causes problems for no good reason. It's treated as a panacea but it isn't -- it fixes nothing for 99% of users -- and the very real problems and issues it causes are ignored.
This _may_ be worth it for some companies and organisations but it's not for anyone else. I can see its worth for governments and military forces but few others.
I run GNU/Linux on all my personal computers but the Windows 10 laptop from work came with Bitlocker installed and other than entering the PIN on start-up, it stays out of my way. Granted, I'm not dual-booting, saving important documents or running any backup tools; I mostly use it for browsing, Teams calls and SSHing into my Fedora workstation and other servers after connecting via VPN.
Also, in my case, performance was only noticeably affected when the IT contractors installed Symantec anti-virus which resulted in the laptop becoming a noisy heater every so often.
For what it's worth, I bought my wife a laptop for her birthday when she needed a new one and I never considered enabling Bitlocker on it. She wouldn't have any sensitive data on it so I figured there's no need.
If it's a Win11 machine with Secure Boot then there is a high chance it has Bitlocker on by default. You should probably check and disable it if you don't want it. It'll be a little faster, and easier to recover if anything goes wrong.
ABAN is the modern free replacement for DBAN once that went payware.
That's an exaggeration. I didn't have the highest-end premium kit. I had good hardware (I was a gamer after all), but I doubt very much if I had more than 2 GB memory and I ran Vista with zero performance issues whatsoever.
It did have faster file copying though. I'd say it had 64-bit for more memory addressing but that was actually available with XP as well.
Windows XP also had perfect timing for the beginning era of broadband and a generation spending hours on their computers.
You only need to look at the leadership at Microsoft who were in charge of Vista and Windows 8. They were “suits” who didn’t understand “mobile”, which was arguably confusing at the time. I vividly remember watching the release videos of Windows 8 and the interviews of the leadership clearly showed they had no concept of what they were doing.
An OS should be extremely boring. It’s an app launcher and file organizer. An OS shouldn’t be flashy. That’s why people have fond memories of Windows 2000 and XP.
Windows 10 can also be extremely boring if Open Shell is installed and some other tweaks. Same thing with Windows 11.
Windows 2000 was the GOAT, it looked perfectly OK, had NT underpinnings, was stable and had pretty good hardware support. You could probably run it today if you don't play games or have a non-postscript/HPL printer.
My old coworker at my first company gave it to me, I worked in an old mill building that had a random room for IT storage.
I also got a very old FreeBSD mouse pad from there too! I'm not sure if I still have it around.
I recall a handful of tools that anyone could use (I was 10-11 and could figure it out) to break and bluescreen Win 98 computers remotely.
10-11 year old me liked the XP theme, the icons were so “fresh”, nearly everything that came before was grey and boring (and the beige boxes didn’t make that better) so it was a welcome change to me at the time.
Now I’m old, I see the joy of grey high contrast consistent UI: what I am doing is more important than the shell around what I am doing.
I've got friends who ran Windows ME and it was rock solid. My experience was very very different, same with Windows 98 SE.
With that being said my PC with Win95 OSR2 was super stable.
Windows XP forced driver development to a more modern standard that made things more stable. Still not stable enough (Windows Vista and up enforced that more and more in their APIs) but with XP the days of drivers assuming they could take complete control of the CPU and various buses were over.
Of course the companies that made shitty drivers for 9x also made shitty drivers for XP, so old hardware and hardware with shitty drivers was still less stable than other new hardware available, but things were moving forward.
These days, it's rare to see a full BSOD in Windows on any hardware but the very shittiest, especially with Windows 11 thanks to its artificial hardware support cutoff.
Good gods no. But then in the business in the UK late-1990s, Wikn98 was known as "GameOS".
I ran NT 4 at home until W2K came out.
A lot of references, topics, and language patterns on here really highlight the fact that the userbase is somewhere between 35-45.
Still love Windows XP though.
I could make a similar argument for Win7 and the indie gaming scene.
That said, the Windows computers I remember were Vista or Windows 7.
Can't say for Macs, the district hadn't used those since the iMac G3. After I graduated it was only a couple of years (maybe 2015?) before they rolled out Chromebooks, so 7 didn't even have much staying power.
Shoutout to kipix studio deluxe.
Actually, mostly since Wxp was slow as a dog compared to W98, because W9x still had direct control of the hardware rather than the sluggishness-inducing Hardware Abstraction Layer (HAL) that NT has always had inserted between the OS and the devices.
W95 was noticeably faster than W98 was too, and both of course move like lightning-speed compared to W10 whose 64bit drags compared to W10-32bit, and W11 is more embarrassing as it continues to further slow with each update (almost every month now rather than only once per year), which makes W10 seem like it was a quite a bit less encumbered than W11.
I cut down Win95 to run from a 16MB SSD in 1996, paid for by PC Pro magazine. I knew that OS inside out.
Around the turn of the century my travel laptop was an IBM Thinkpad 701C, the famous "Butterfly". 40MB RAM and a 75MHz 486DX4.
Win95 was great on it, better than OS/2, but the thing is Win95 had a max of 4 IP addresses. In total.
I had a dialup modem (1), an Ethernet card (2), AOL for toll-free dialup (different stack, so 3) and Direct Cable Connection (4).
Add a different modem or Ethernet card and it couldn't bind TCP/IP to it. No more addresses.
I tried NT 4 but it had no power management, no PnP, no FAT32.
I tried Win2K. Not fun in 40MB of nonstandard (and so vastly expensive to upgrade) RAM.
I tried 98SE. Too big, too slow.
So I cut it down as hard as possible with 98Lite.
(Still around, remarkably: https://www.litepc.com/98lite.html )
No IE, no themes, no built in media stuff, no Active Desktop, and it ran reasonably on a 486 in 40MB of RAM.
And it supported more IP addresses!
But it was hard work to get it working, and it was never entirely stable.
No. I reject your statement based on considerable personal experience and benchmark testing.
98 was considerably heavier than 95.
Just look at the ISO files!
95 OSR 2.1 with USB support:
https://winworldpc.com/product/windows-95/osr-21
385MB.
98SE:
https://archive.org/download/windows-98-se-retail
622MB.
98 is a significantly bigger and more complex OS.
Same design, but a lot more stuff piled on top.
When people bought a new W98 PC, which was often the first computer for so many consumers, it really did perform quite similarly to earlier-adopters' W95 PC's that were already in action.
The specs on the newer hardware were so much better which made up for it, and progressive sluggishness of Windows was swept under the rug for mainstream consumers, continuing to an extent today. You know, like a snail without a shell ;)
This is why in the '90's when Grove was running Intel and Gates was running Microsoft, professional geeks coined the phrase: "What Andy giveth, Bill taketh away." They didn't wait until WindowsME to say this.
It wasn't really worth it for mainstream apps, but if you had a challenging Office 97 workload, with or without VBA, something like live "real-time" data acquisition, or god forbid any type of ML or simulation, the best improvement you could get was to wipe W98 off the HDD and start fresh with W95. It always has seemed like there was some uncalled-for obstacle to prevent easily installing a previous version of Windows on a new PC though.
Even now this still works to an extent, buy a new mainstream W11 consumer PC, install W10 in a regular ordinary Microsoft dual-boot configuration and see for yourself.
Most people would have so much SSD space left over they could even try a triple boot, how about that W10 ISO from 2015 if you really want to emphasize the difference in how much less sluggish things could have been now. Woo hoo. Plan to stay off the internet when booted to this one, in Device Manager you could even pre-emptively disable the ethernet & wifi.
Of course try it on a HDD if you haven't done that in a while, to see how that feels compared to earlier Windows when you were using nothing but HDDs.
Windows 8.0 is also still fairly installable in new PC's if you want to see what it was like when they had one of their many brilliant engineers taking focused responsibility to achieve faster boot times in particular.
Back in the day there used to be custom builds of Windows 98 that had Internet Explorer completely stripped out. Those were much closer to Win95's performance.
But boy are they sure fast.
But I wouldn’t daily drive one.
I think part of MS issue is that they keep bundling and pushing "crap useful to some minority" (as well as unwanted ads and features too) by default into ostensibly "your" system and making it hard to focus on what you want it for.
If you want it to focus on gaming performance... well it's more about arcane tweaks rather than having a turn off the shit button.
Maybe the coming Win10 EoL will see a few % points jump to Bazzite or some other linux gaming-focussed distro.
I could go on, but yeah, not sure how OP thinks that race cars aren't as safe as road cars.
From my enterprise image/push creation days one example of something I did find different between x64 and x32 was the specific driver bugs/performance. The thing is it went/goes both ways on that, sometimes it's the 32 bit driver that's bugged, sometimes it's the 64 bit driver, sometimes there was a special patch version of the driver but the vendor didn't post both builds. You get the idea. In this case it wouldn't make sense to blame the <x> bit OS variant as inherently being massively slower, but it sure might seem like that with an n=1 test.
The consistency is quite good.
It's actually such a simple comparison anybody can try it and see for themself.
Now that you mention it I actually did drive (rental) cars back & forth between airports when I was a student. We went south packed into one car, then came back from the resort areas in a half-dozen or more cars so they could replenish the ones needed in the rental lots hours to the north.
We really would all reach the destination at the same time, traveling at virtually the same speed, but you could easily tell the difference when you had a V8 under the hood compared to a 6-cylinder.
Neither one was a show-stopper and plenty of people wouldn't know the difference anyway.
It's not like some had air conditioning and some didn't, that was by far the most important feature, not performance ;)
Similarly, for the rental cars, if one you drove was really "lightening fast" compared to another rather than something you noticed while microbenching it up the on-ramp or similar then you probably deserve jail time for the speeding ticket. That or a Model T was a rental option :D. But again, the point was 2 cars of the same model with a different trim, not 2 completely different cars.
Yes, SP1 wasn't horrible if you could get it (but who can download something that big on dial-up?), but it still was not great.
A true Microsoft masterpiece, back when they still remembered how to build something that didn’t need 17 updates before lunch.
Even Apple would not deprecate an OS two months after its release. The AMD64 version was supported until 2014, the same as the x86 version. Itanium was a dumpster fire, and anyone who had any Itanium hardware would probably want Server 2003 anyway.