Tag Archives: registry

How to Export PuTTY Saved Sessions CodeUnit 11 FEB 2013

If you are a developer and you make use of the Windows operating system, then you will undoubtedly be more than just a little familiar with the fantastic PuTTY telnet/ssh client written and maintained by Simon Tatham.

I manage a fair number of servers over SSH and it is always a problem when I change my primary work machine as there isn’t a simple way to transfer all of your Saved Sessions over to the new machine.

Or rather, there isn’t any obvious way of doing it.

Turns out that exporting your Saved Sessions is a matter of registry manipulation, as the software saves everything over there. This makes it a simple task of exporting all the relevant keys using Window’s standard regedit utility and then importing them on the new PC.

To achieve, fire up a command prompt and enter:

regedit /e "%userprofile%\Desktop\putty-registry-export.reg" HKEY_CURRENT_USER\Software\Simontatham

This will generate a .reg file on your desktop which you can then move across to your new machine. Once there, you can either restore using regedit and the /s switch, or simply right-click on the file and select the top “Merge” option.

Nifty.

Ubuntu Maverick Meerkat: GConf Cleaner to Boost Your Performance! CodeUnit 01 NOV 2010

Just like its commercial big brother, Windows, Ubuntu sometimes manages to miss deleting certain keys or associated data when you uninstall programs or packages. Needless to say, this affects your GConf Database which could in turn become unstable and might even go so far as causing some problems further down the line.

So how to remedy this and perhaps improve performance all in one go?

Well GConf Cleaner is a handy little tool that scans your GConf Database and removes keys not associated with any schema. First off, you will need to install GConf Cleaner via the Ubuntu Software Center. Once installed, you’ll locate the launcher icon under the System Tools menu option on the system menu bar.

From there, follow the on-screen instructions, make a back up of the registry when prompted and watch GConf Cleaner work its magic.

Nifty.

Clean up Windows Registry: CCleaner Software & Sites 04 DEC 2009

ccleaner-logo-on-pedestalCCleaner has for years been one of those must-install tools, essential for automating that icky task of keeping Window’s registry as spotlessly clean as possible.

What it is, is a compact, pretty lightning quick piece of software that automatically scans through your PC and removes any unneeded temporary files and logs, cleans out your registry and helps better protect your browsing privacy should there be anything you don’t want someone else to know of (like all those filthy Internet pictures of Sasha Grey of course! :P).

The registry clean-up helps remove broken uninstaller links, orphan registry entries and better control startup applications. The removal of temporary files helps recover underutilised disk space and in the process, helps better protect you against identity theft by properly cleaning up your Internet browsing trail.

It features a particular friendly user interface and has enough checks in place to ensure that you don’t get into too much trouble cleaning up your machine, meaning that almost any level of user should be able to use the app relatively comfortably.

In other words, well worth checking out if you find yourself running a particularly sluggish and old installation of either XP or Vista then!

Windows XP Locking Video Files Software & Sites 19 JUN 2008

AVI IconWindows XP has a nasty habit of locking corrupt or incomplete video files, and you’ll often find yourself screaming in frustration as your latest attempts to delete the offending file keeps resulting in an annoying Windows error message proclaiming:

“Cannot delete FILE_X: It is being used by another person or program. Close any programs that might be using the file and try again.”

It turns out that the problem is caused by Window’s pesky Windows XP Shell Media Extension (shmedia.dll) which is the .dll that Windows uses in order to give you all those nice video file statistics in the Explorer status bar, as well as the video preview thumbnail that appears under the file’s details tab to the left of the Explorer window.

The problem is that when shmedia.dll encounters a corrupt or incomplete video file (or even one simply using an unknown codec), it crashes, effectively locking the file. And because the .dll is executed under Explorer, the file will basically remain locked until you logout and log back into Windows!

Now you can try killing the Explorer process from Task Manager and then deleting the file via the command line, but often this rather simple solution fails to do the trick. Of course, if you don’t like using the command line to delete files anyway, you can take a different approach by temporarily unregistering the offending shmedia.dll (run regsvr32 /u shmedia.dll), restarting Explorer and deleting the file, and then re-registering shmedia.dll (run regsvr32 shmedia.dll). This method is a little cleaner than directly hacking away at the registry, and if you find that you don’t actually need the data provided by shmedia.dll anyway, you may as well just leave it unregistered.

Note: There is also a bad bug in older versions of VirtualDub’s frameclient that causes shmedia.dll to fall over for all video files, not just broken ones. The problem only occurs if you have manually installed the AVIFile frameclient using auxsetup.exe and also enabled proxy mode via the proxyon.reg file. Uninstalling the frameclient or turning off proxy mode is usually sufficient enough to fix this particular problem. (Apparently this issue has since been patched from VirtualDub version 1.6.0 onwards)

(And as an extra little tip, you can also run regsvr32 /u shimgvw.dll to disable image previews, should they also be plaguing your system unnecessarily.)

For those of you who do however like mucking about in the Windows registry, there is yet another, more final fix to the shmedia.dll problem, a solution which basically stops Windows from loading the handler up in the first place. So after making a registry backup just for safety’s sake, you can remove the following key to give you the desired effect: HKLM, “SOFTWAREClassesCLSID{87D62D94-71B3-4b9a-9489-5FE6850DC73E}InProcServer32”

Hopefully you now have enough tools in your arsenal to deal with this rather pesky problem that’s been bugging me for ages already!