Jakub Anderwald

Due to recent Starcraft 2 beta release, I started playing 3D games more often (almost daily, I must say). However, one problem appeared: my graphics card was overheating. I measured the temperature and it was going up to 110 degrees, then the game was slowing down making it hard to play.

I did some research on the GeForce 8800 GTS I am using and it turned out that:
1/ I am running those cards way too hot, even when idling.
2/ They tend to overheat, especially when they don’t have enough airflow.

As I have quite a dense environment with two GPUs, the overheating was understandable.

After some gooling, I found a custom cooler ZEROtherm Hurricane HC92 Cu 8800 to provide the best cooling results, but it was quite loud. I read some reviews of other 3rd-party coolers and they weren’t that effective, so I got the Zerotherm. Just notice, it will consume 2 additional PCI slots below you GPU, be prepared for that.

It came in a nice box, with installation manual (with miniature images, so I downloaded the PDF version to see them better) and all the required stuff. Unfortunately, I also got a dried-out thermal grease, so had to buy a new one in a nearby store.

The whole operation took around 1 hour. Here’s the toolset (thanks to my girlfriend for having the nail polish remover)

First step is to remove the OEM cooler from the card. There’s a lot of screws for that, also at the end you have to detach it from the GPU with some force Once you feel it moves on the GPU surface freely, it means it’s kept only by the thermal grease and you can pull it off safely. Then you get some alcohol- or acetone-based fluid and clean off the old grease from card. The results should look like this:

Then you stick all the small heatsinks onto memory chips, NVIO (with extra help from two plastic mounting legs) and FETs. The manual says here

Do not apply excessive force until the adhesive tape of the memory heat sink is completely attached.

which got me a bit confused, whether shall I apply excessive force after it’s attached or not. I decided not to try braking my card in half, but left the heatsinks movable a bit. They didn’t fall off, so I guess it’s OK.

Then you mount the central module with heat pipes and fan. Just remember to remove the transparent sticky tape from the copper base. I forgot to do it and had to remove the module again and add some more thermal grease. At least I realized before starting the card up!

Then you just need to mount the card back into your PC, find some space around it and you’re done!

There’s also a wired fan speed controller, which you need to place somewhere. I put it on top of my DVD recorder, so it’s accessible without opening the case, and not spoiling the looks.

So, how does it work?

Idle temperature fell down from around 75 degrees to 60. During gaming it’s between 75 (on maximum fan speed) and 90 (on lowest fan speed).

However, what’s more important – the binary result is “it worked”. I can now play games at maximum details and the card doesn’t overheat. I don’t really care if it’s 5 degrees higher or lower, I do care if I can use my card at full performance. Yes, I can – so this was a good investment.

As you can see, I joined Flattr beta.

If you don’t know it yet, have a look. It’s a flat rate (hence the name) donation system, where you pay some flat amount of money every month and it’s distributed to authors of things you “flatter” that month. To flatter a thing, click the orange / green button underneath each blog post.

Let’s see how it developes, but it might be “the way”.

I never liked Quicktime. The Windows player for it was always incompatible, slow, hanging. It also used it’s own chrome, so it never looked like Windows software. Since some time, due to fancy Apple Software update, it was trying to push some other Apple software (Safari and iTunes mostly) to your system with every update.

Because of that I never wanted to install the Quicktime player on my machines. I tried using Quicktime alternative codecs, or avoided having videos in Quicktime, but there’s always a situation when you get a quicktime video and have to see it, at least once.

Recently, I found a solution to that. I just upload the quicktime video to YouTube as private, and then decide if it’s worth keeping or not. I know it’s a twisted way, very slow and error-prone, but I am so happy I don’t need to install the player that I can spare those 10 minutes of my time.

This made me think: how far can you go in hating a product? I mean, the player is just a player, but I feel so much discomfort when I have to install it, that I will do a lot to avoid it. I felt the same way about Java applications, and luckily, they’re gone. It should be some kind of a warning sign for the seoftware vendor: if people hate you enough to use their time and resources (bandwidth in this case) just to avoid using it, you should rethink your strategy. Seriously.

The below registry hack will allow you to Open applications with multiple windows / tabs with single click. Single clicking will open the last active tab, while hovering mouse over the program icon will show all open tabs – like before.

Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
Go to Edit->New->DWORD (32-bit) Value
Name the value LastActiveClick
Hit enter to assign the value and change it to 1
Restart Explorer and you’re good to go

Just wanted to share one thing I noticed at work recently.

When you add a wildcard application map in IIS 5/6, there’s a checkbox called “Verify that file exists”. What it does is that it checks if the file called in URI actually exists on the file system before invoking the specified executable. If the file doesn’t exist, it will just throw HTTP 404.

This causes two issues:
1/ If you have an access control extension mapped like that (e.g. Siteminder), it will be possible to map your website structure without logging in – attacker can just iterate through all file names and find out which ones are there.
2/ If you have additional ISAPI filters mapped that reply to requests for files that are not on the hard drive, they will not be invoked. The first application mapping will reply to the request with HTTP 404. I had this case with Trace.axd file, which is served dynamically by ASP.NET. With the “Verify that file exists”, the request pipe was broken and it never made to ASP.NET