Didja know that STARCRAFT II don't run so well on multi-core systems?

Well, you do now! But be of good cheer: I'm about to tell you how to fix that.

I've had StarCraft II for awhile now, but haven't played even anywhere close to finishing the first campaign. Among other reasons, I've been frustrated by what I have been certain is too slow performance for the high-end rig I've got it installed on. And yesterday, I finally set out to find out why (or if I was even right about that).

Turns out that StarCraft II doesn't like multiple CPUs all that well. Optimally it should be running on two cores, not three or four. So Yours Truly went searching for a way to bring it down to operating on only two processors. Lo and behold: it can be done! Start up StarCraft II from the desktop, then bring up Task Manager (usually done through CTRL+ALT+Delete), go to the sc2.exe process and right-click on it and look for "Set Affinity". From here you can specify which CPUs you want to run the game on and which ones to turn off.

I tried it yesterday and the game performed significantly faster than it had before.

But, there was one hitch: every time the game is exited, doing Set Affinity through Task Manager must be done all over again. Leaving the program causes CPU affinity to revert to the default four cores (or whatever is the number of cores on your computer).

This is the kind of problem that, I can sometimes be awake for days trying to solve. I just don't like it when I've a gut feeling that a technical issue can be resolved, given enough time and thinkin' about it.

Well dear readers, a short while ago I came across a fix.

Actually, good friend Adam Smith located the substance of the solution, so credit goes to where it must :-) If you're trying to get StarCraft II - or any program that might run faster on one or two cores instead of four or five or seven - downshifted from too much processing power, then PriFinitty is the tool you need. PriFinitty (currently at version 2.47) sets affinity for whatever executable programs you need to do it for, and it keeps the affinity settings in a profile that loads automatically whenever you launch PriFinitty (which can be set to load at startup). I set StarCraft II to use CPUs 2 and 3, ignoring the rest, and it worked beautifully! Then I exited the game, and re-launched it. The affinity settings were still binding just those two cores! So... color me impressed :-)

There is just one thing that I need to say about using PriFinitty with StarCraft II: you should have PriFinitty set affinity for both "starcraft ii.exe" and "sc2.exe". But there are more than one version of sc2.exe to consider: they're all in the Versions folder of the StarCraft II main folder. And then you'll have to look in the folders in the Versions folder that say "Base..." (my install has six of 'em currently). So, I'd recommend going into all of the Base* folders, and adding each sc2.exe to your PriFinitty profile and adjusting the affinity for each. Y'know, just to be on the safe side. I don't see how doing it to any extra sc2 executables is going to do any harm.

Then make sure that PriFinitty is running in the background with your profile and launch StarCraft II and prepare to take the fight to the Zerg faster than ever!

(And a tip o' the hat to Adam Smith for pointing me toward PriFinnity :-)

Read More

Microsoft stops selling Windows XP today

Today is the final day of widespread sales of Windows XP. After today, it will no longer be possible to purchase a new computer from any major manufacturer with Windows XP installed on it.

The operating system first went on sale on October 25th, 2001. So it lasted with full support for nearly seven years: not bad for any software product but especially one from Microsoft, a company notorious for pushing updates on customers.

I was working at a Best Buy store when Windows XP was rolled out. Everyone associated with computers or media sales had to come in one Sunday morning prior to Windows XP's release for three hours of what I have since come to call "Microsoft religious indoctrination". We had to learn all about what Windows XP could do, what made it different from Windows Me and Windows 2000 Professional, all that jazz. I remember thinking at the time that this was so much ca-ca. That's not a knock on Best Buy at all: they're one of the best companies on the scene today. I just couldn't help but think that it was a little ridiculous to spend so much time being inculcated with the virtues of a bloody operating system...

(That I had to give up the weekend, which I could have spent driving down to Athens from Asheville to see Lisa, did not make me feel better about it either.)

And then sometime later, a few months before getting married, I wound up with Windows XP on my own system. And I promptly decided that the "indoctrination session" we'd been made to sit through was woefully unfair. That in fact, Windows XP was far better than Microsoft was making it out to be.

Windows XP was the most stable version of Windows that I've worked with since Windows 3.1 many moons ago. Not once did Windows XP crash on me or give me a reason to have to reboot. In fact, the only time that I lost any productivity with Windows XP came in January of 2003, and that was my own fault for failing to take precautions: a story that I was writing for the newspaper I was working at was lost because an ice storm knocked out the power and I hadn't saved it to disk. The next day I bought an un-interruptable power supply, and it hasn't happened again since.

And hey, it was Windows XP that I did my first forays into filmmaking. Now I'm working on Windows Vista and if it weren't for all the useless gimmicks like Aero being turned off, I wouldn't get any work done at all. Windows XP was not only stable, it was lean and mean. It respected its users enough to trust them with knowing whether or not something needed to be hogging precious resources. Let us hope that Microsoft has learned its lesson with Vista... but I cannot help but feel doubtful about that.

Anyway, let us raise a toast to Windows XP: the operating system that, whether it's widely appreciated or not, did most of the driving in this first decade of the new millennium.

Read More