Moving incomplete µTorrent downloads to a different computer

If you use µTorrent, you might have wondered how to move your download to a different computer, without losing the progress of the downloads which have started but have not completed. Now, here is how you can do it.

Prepare the files for transfer:

1. Shutdown µTorrent
2. Copy the contents of %appdata%\utorrent folder to a portable storage device (USB drive, etc). Actualy, the most important file which is required is resume.dat. But I would suggest copying the entire folder, just for simplicity's sake.
3. Copy the folder/files in which the partial downloads of the in-progress downloads are to the portable storage.
4. Copy the files from (2) to %appdata%\utorrent on the second computer
5. Copy all the files from step (3) to the second computer
6. Download BEncode Editor from https://sites.google.com/site/ultimasites/bencode-editor
7. Using BEncode Editor, edit the resume.dat in %appdata%\utorrent by using the function 'find/replace' to change the path or drive letter if the destination path of the partially downloaded file has changed.
8. Start up µTorrent and the download should continue from where it left off on the older computer.

Enjoy!!!

Changing the Windows 7 Logon Screen image

There are numerous ways to change the background of the Logon Screen in Windows 7. All possible methods, including the steps, can be found in the tutorial below:

How to Change the Windows 7 Log On Screen Background

From the tutorial in the link above, the easiest way IMHO is to use Julien Manici's Windows 7 Logon Background Changer. The application's title speak for itself - it does exactly what it says it does - and it is really simple and hassle-free. And to top it off, it is FREE!!!

PC Hardware Review websites

Here is a list of some websites which contain PC hardware reviews:

• Tom’s Hardware Reviews
• Overclockers Club
• Legion Hardware
• Hardware Canucks
• HardOCP

Fixing problem of NFS mounts specified in /etc/fstab not being mounted at boot

When using SUSE11 (and possibly other flavours of Linux), there could be issues in nfs mount to successfulyl get mounted at boot up time, even though already specified in /etc/fstab.

There is a basic workaround for this, where the command "mount -a" can be manually entered when you log into the system the first time after each boot up.

However, if you wanted to fix this once and for all, there here's the solution. Open the file /etc/init.d/nfs, and change the following lines (the text in green are the additions that need to be made):

if test "$nfs" = yes ; then

sleep 10 && mount -at nfs,nfs4 > /dev/null 2>&1

sleep 2

fi

The value of "10" for the first sleep could be changed to a lower number, e.g. 5, but I decided to choose 10 just to be sure that the network was up and running for the nfs mount to succeed. This sleep period value could be increased/decreased to suit your needs.