Are you kidding?
by AC - permalink
After putting it off and putting it off, after playing all the way through nearly every game I have, I finally gave in and just had to try to play some Half-Life 2. I love this game. It's one of my favorite shooters ever, but the instability that seems native to the otherwise brilliant Source engine makes it hard for me to even launch it. I know it's the engine and not just the game because Counter-Strike: Source and Half-Life: Source have the same problems. Source games have crashed my PC more spectacularly than any games I've ever played. But I may have found the problem.
Before starting another HL2 campaign, my first with my new CPU and PSU, I tried, yet again, to troll through the Valve support site and forums for some overlooked magical cure-all. In the middle of this year-old post, I noticed the following:
It can't be, I think to myself. WindowBlinds? Seriously? I've been using WindowBlinds for almost a decade. I'm a registered user. I paid twenty goddamn dollars for WB 5 (now 5.5), I look for new themes literally every day. I've never had it interfere with any game I've ever played. But I unloaded WB, shut down a couple of iTunes-related running processes that I've never been happy with (ituneshelper.exe and ipodservice.exe [I don't even have a fucking iPod]), and launched the game. And I played for two hours and it didn't even blink. Later in the day, after a reboot, I went back into HL2 and played for about 15 minutes before it crashed, and once again locked up my PC in the process. Then I realized WB is in my startup. I rebooted, unloaded WB again, and started HL2. I've been playing for over an hour.
This is insane. "Game freeze or crash with looping sounds" has got to be the most common Source issue ever, and of all things, I can fix it by disabling WindowBlinds? What the fuck? Obviously, I'll keep playing the game, and I'll update if anything else happens (like a crippling crash with no obvious cause).
Moving on. Seems Ars Technica agrees with pretty much all my complaints about the new Windows-compatible Safari 3 beta. They also raise an interesting question: if Apple is hoping apps like Safari (and iTunes) will sway Windows users toward switching to Macs, this is not the way to do it. Sure, Safari behaves on Windows just like it does on a Mac. But it's weird and inconsistent with the rest of my OS. That makes it annoying, not attractive. And releasing it with at least two downright dangerous security flaws is not especially compatible with Mac OS's image as the most secure mainstream operating system on the market. Don't get me wrong, gaming aside, I'd love to have a Mac as a second computer. But I think I'd rather run Firefox or Camino as my main browser.
by AC - permalink
After putting it off and putting it off, after playing all the way through nearly every game I have, I finally gave in and just had to try to play some Half-Life 2. I love this game. It's one of my favorite shooters ever, but the instability that seems native to the otherwise brilliant Source engine makes it hard for me to even launch it. I know it's the engine and not just the game because Counter-Strike: Source and Half-Life: Source have the same problems. Source games have crashed my PC more spectacularly than any games I've ever played. But I may have found the problem.
Before starting another HL2 campaign, my first with my new CPU and PSU, I tried, yet again, to troll through the Valve support site and forums for some overlooked magical cure-all. In the middle of this year-old post, I noticed the following:
"Tuneup WinStyler Theme Service has been found to cause a crash with the Steam client application and WindowBlinds may cause crashes with Source games."
It can't be, I think to myself. WindowBlinds? Seriously? I've been using WindowBlinds for almost a decade. I'm a registered user. I paid twenty goddamn dollars for WB 5 (now 5.5), I look for new themes literally every day. I've never had it interfere with any game I've ever played. But I unloaded WB, shut down a couple of iTunes-related running processes that I've never been happy with (ituneshelper.exe and ipodservice.exe [I don't even have a fucking iPod]), and launched the game. And I played for two hours and it didn't even blink. Later in the day, after a reboot, I went back into HL2 and played for about 15 minutes before it crashed, and once again locked up my PC in the process. Then I realized WB is in my startup. I rebooted, unloaded WB again, and started HL2. I've been playing for over an hour.
This is insane. "Game freeze or crash with looping sounds" has got to be the most common Source issue ever, and of all things, I can fix it by disabling WindowBlinds? What the fuck? Obviously, I'll keep playing the game, and I'll update if anything else happens (like a crippling crash with no obvious cause).
Moving on. Seems Ars Technica agrees with pretty much all my complaints about the new Windows-compatible Safari 3 beta. They also raise an interesting question: if Apple is hoping apps like Safari (and iTunes) will sway Windows users toward switching to Macs, this is not the way to do it. Sure, Safari behaves on Windows just like it does on a Mac. But it's weird and inconsistent with the rest of my OS. That makes it annoying, not attractive. And releasing it with at least two downright dangerous security flaws is not especially compatible with Mac OS's image as the most secure mainstream operating system on the market. Don't get me wrong, gaming aside, I'd love to have a Mac as a second computer. But I think I'd rather run Firefox or Camino as my main browser.
No comments:
Post a Comment