Launchy displays the name of the file (i.e. the name of the shortcut) itself, as stored in the file system.
Although Windows tries to hide that, the file name is "dfrgui.lnk" (hence "dfrgui" is added to the index; the full path is "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools\dfrgui.lnk").
You can see the real name of the shortcut if you open a Command Prompt, navigate to the directory mentioned above and issue the "dir" command.
However, the Start Menu and Windows Explorer do not display "dfrgui" but "Disk Defragmenter". The reason is that Vista is able to display localized names for all files and folders.
The folder also contains a hidden file "desktop.ini" with a section "[LocalizedFileNames]" and an entry "dfrgui.lnk=@%systemroot%\system32\dfrgui.exe,-103". Vista's Explorer then displays the localized string as defined by the resource instead of the mere file name.
When trying to launch the Disk Defragger on Windows Vista 64 bit SP1 using Launchy 2.1.2, a search of:
Disk Defragmenter
Draws a blank (which is the name of the shortcut).
However, I discovered that
dfrgui
Causes the defragger to launch (which is the name of the exe).
Why is this?
Launchy displays the name of the file (i.e. the name of the shortcut) itself, as stored in the file system.
Although Windows tries to hide that, the file name is "dfrgui.lnk" (hence "dfrgui" is added to the index; the full path is "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools\dfrgui.lnk").
You can see the real name of the shortcut if you open a Command Prompt, navigate to the directory mentioned above and issue the "dir" command.
However, the Start Menu and Windows Explorer do not display "dfrgui" but "Disk Defragmenter". The reason is that Vista is able to display localized names for all files and folders.
The folder also contains a hidden file "desktop.ini" with a section "[LocalizedFileNames]" and an entry "dfrgui.lnk=@%systemroot%\system32\dfrgui.exe,-103". Vista's Explorer then displays the localized string as defined by the resource instead of the mere file name.
At least for the 32 bit versions of Windows, you can use
http://cid-ba66807a9823f946.skydrive.live.com/self.aspx/Public/Launchy/LaunchyL10N.zip
to fix this issue.
Best regards,
Fabian.
That makes sense, thanks!
I don't suppose there are any plans to allow Launchy to search these localization names?
Thanks!
The download can now be found via
.
This folder contains the patched executable for the current version of Launchy () as well as versions to be used with older Launchy releases (e.g. ).
: http://cid-ba66807a9823f946.skydrive.live.com/browse.aspx/Public/Launchy/Launchy "Download patched Launchy"
: http://cid-ba66807a9823f946.skydrive.live.com/self.aspx/Public/Launchy/Launchy/LaunchyL10N.zip "http://cid-ba66807a9823f946.skydrive.live.com/self.aspx/Public/Launchy/Launchy/LaunchyL10N.zip"
: http://cid-ba66807a9823f946.skydrive.live.com/self.aspx/Public/Launchy/Launchy/LaunchyL10N_v212.zip "http://cid-ba66807a9823f946.skydrive.live.com/self.aspx/Public/Launchy/Launchy/LaunchyL10N.zip"