.net 3d art blog c# coding college computers editorial entertainment firefox food freeware gaming hardware hdtp hiking humor ide japan japan, javascript linux mac mailbox milestone misc. mods momoiwa, mono movie nintendo philosophy php politics rant rebun review science software technology time ucr wakkanai windows work wormholeftp
I migrated my computer over to the Beta release of Windows 7 before the new year. Every time I re/install an OS on my machine, I back up a few folders stored in the AppData folder containing Pidgin's chatlogs, Thunderbird's e-mails, and Firefox's browser preferences.
Dropbox is a relatively new automated file synchronization service that gives users 2GB of free online storage to synchronize documents to. Using a desktop app (available for Windows, Mac, or Linux), you can specify a single folder as your "dropbox", the contents of which are automatically synchronized to your storage space online. Your Dropbox account can then be linked to any number of other machines, and those machines in turn will download and make available all of the documents that have been synchronized to your account.
What does Dropbox have to do with backing up the three folders I mentioned earlier? Well, through the magic of a few NTFS Symbolic Links, I've managed to move folders that are otherwise in C:\Users\<username>\AppData\Roaming and place them in the folder I've designated as my dropbox in my Documents folder; as a result, I can keep all of my chatlogs, e-mails, and browser preferences automatically synchronized online and accessible from anywhere I have internet access, and I can easily restore all of those files the next time I install an OS.
To accomplish this, I used Vista's mklink command:
mklink [[/D] | [/H] | [/J]] link target
/D – Creates a directory symbolic link. Default is a file symbolic link./H – Creates a hard link instead of a symbolic link./J – Creates a Directory Junction.You can read more about the /D and /H flags with a bit of googling, but for now we'll focus on the /J flag. When set, the /J flag tells the OS to point any requests to the link directory to the target directory. Here's an example:
mklink /J "C:\Users\AppData\Roaming\.purple" "D:\My Dropbox\Pidgin"
First, we initiate the link program with mklink with the /J active. Next, we give the program the folder path that we want to link to another folder somewhere else in the computer. We're telling it to point (a hypothetical) Pidgin's settings and chatlogs folder to another location. That location is specified in the last folder path. In this case, I'm pointing it to the Pidgin folder stored within the Dropbox synchronization directory.
Before you hit enter, make sure the link folder is completely empty of any file or folder. When everything's set, hit enter and you'll have made a directory junction between the two folders.
It's worth taking a moment to explain how the OS handles the junction. First, if you go to C:\Users\AppData\Roaming\.purple, though it appears as though files are in the folder, what you're really seeing are the files stored in D:\My Dropbox\Pidgin. To Pidgin, it appears as though all the files it needs to run are in their proper location, but in reality it's accessing and modifying files in the Pidgin dropbox folder.
How does all of this fit in with Drobox? Each of the three Directory Junctions I created points to a target folder in the My Dropbox folder. Whenever Pidgin, Thunderbird, or Firefox makes a change to any of their files, Dropbox see the changes and synchronizes the files to my Dropbox storage space online. With just a few short minutes in the command line, I was able to automate the archival of some of the most important files on my computer and set up an easy means of accessing them should something ever happen to my machine.
I hope this tutorial helps out someone in a similar bind as me. If you find a better way of automating file backups to an online location (maybe even a personal FTP server!), let me know; I'm always looking for new ways to automate archiving of important files!
I was rummaging through some old Lifehacker posts when I came across a little gem called Vista Drive Icon.
What does Vista Drive Icon do?
It implement's Vista's Hard Drive capacity meter in Windows XP! This was one of the few features about Vista I liked; the lack of that feature made the move back to XP a bit more difficult, since now I had to right-click on a drive and click Properties to see how much capacity was available.
And the best part? It's freeware! If you're worried about memory usage, don't be; on my system it only used ~4.5MB of RAM, a measly amount in today's era of 1+GB of system RAM.