I am far too visible and just a bit too known for my liking, given the state of things. I'm not entirely sure what to do about this situation other than shutting up and removing traces of my identity.
This entry was edited (29 minutes ago)
Just heard the sound of a dot matrix printer for the first time in years.
My family had one in Australia but it sounded very different to the usual sounds you get on YouTube, it was in the key of A and had this long tearing sound instead of the really quick ones.
When I was a kid that used to always sound to me as though the paper was being savagely tortured.
My family had one in Australia but it sounded very different to the usual sounds you get on YouTube, it was in the key of A and had this long tearing sound instead of the really quick ones.
When I was a kid that used to always sound to me as though the paper was being savagely tortured.
If any of y'all friends are on Windows 10, 21H2 LTSC, you can run a single file that upgrades you to 22H2, since it's just an enablement package. Someone turned it into a 7-zipped .exe with the update package contents, and a .bat file that runs to install it via dism. It's at github.com/teknixstuff/misc-fi… - if you want to do it manually you can, you just need the .MSU file for KB5015684, extract the .cab file from within using 7-zip, then run dism with the same commands as listed in the setup.bat file you'll see within that other script.
Essentially, since it is just an enablement package, it's flipping switches on internally that were dorment within your existing build. This is why a 100 kilobyte update can change your entire build number up by one, it fools you a bit, but your winVer should reflect the 19045 build numbering (might still say"21H2") after you run it. It may not say 22H2 until you do: dism /online /Cleanup-Image /StartComponentCleanup /ResetBase - this will roll the update into your image permanently, so use only after next month when we know this combination can in fact get updates just fine. Nothing would indicate otherwise, though, since your SKU remains LTSC 2021 evven after installing this pacakge.
Essentially, since it is just an enablement package, it's flipping switches on internally that were dorment within your existing build. This is why a 100 kilobyte update can change your entire build number up by one, it fools you a bit, but your winVer should reflect the 19045 build numbering (might still say"21H2") after you run it. It may not say 22H2 until you do: dism /online /Cleanup-Image /StartComponentCleanup /ResetBase - this will roll the update into your image permanently, so use only after next month when we know this combination can in fact get updates just fine. Nothing would indicate otherwise, though, since your SKU remains LTSC 2021 evven after installing this pacakge.
This entry was edited (47 minutes ago)
oh and I wanted to note. If you're *THAT* bothered by it still saying 21H2 for you, if it does, you can actually change the display info in registry, that's all the package would do anyway. Look here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion, in the right-hand pane, find DisplayVersion REG_SZ 21H2. Change it to anything. Even, "fuck you Microsoft for ending support for my OS!" Then when you open Winver you would see it, like "Microsoft Windows Version Fuck you Microsoft for ending support for my oS (OS Build 19045)" - it's great. Again, messing with this display string is cosmetic, so you're not breaking your system by changing it especially after installing the package.
This entry was edited (39 minutes ago)
At the edge of dawn and still a bit before daylight. Pointless ramblings before refocusing.
freshwatermedia.bandcamp.com/a…
#music for mornings #bandcamp #ambient #vaporwave #talkradio
#music for mornings
like this
An ongoing phishing campaign is targeting LastPass and Bitwarden users with fake emails claiming that the companies were hacked, urging them to download a supposedly more secure desktop version of the password manager.
Borris
in reply to Michael Marshall • • •Michael Marshall
in reply to Borris • • •Until recently I could hear the same kind of sounds at my supermarkets and in fact when they print out the receipt receipts, they still kind of sound the same.