When IE7 detects that you are entering a password into a web-form, it asks you if you would like this password to be “remembered” for next time. If you choose “Yes”, well and good. If you choose “No”, it will never ask you again—a problem if you later change your mind. Well, recently, I changed my mind.

I followed the instructions given here on watchingthenet.com. Upon revisiting the page in question and entering my password, IE7 once again asked me if I'd like the password to be "remembered". Yay!

I recently purchased a Gigabyte NX88T512HP 8800GT. I decided on this card as it shipped with a custom cooler installed, saving me the job of having to do this myself.

I didn't realise it at the time, but this card is also factory overclocked. In fact it is factory very overclocked. The stock speed for the core is 600MHz; this card is clocked at 700MHz. That's a very ambitious overclock, and indeed the largest factory setting I found after a quick glance around the web.

After I installed the card the screen would go dark at random intervals, sometimes at boot, sometimes after several hours, and sometimes during a game. Also the card would display the classic 3D freeze during a game, a sure sign that the card is being pushed too far. By the randomness of the blackouts, my guess was that the card (possibly the memory) was damaged, so I returned the card the next day.

I then waited a week until a replacement card was sent from Gigabyte. But this card too displayed the 3D freeze, something I had seen many times from my past youthful attempts at overclocking.

I was upset at this point. I did not want to wait yet another week for a third and possibly crappy card. I decided to return the card to its stock clocks. I used NiBiTor to capture and create a new BIOS, setting the clocks to their stock speeds of 600, 1500, 900 (1800). I then used nVFlash.exe running from a startup floppy to reflash the BIOS of the video card. So far a week on and all is well.

This is my first experience with a factory overclocked card—and it sucked. Please don't anybody buy this card.

Under OS X I wanted two things to happen every day. Firstly I wanted iTunes to download my podcasts before I woke - during the off-peak download quota offered by my ISP. And secondly I wanted EyeTV to delete the recordings it had made the day before, as those recordings would have already been exported to iTunes.

Using CronniX to edit the crontab file (which I find easier than using "crontab -e"):

iTunes actually doesn't need to be told to launch, after receiving the updateAllPodcasts command it launches and behaves as expected. Unfortunately EyeTV isn't as well behaved. I've included the same commands for iTunes as a matter of completeness. Note that "> /dev/null 2>&1" sends the output from cron to the big unix blackhole, else you'll receive e-mails everyday telling you if the jobs were completed successfully.

If your iPod is attached you can have iTunes complete a sync by issuing the AppleScript command update.

For example:

If your goal is to allow the currently downloading podcasts to be copied to your iPod you best allow some time for this to happen:

That's 10 minutes. I'm lucky to have a fairly fat pipe. You may have to allow more time.

My little brother (pictured) and I were upgrading and repairing a number of computers this afternoon. The resulting mess was so impressive I just had to snap this photograph. Fortunately we had the bulk of this cleaned up before Mum arrived home a few hours later.