Why is this even a question? The post A question about the maximimum number of values in a registry key raises questions about the question appeared first on The Old New Thing.

You can steal them from your owner. The post What if a dialog wants to intercept its own message loop? appeared first on The Old New Thing.

Because it opted out. The post Why doesn’t <CODE>WM_<WBR>ENTER­IDLE</CODE> work if the dialog box is a <CODE>Message­Box</CODE>? appeared first on The Old New Thing.

The dialog box lets you change how it waits. The post How can I change a dialog box’s message loop to do a <CODE>Msg­Wait­For­Multiple­Objects</CODE> instead of <CODE>Get­Message</CODE>? appeared first on The Old New Thing.

A very primitive version of recovery. The post Windows 95 defenses against installers that overwrite a file with an older version appeared first on The Old New Thing.

You'll have to ask nicely. The post How can I make sure the anti-malware software doesn’t terminate my custom service? appeared first on The Old New Thing.

Wrapping things up. The post Windows stack limit checking retrospective: arm64, also known as AArch64 appeared first on The Old New Thing.

Reaching the modern day. The post Windows stack limit checking retrospective: amd64, also known as x86-64 appeared first on The Old New Thing.

Double the size, double the fun. The post Windows stack limit checking retrospective: Alpha AXP appeared first on The Old New Thing.

Appeasing the invisible return address predictor. The post Windows stack limit checking retrospective: x86-32 also known as i386, second try appeared first on The Old New Thing.

Doing the math backwards. The post Windows stack limit checking retrospective: PowerPC appeared first on The Old New Thing.

Optimizing out the unnecessary probes comes with its own complexity. The post Windows stack limit checking retrospective: MIPS appeared first on The Old New Thing.

One of the weirdest calling conventions you'll see. The post Windows stack limit checking retrospective: x86-32, also known as i386 appeared first on The Old New Thing.

Don't take steps that are too large. The post How do compilers ensure that large stack allocations do not skip over the guard page? appeared first on The Old New Thing.

Oh, this old thing? The post A snappy answer when asked about dressing casually at IBM appeared first on The Old New Thing.

Think fast, no pressure. The post The fine print giveth and the bold print taketh away: The countdown timer appeared first on The Old New Thing.

Look for the conflicting definitions to see where they are coming from. The post Learning to read C++ compiler errors: Ambiguous overloaded operator appeared first on The Old New Thing.

It's already gone. If you need more information, you should have been remembering it. The post When <CODE>Read­Directory­ChangesW</CODE> reports that a deletion occurred, how can I learn more about the deleted thing? appeared first on The Old New Thing.

Perhaps it's because you dispatched it. The post The mystery of the posted message that was dispatched before reaching the main message loop appeared first on The Old New Thing.

Of course, anything can happen if you break the rules. The post Aha, I found a counterexample to the documentation that says that <CODE>Query­Performance­Counter</CODE> never fails appeared first on The Old New Thing.

Just some useless trivia. The post Just for fun: A survey of write protect notches on floppy disks and other media appeared first on The Old New Thing.