I just tried disabling nvsvc32, but I discovered that it doesn't exist on my system - the NVIDIA Display Driver Service is named "nvvsvc.exe" (and the Update Service Daemon is "daemonu.exe"), and while I did find an "nvsvc64.dll", I could not find a single file named "nvsvc32.exe" anywhere on my system.

Is this something that only exists in the 32-bit drivers (I'm running Win7 x64), or is it something that disappeared in the 310.70 drivers released last week?

How on earth do you translate 240p to "240 frames progressive" without making the [effectively] industry-standard terms "480i", "480p", "720p", "1080i", and "1080p" equally meaningless?

It means 240 scanlines progressive - old NTSC television sets normally like to run at 480i, but they're tolerant enough to handle video signals which don't have the extra half-scanline at the end of each frame and display it non-interlaced.

Microsoft's compiler has a similar warning - "C4706: assignment within conditional expression", and it actually doesn't let you suppress it just by adding extra parentheses - instead, you have to add a comparison around it.
Thus, your second example would have to be while ((list = list->next) != NULL)", which is probably more readable anyways.

They're probably using "apps developed for Windows RT" to mean "Windows Store apps that the developer didn't bother to compile for i386/amd64", which is going to be a very small set of apps (in practice, it appears to generally be the other way around - apps that the developer didn't bother to compile for ARM).

What you've said is certainly true... for Windows 95/98/Me, which were indeed built on top of Windows 3.1 and MS-DOS and not properly designed to be multi-user. If you think Windows 7 falls under that same category, you are sadly mistaken - that traces back not to 16-bit Windows 3.1 but to 32-bit Windows NT 3.1, which was designed to be multi-user (and even multi-CPU) from the very beginning.

If you did never lock up your drive wheels using engine braking, you haven't tried hard enough.

Last I checked, "wheel lock up" means the wheels cease rotation and start skidding uncontrollably, so the only way you could possibly lock up your drive wheels with engine braking would be if you stopped the engine - as long as it's still running (and the transmission is engaged), the wheels will keep turning (though they won't provide much torque unless you're driving an automatic and you're at a complete stop).

I will agree, though, that strong negative torque from engine braking (equivalent to what would cause your brakes to lock up the wheels) can definitely cause you to lose traction and start skidding, but it won't lock the drive wheels unless you define locking differently.

My guess would be that in low-traction situations, even light pressure on the brakes can be enough to lock the wheels, while engine braking cannot possibly cause the wheels to lock.

A man with three clocks will invariably find some convoluted way of using them to tell the time:

"This one runs ten minutes slow every two hours. This runs twenty minutes fast every four hours. The one in the middle is broken and stopped at two o'clock. I take the ten minutes on this one and subtract it from the twenty minutes on that one. Then I divide by the two in the middle."

EAS alerts have a distinctive noise they make before the announcement.

Specifically, that noise is a data burst which encodes most of the details of the alert (who sent it, what happened, where it happened, when it happened, etc.). Wikipedia provides a reasonably detailed description of the signal structure and the data encoding.

Sure it did - the turrets shoot plenty of bullets (and they shoot the whole bullet - that's 65% more bullet per bullet).

Simple - make it so applications have to be signed by Microsoft, a certificate on your domain controller/equivalent (for enterprises), or a "test" certificate that's specific to your own system so you have to sign everything yourself.

To make it even more annoying, force the user to boot the system with a special option (which you can't set in boot.ini) in order to disable signature verification entirely (like you have to do when developing 64-bit device drivers, from what I recall).

The term "homeopathic" specifically refers to medicines that are purported to be more effective the further they are diluted. Tapeworms aren't homeopathic - they're just one of many examples (another of which would be Radiation) of people using harmful things they didn't yet understand as if they were beneficial.

Killing Bin Laden does not weaken the terrorist threat and may well make all of this worse. Think Leia to Darth Vader "The tighter you clench your first, the more star systems will slip through your fingers like grains of sand."

Funny, I was thinking of an entirely different Star Wars quote - "If you strike me down, I shall become more powerful than you could possibly imagine." Martyrs are particularly difficult to deal with, after all.

This sort of thing has already been done with other works, such as some of the DVD releases of certain Looney Tunes cartoons bearing a disclaimer along the lines of "The cartoons you are about to see are products of their time. They may depict some of the ethnic and racial prejudices that were commonplace in the U.S society. These depictions were wrong then and they are wrong today. While the following does not represent the Warner Bros. view of today's society, these cartoons are being presented as they were originally created, because to do otherwise would be the same as claiming that these prejudices never existed ."

I don't think that game qualifies, since it's not a tournament system and it's not distributed. Besides, if it did qualify, there's no reason to single out my version of Promisance from the dozens of other versions that have been released over the years...