Day 3 of running Windows XP in 2025 is up.
I opened Enafore to check my Mastodon replies. It worked—for a few seconds. Then the notifications started. And they didn’t stop. Ping. Ping. Ping. I couldn’t reply. I could barely move the cursor. I watched the system buckle in real time.
So I tore XP apart.
I disabled over thirty services, deleted Windows File Protection, nuked the prefetch cache, rewrote shutdown behavior, and killed every background process that wasn’t strictly mine. If it touched the network, tried to log something, or ran without permission, it’s dead.
And you know what? Enafore runs fine now. JAWS doesn’t read new posts live, but I don’t care. I can read. I can reply. XP obeys.
Discord, though? Wouldn’t even load in the browser. Just a blank page. So tomorrow, I’m pulling in what channels I can through IRC. It’s not over.
Read the full post:
https://fireborn.mataroa.blog/blog/dead-os-walking-30-days-on-windows-xp-in-2025-day-3-i-dont-patch-i-burn/
#WindowsXP #Retrocomputing #BlindComputing #Accessibility #IRC #Mastodon #DeadOSWalking
@fireborn Really enjoying both this series and your other posts. Re: Discord, I recently became aware of a project called Discord Messenger which is a win32 Discord client specifically designed to be runnable on older Windows versions. I tried it briefly, meant to contact the developers to report a few things because they have it set up so that the arrow keys love putting you back in the box to type a message and the list of messages is a custom control not reachable from the keyboard, but the CTRL+K quick switcher is there and NVDA screen review was able to read the messages so the JAWS cursor should in theory work too. This is in case you need access to more than you'd get from your IRC bridge.
@fireborn How was processes simply being on the net causing it to do that, like that's only supposed to happen if you go onto some sketchy site. That's weird, XP shouldn't do that when the entire system accesses the net.
@fireborn I'm surprised that killing services made much of a difference. Windows XP doesn't tend to have nearly as much junk running in the background as later versions. I'm guessing you're running on a single core processor? Actually that might be a moot point since XP didn't handle multiple cores well.
@fireborn You should turn this system into a VM with NVDA instead of JAWS. I would kill for a Windows XP VM like this.
@fireborn Good article. Note about Discord: have you tried Discord Messenger - the thing that was made to run on Windows XP all the way back to NT 3.1? Might work a bit better than an IRC bridge. Matt KC made a video about it: https://youtu.be/wxdn30G2LE8
@fireborn I love reading this Windows XP adventure. I used Windows XP back in the day, and this is truly taking me back. :-)
@alexchapman it wasn't because of that, it was because of the background shit eating ram and CPU cycles for breakfast ,dinner and tea.
@fireborn Oh damn, just read through all the services and registry adjustments and stuff and wow. iDK what to say, but wow at least it didn't buckle. As for Discord you could try Supermium, that way you don't have to mess with IRC bridging.
@alexchapman it doesn't load. I tried.
@alexchapman Not really. an Intel atom n270 with 2gb of ram really isn't up for doing much.
@pitermach Will try this, thanks! I haven't had too much luck with the JAWS cursor not falling over, video intercept is a bit flaky on this machine.