Vista - dreaded spaces in shell special folders

I just found a little tutorial that shows how to open shell special folders from
a command prompt. As in C:\>start shell:Personal
to open the Documents folder. All well and good but naturally there's no example
to demonstrate doing the same with a shell folder that has spaces in the name.

Example: C:\>start shell:Quick Launch gets an error "cannot find shell:Quick"
I tried double quotes, single quotes in as many combinations I could could contrive
but no joy.

Anyone have the easter egg that works?

(btw I notice nobody is taking credit for the great innovation of spaces in file paths.)

edit: btw I have search indexing disabled to it's no good to use the search in the start button. I need to use a command prompt

MilesAhead wrote:Try: start "junk" "shell:my music"

List of valid shell folder names is in registry;
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

The "quick launch" is not among them, so it won't work anyway.

Regards,
--PA

C:>explorer "shell:quick launch" does the trick. I'd still like to get my hands on the guy
who gave the OK to spaces in file paths. It's the biggest PITA in Windows. Some
APIs you have to double quote if there's a space, some you don't. Reduces everything to trial and error when capitalization works just as well for setting off words in the filename. Those spaces are driving me mad!!!

And here:

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \
explorer \ FolderDescriptions

http://www.winhelponline.com/blog/sh...ecial-folders/
(with due credits to MS-MVP Keith Miller.)

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog http://www.winhelponline.com/blog


"Pavel A." <pavel_a@xxxxxx> wrote in message
news:u56sxZnJJHA.3976@xxxxxx

That's how I got into this thing with one of those blogs that demonstrates opening a special folder from the command line. Seems they all neglect to demonstrate the case with the space. Always in Windows now you have to do this when applicable or the info is nearly useless. The reader is left to waste several hours when the blogger
supposedly already knows the answer. Also not everyone puts up with Windows search. So only demonstrating from the search line is half baked. Running locate32
manually saves me from Windows Indexing running my HD endlessly.