The guide to trading candy
Important information to know this evening.
Breaking news from around the world Get the Bing + MSN extension
Important information to know this evening.
Troy Martin is puzzled by the remark in this knowledge base article that says
No 16-bit code can run, except for recognized InstallShield and Acme installers (these are hard-coded in Wow64 to allow them to work).
I agree that the sentence is rather confusingly written.
Internally at Microsoft, we have a programmer’s tool which I will call Program Q. On the peer-to-peer mailing list for Program Q, somebody asked the following question:
What’s the best way to look at all tables created in the past week? I want to repeat this command across multiple table repositories.
Um, not really.
I dreamed that I was attending some sort of “how to be awesome” seminar where the presenter said, among other things, that a sea turtle, when left to thrive undisturbed, amasses $1 million in personal wealth within one year.
Today’s Little Program uses the
GetLogicalProcessorInformationEx
function to print the mapping of logical processors to
physical processors,
as well as the mapping of logical processors to packages.
(A dual-core processor is a single package with two cores.
If those cores are themselves dual-hyperthreaded,
Here’s a little puzzle
inspired by an actual bug:
// global variable
DWORD g_WorkerThreadId;
bool IsRunningOnWorkerThread()
{
return GetCurrentThreadId() == g_WorkerThreadId;
}
bool LaunchWorkerThread()
{
HANDLE hThread = CreateThread(nullptr, 0,
WorkerThread,
nullptr, 0,
&g_WorkerThreadId);
if (hThread != nullptr) {
CloseHandle(hThread);
return true;
Windows 7 introduces a new flag to the FindFirstFileEx function called FIND_FIRST_EX_LARGE_FETCH. The documentation says that it “uses a larger buffer for directory queries, which can increase performance of the find operation.” This is classic MSDN-style normative documentation: It provides “just the facts”.
A bunch of security vulnerability reports came in from the same person, all of the form, “Program X is vulnerable to DLL planting if you create a DLL with the name Y in a directory on the PATH,” with varying values of X and Y.
One of my colleagues told me a story from his days on the Windows team. He had to give a presentation to his vice president on his feature, and he prepared his presentation and demo obsessively to make sure it went smoothly.