Technology

58303 readers

10 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

112

Remember that old BSOD screensaver from back in the day? TIL it's actually published by Microsoft (learn.microsoft.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

I remember installing this or a similar one on a friend's laptop, just setting it as the screen saver for later chaos. Must have been around Vista era.

Something incredibly funny to me about the fake Microsoft error being a Microsoft product.

More weirdness from the Sysinternals resources: one of the resources that MS actually recommends in the year of our lord 2023 is to actually go out and buy a physical book for their software:

https://learn.microsoft.com/en-us/sysinternals/resources/troubleshooting-book

I'm leaving that link as a URL on purpose. Just look at that. /troubleshooting-book. Amazing. The errata are updated online though. Very weird. Maybe leftover contractual obligation after acquiring SI in 2006? So weird.

They even suggest you go buy it from an independent bookstore if you're not feeling like the Microsoft Press Store does it for you.

I've always been fascinated by these third-party-but-now-first-party-after-acquisition situations everything doesn't quite line up neatly.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago

I actually found this because I was following a guide that needed Process Explorer to find out which damn program was catching my controller before DS4Windows was.

It was Firefox, specifically the Stable Diffusion WebUI for some reason.