Had some problems with my DFS setup, not making it possible for my Windows XP machine to utilize the DFS share on my local machine. Som googling and the answer:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters] "EnableDfsLoopbackTargets"=dword:00000001
Or how to keep your start menu free of clutter. Do you like your Start Menu? After a while, after a number of software installations, the Start menu gets overfilled with items, organized sometimes after the vendor, sometimes after the application name. No one really knows! I would like to see a solution in the installer for this. In my opinion, the following guideline should help installers to actually put software into a somewhat more easily found location:
Every software must
With these premises, the explorer/installer would be able to put the intended shortcuts into a meaningful place. First there should be a branch of categorizes (in my likings the proffered branch), and one branch for vendors. In each branch the main shortcut should be put. Initially, only the main shortcut should be seen. hovering over, or using some kind of context menu, the “extra icons” would be shown. Clicking the shortcut opens the underlying application/document, as normal.
By using more than one path to find the application, I believe the user can reach the correct application easier then today, using its own preferred approach.
OK, you may argue that one can nowadays search the start menu, but searching requires knowledge of the application’s name or its vendor, and you never know which. If you don’t know the name, but are interested to find a graphic renderer, wouldn’t it be easier to browse in the Graphics Applications category?
Before the start menu gets intelligent, one can (kind of easily) organize it manually:
My current (fist level) start menu:
As you see, there are still some software not categorized, for example PowerDVD. its icons seams to be created by the application itself, no matter if I delete them! We do not have such thing as a perfect world 
I’ve had a number of issues playing WMA and WMV files the last couple of months. Both direct loading as well as streaming. It just loaded, then the status said ready! There was an error saying something like “protocol not supported” as well. Today I had it, when I missed the high jump final of the world championships in athletic in Osaka 
(instead I had to work)
So, with some trial and error I managed to correct it… it really took some hours ZzzzZzzz: This is what I did:
I logged in to the system as another (untouched) user. This user had no problem playing the files, meaning there is some user setting that have gone havoc. OK, back to my ordinary account.
Windows Media Player seams to store its settings in the following locations:
HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer, and in%USERPROFILE%\AppData\Local\Microsoft\Windows Media\11.0To see where the corruption is, I renamed each of the folders in order. After each renaming I started WMP and tested its functionality. Don’t worry, these folders are recreated when the application runs. OK, WMP pops up its initialization dialog.
The fault seamed to be in the second location. I just removed the renamed folder, and now I’m happy 
Ever got tired of all unpacking of scene releases where movies (and software)
is distributed in multi-volume RAR archives. For each archive you need to find the archive’s start file, maybe create a destination directory, copy the NFO file etc, etc…
This tool tries to ease the process of unpacking these scene releases. Instead of focusing on RAR-files, the tool takes as input a directory, which is scanned for archives. A destination folder tells you where to to unpack.
Top directories are created as needed. Extra material, for example, NFOs are copied automatically.
You can use drag’n'drop to scan directories, and set destinations. Values
are remembered between runs. Several archives can be unpacked in parallel.
Download
Download the required files. You need to have .NET 2.0 installed. You can download the runtime from Microsoft.
Installation
Copy the files to any destination. Create your own shortcuts as needed.
Tip: If you create a shortcut in %USERPROFILE%\SendTo you can use the context
menu, on folders, to open the application and scan the selected folder.
Be aware. This tools is released as free software. I take no responsibilities
for any lost of data, etc.
TODO:
Screenshots
Fell free to download.
I think there is a lot of confusion regarding where files, in a windows environment, should end up. A home directory, for each user, first appeared wind the NT-system. The location for this directory is %USERPROFILE%. The idea is to but all user related files inside of this area, in one of its subdirectories.
%APPDATA%)The user can decide to retarget a lot of these directories into other directories. This is good when roaming profiles are in use. Say that you have a lot of files inside your document folder (which you of course have ). Then, to ease the saving of the profile, you can retarget this folder to a common net folder. When you now logout, the My Document folder is not uploaded to your server, making the logout process quicker.
But, a lot of software, there among games, have an annoying idea of putting saved progress in the My Document folder. And in case when this folder is retargeted, one can notice delays when progress is saved by the games, due to the worse performance of networked folders.
Software must use the %USERPROFILE% folders wisely. My Documents are for the user’s own creations, and %APPDATA% for application’s creations. Progress of a game is nothing a user is supposed to edit, or open, himself. Only the application is supposed to touch these files. These kind of files should therefore be put in %APPDATA%.
Also, software, makes bad decisions weather to use %APPDATA% or Local Settings:
%APPDATA% should only be used for settings which can be shared (without a huge amount of extra storage involved) from several machines, in a roaming environment. Caches should never go into %APPDATA%.Local Settings.As you see, %APPDATA% is the place to put application settings, which in the end will/should replace the registry, as described by Application Configuration and the Registry.
Microsoft is making bad judgments as well. For example, Outlook is using Local Settings for its *.pst files, giving the user problem to find his mail, when logging in from another machine. Well, one can say that Microsoft knows the *.pst files can grow big and therefore uses the Local Settings folder… and by the way Microsoft don’t actually support roaming *.pst files. They want us to use Exchange for this matter
Two small blogs regarding the differences can be found here
