in reply to Dan Fixes Coin-Ops

Lewd, car repair

Sensitive content

Commodore needles Microsoft over end of Windows 10, tries to lure disgruntled users to its Linux-based OS Vision 3.0 — 'Microsoft may be leaving you behind. We Won't.' tomshardware.com/software/oper…

A lovely follow-up to what is no longer any #curl license violation:

github.com/curl/curl/discussio…

#curl

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.
This entry was edited (3 months ago)
in reply to Tamas G

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 (3 months ago)

I always knew companies treat remakes as straight replacements of the original games but it’s still galling seeing it said this plainly. videogameschronicle.com/news/c…

Big F5 stuff dropping, starting with disclosure of incident and 8K filing. If you've got F5 in your stack, you're going to want to brew more coffee. No, more than that.

Keep going.

#threatintel #cybersecurity #infosec

infosec.exchange/@cR0w/1153783…

#AndroidAppRain at apt.izzysoft.de/fdroid/?radd=1… today brings you 16 updated and 2 added apps:

* Easy Launcher (Internet Edition): the minimal launcher also available at F-Droid, but here with added functionality and integrated weather widget 🛡️
* Eblan Launcher: another small homescreen replacement 🛡️

RB status: 730 apps (57.1%)

Enjoy your #free #Android #apps with the #IzzyOnDroid repo :awesome:

Well, we've reached the point where AI assistants (sometimes) write better code than me.

Codex just perfectly avoided a bug that I would have never thought about if I was writing that code myself. It was one of these suptle, pernicious issues that make your code return slightly wrong results instead of crashing, so it definitely could have slipped by unnoticed.

Weihnachten

Sensitive content

The first working release of Eloquence for 64-bit versions of NVDA is now available as an NVDA add-on. It even supports the Community Dictionary. A solid start overall, though some audio stuttering can be heard during Say All or other long NVDA utterances.
github.com/fastfinge/eloquence…
@NVAccess
in reply to JamminJerry

@JamminJerry I believe that @serrebi also did this, not sure if his is based on @fastfinge or other way around, or neither: github.com/serrebi/Eloquence64

What makes me happy to know is that every Windows 10 2021 LTSC user is seeing this message at the top of their Windows 10 update page, not just me:
"Your device is no longer receiving security updates. Learn about the end of support. link."
Ha. Yeah right, Microsoft. You're supposed to give Windows 10 IoT LTSC Enterprise support until 2032. Even so, regular Enterprise LTSC until 2027. So where's that promise?
As it turns out, that message is very generic and placed there for everyone, regardless of whether your computer can or cannot download updates. It honestly freaked me out, but then I imaged my desktop's Win10 image onto my Spectre, and since it didn't have the update, I was surprised to still see that message there but grabbing the security update. This tells me: They just placed a big warning on the update page to entice Windows 11 migration. Not today, Microsoft, not today, I'm not dealing with your fuckery.
"Seeing "end of support" on Windows 10 LTSC 2021 or IoT LTSC? Don't worry, it's a glitch – support " pureinfotech.com/windows-10-lt…
But then inside Microsoft's own "end of service statement" they list LTSC. (update: good news! Microsoft removed LTSC.) support.microsoft.com/en-us/to…
This entry was edited (3 months ago)
in reply to James Scholes

@jscholes yeah, in theory the LTSC versions automatically get them without an ESU enrollment, which is why I chose that path. Eventually I may end up migrating to Linux but Electron apps there like Slack would really royally suck. I'm seeing software already enforce a requirement for build 19045, which is why I did the unofficial upgrade to my LTSC to use 22H2, and I think at least until the ESU program itself ends (hearing 3 years max potentially for it) software should continue to support particularly if it's used in enterprise scenarios, which is good. Games, consumer-facing tools that need cool new NPU gadgets, well, those will most likely be out.
in reply to Scott

oh, just use this package someone made after modding it. github.com/teknixstuff/misc-fi…
Or, if you are like, "fuck you man, I don't wanna run a randomly prepackaged file with this!" Alright, alright. I get it yo. So, you can just grab: catalog.s.download.windowsupda… - see? It's from shiny Microsoft. You download the .msu, inside of it is a .cab file. You use 7-zip to extract that .cab file as well into a folder. Inside it are a lot of files, many ending in .mum. You need this command: dism /online /add-package /packagepath:C:\Temp\KB5015684\microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum
This will install it, and is the same thing the other file is doing. I know this because you can open that 22H2LTSC.exe file in 7-zip, and find the same files as from the .msu plus an install script .bat file that runs and does this, so yes, it's safe for sure, just packaged as a single .EXE file instead.
This entry was edited (3 months ago)

#фалыстыннаш

жалостливые рассказы об ужасающих лишениях и унижениях, которым подвергалась международная хамасня с флотилии сумуда продолжают регулярно поступать в ленту.

надо отдать должное - ребята воздерживаются от буйных фантазий, а описываемое вцелом не выходит за рамки суждений и допущений.