I'm very curious to see Intel APX and especially cooperation with the rest of the OS.

Another fun troubleshooting.

dism /online /Cleanup-Image /StartComponentCleanup

...will fail and completely roll back all attempts at cleanup, if the oldest CbsPersist_XXX.log somehow reached near 4 GB and thus can't be compressed into an existing .cab archive. Something totally courtesy.

I could really use having current NUMA node number in TEB. Updated on context switch by the kernel.

Why doesn't the system let you declare your own messages to have the same semantics as WM_COPY­DATA? - The Old New Thing Tempting but misleading.

Once again my annoying questions made Raymond Chen spin up a whole new blog post.

My assumption about VCRUNTIME was false, fueled by nonsense spit out by an AI that I asked out of a whim.

The real reason, as I discovered later, is that if the subsystem is 6.3+, the loader rejects images without CFG (control flow guard).

The second one. Third season was quite good too.

On the other hand, now that nobody will afford constantly buying new and faster hardware, maybe software devs will be forced to think again.

GitHub - tringi/shutdown-on-preempt: Proper OS shutdown on Azure Spot Virtual Machine Eviction Proper OS shutdown on Azure Spot Virtual Machine Eviction - tringi/shutdown-on-preempt

And yes I did.

Also the reports of @visualstudio.com 2026 (MSVC) no longer supporting Windows XP/2003 were somewhat exaggerated.

Numerous caveats apply, though.

I'm going to be adding XP and Server 2003 support to an app of mine in 2026, won't I?

This is what third glass of whisky in the middle of the day compels me to do.

So it appears, that for such EXE to launch, it MUST be built with CFG.

The /guard:cf option by itself won't do anything though. It will be silently ignored. The libcmt.lib must be linked in!

GitHub - tringi/subsystem-10-load-failure: Plain EXE with subsystem set to 6.3 or higher fail to load without VCRUNTIME140.dll. Why? Plain EXE with subsystem set to 6.3 or higher fail to load without VCRUNTIME140.dll. Why? - tringi/subsystem-10-load-failure

"Fun" Windows programming forensics exercise: Why does this not load when EXE subsystem is set to 6.3 or higher, but runs perfectly well when it's 6.2?

I think APIs like SetLastError/GetLastError should be finally replaced with inline code in the SDK.

It's not like TEB is going to change. Everyone's accessing it directly anyway.

Clean shutdown of Azure Spot Virtual Machines through something lighter than cyclically executing scripts?

Why of course!
Use my slim service (open source) to do what Azure should be IMHO doing on it's own. Note the size :)

github.com/tringi/shutd...

Twitter

Nah, I'll just keep making normal EXEs.

This is the first time I see explicitly stated, what AVX512 extensions are considered AVX3 to AVX9. Is that in any way official? -ish?

C:\> compact /C /S:C:\ /I /F /EXE:LZX

True enough. I'm looking forward to when these (and compilers) are eventually available.

A while ago I did a fun benchmark of performance improvements from using 32-bit pointers instead of 64-bit ones, and this is the same theme, just a different cache.

Also, why it's just doubling registers? Why not 64 or 128 even?

Then most functions would fit their entire working set into registers, completely rid of movs for stack/register swapping, relieving I$ pressure, register renaming, and even allow for some way better __fastcall2 calling convention.

I'm kind of wary of the real world benefits of APX.

All those very common instructions getting additional byte(s) of prefix will greatly increase L1 instruction cache pressure.

The worst programming language of all time YouTube video by Lazo Velko

Well, it's C++. You can give out points in machine gun cadence and still have it 2 hours long, like this guy:

Won't install onto a handcrafted 4Kn VHDX.
Otherwise seems working alright.

14.36 is the most important one to me. It's the last one that can generate binaries working on Windows XP.

So let me get this straight... a person with Tourette's, who inspired a movie about people with Tourette's being misunderstood, has an involuntary fit of Tourette's ...and gets misunderstood.

...by the very same audience who highly acclaimed the movie itself.

A solution to OpenGL apps, like my Starfield Screensaver (tringi.trimcore.cz/Starfield_Sc...), sometimes breaking HDR and brightness:

NVIDIA Control Panel -> Manage 3D Settings -> Vulkan/OpenGL Present Method -> Prefer layered on DXGI swapchain

If I set DWMWA_SYSTEMBACKDROP_TYPE, then DWMWA_CAPTION_COLOR must be either set manually, or to DWMWA_COLOR_NONE.

Because DWMWA_COLOR_DEFAULT swaps red and blue component of the default/system caption color.

Was that always a thing?
Or am I breaking something again somehow?

finally. #embed It happened. Nearly 5 years of paper writing, being snuck Committee Meeting notes on the DL until I could access them myself and absolve my co-conspirators of their sins, 5 different implementations/p...

And that's just the bare surface of C++ std committee politics. They routinely nitpick to waste time of others, and vote against others' papers to shift limited resource to their one.

See how hard it was to push #embed through for this guy:
thephd.dev/finally-embe...

And since it's a well known person, everyone else piles on you too, and downvote you to oblivion.

And if you dare to talk back, you get warning from a mod for personal attacks and such.

Yeah. Ask me how I fucking know.

And the very first comment is some old guard from the committee ripping you a new one for not having written a whole fucking paper solving all the dependencies on other features and pending papers too.

Some other comes scolding you for not having clang forked and implemented it yourself yet.

They'd tell you: "Because nobody proposed it, yet. If you want it, do it."

So you go to learn about the process, and the first bullet point says: "Don't write full proposal at first, float the idea on social networks and forums."

So you create a thread to "float the idea" on /r/cpp for example...