Just recently, I read this article on Golem about Mouse Without Borders (in German).

Mouse Without Borders (http://www.aka.ms/mm)

My current project at work revolves around network communication. For several reasons I cannot work with a single computer and simulated networks, but I need two physical machines to do my work. And I hate switching keyboards and mice all the time. But, I thought, “how many people have such a problem. Surely not many.” So, I accepted it. And now, Mouse Without Borders comes totally unexpected to my aid. Awesome! And it works!

Windows has a lot of nice features nobody knows about. And with some of them I am really wondering why. A good example are links: hard links, junctions, etc., not those silly shortcuts. NTFS has these things, it always had. And most *nix users know their way with these fellows to do cool stuff. Well, Windows has these too. They just never found their official way into the GUI. Most likely it was for political reasons, because the guys at Microsoft were afraid that the standard windows user would trap himself with these links and die. And most likely the guys are right on this. However, for us windows power users such links form great opportunities to optimize our systems. What is missing is usability. And this is where the Link Shell Extensions by Schinagl comes into the play. With this everything work great and nicely. What else could you want?

I may be in some aspects old fashioned. For example, I like to have my music locally on the devices I am going to play them at. So, I am grabbing my CDs and collecting everything as MP3s and Flacs on my hard disk. Then, of course, I have to deal with the MP3-tags, especially unifying them across the files. This is something, I wouldn’t need to bother if I would use an online service. Whatever.

After some try and error, I finally came across Mp3tag. It works and is nice to use when you are editing multiple files at once.

Today I am only writing a short comment: with WinDirStat there is a further alternative/successor of SequoiaView. The tool itself is a clone of KDirStat, but who cares. The only important thing is, that the great visualization of space consumption on your hard dist is available in one further tool for all of us to use.

Up until now I was using WinAmp, but since this project has reached its end, I started looking for an alternative.

One problem I was avoiding for quite some time now is the use of a media library. I buy my music very old-stylisch on CDs. And because these disks are so bulky to use I grab them. Thus my hard disk stores lots of MP3s and FLAC files. The grabbing, however, bores the problem of tagging. Thus, the tags of my files are only as good as I was motivated at that time, that is, the tags are horrible. Therefore, I did never use a media library but instead organized my files in directories and subdirectories as good as possible, which is not very good at all.

On my search for a new player software my friends told me about FooBar2000, most likely the software with the strangest name ever. … However, since I got curious I gave it a try. And now I am enthusiastic about it.

The minimalistic GUI is for sure not for everybody’s taste, but I like it. I never understood why the windows of some applications, including WinAmp, need to look “different”. Whatever.

What really sold FooBar2000 to my, were the integrated tag editor and the flexibility of the media library. I mostly listen to soundtracks and thus a sorting by artists or genre does not make much sense for my collection. With some custom tags and one simple expression for the tree structure the media library of FooBar2000 now meets my needs. In very short time I slapped this expression together which does what I want:

%<genre>%[|%<group>%]|[%album artist% - ]%album%[|%<extra>%]|[[%discnumber%.]%tracknumber%. ][%track artist% - ]%title%

I use the tags “group” and “extra” to get my special sorting I am used to.

I love it.

Today, I want to talk about another tool which is not written by me: ReplaceVistaIcon (aka SetVistaIcon). This is a small windows command line tool which sets or replaces native icons in windows executables.

My usage scenario is mainly connected to my work with .Net applications:

Nowadays I mostly write my smaller utility programs in C#. Simply because it is simple. Often I also define my own file types together with the utilities. So far so good. The problem arises when I want to give these file types dedicated icons, and when I want to place these icons inside my application (I do not like small utility applications, which consist of a thousand files). .Net application also contain a native Win32 resource section. It, however, is usually automatically generated by Visual Studio. If you want to add further native resources, that generation is no longer a viable option.

The normal way around this problem is to provide the complete native resource section manually. This, however, is tiresome because you lose many nice features, like the automatically generated application manifest and the generated version information section.

That is why I use ReplaceVistaIcon after successful compilation (post build event) to add further Icons to my applications.

Today again I want to talk about a tool I do not want to miss anymore: KeePass

It is a nice editor for encripted password data bases. Since a friend of mine told me about that tool and since I tried it, I have to memorize far less passwords now. More importantly, I now use generated, secure passwords everywhere. Thanks to KeePass these passwords are entered automatically without ever appearing on my screen and without ever being typed in on my keyboard.

Ok. The whole security-thing is sorta paranoid. However, KeePass is convenient to use. Convenient and secure! A great combination.

Today I want to introduce a new Category for my website: “Tool links”. Here, I will link to tools by other people. (Small) tools which I like and which I use myself.

I will start with “Everything” (http://www.voidtools.com/). This nice program directly reads the NTFS partition table. Results for file-name-based searches are available in parts of seconds for the whole file system. There is no faster way!