Obtaining a valid path to a special folder ("::{GUID}") ?

  • Thread starter Thread starter tias
  • Start date Start date
T

tias

Hi All !

I want to know if there is some way (or some 3:rd party application)
that allows me to assign a drive letter to a "special path" such as,
for example, an USB connected mobile phone, USB connected MP3 player
etc, (these "paths" usually shows up as "::{GUID}" when selected in
the SHBrowseForFolder dialog).
The problem I have is that these kind of devices shows up in Windows
Explorer as Explorer Name Space Extensions, meaning that they are
visible directly under the "My Computer" node.
I can drag and drop (and copy & paste) files to/from these devices,
but I can't for example, browse to them with a valid Windows Path,
meaning I cannot, for example, open/save files from any program that
is using the Standard Open (or Save) dialogs.

So is there any kind of method (or application) that allows me to
"mount" such a path ?

Or do I need to create my own Namespace Extension to handle this ?

TIA,
/Mathias
 
Hi All !

I want to know if there is some way (or some 3:rd party application)
that allows me to assign a drive letter to a "special path" such as,
for example, an USB connected mobile phone, USB connected MP3 player
etc, (these "paths" usually shows up as "::{GUID}" when selected in
the SHBrowseForFolder dialog).
The problem I have is that these kind of devices shows up in Windows
Explorer as Explorer Name Space Extensions, meaning that they are
visible directly under the "My Computer" node.
I can drag and drop (and copy & paste) files to/from these devices,
but I can't for example, browse to them with a valid Windows Path,
meaning I cannot, for example, open/save files from any program that
is using the Standard Open (or Save) dialogs.

So is there any kind of method (or application) that allows me to
"mount" such a path ?

Or do I need to create my own Namespace Extension to handle this ?

TIA,
/Mathias
Click to expand...

My MP3 players show up as ordinary flash disks (which is basically
what they are).

Run the command mountvol.exe from a Command Prompt to
see the devices you have and to assign a drive letter to them.
 
My MP3 players show up as ordinary flash disks (which is basically
what they are).
Click to expand...

Not the Philips GoGear and my Nokia phone, they just get a new node
under "My Computer" without any driveletter assigned.
Run the command mountvol.exe from a Command Prompt to
see the devices you have and to assign a drive letter to them.
Click to expand...

Good hint, but it doesn't work for me. For example, my USB connected
Nokia 6620 gets the following, "GUID" path (as I cen retreive using
the SHBrowseForFolder() API) :
::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

So I tried this :
MountVol W: \\?\Volume{20D04FE0-3AEA-1069-A2D8-08002B30309D}

And I got "The parameter is incorrect" (one of the most annoying
Windows error mesages BTW ;)

Any other ideas ?
/Mathias
 
Not the Philips GoGear and my Nokia phone, they just get a new node
under "My Computer" without any driveletter assigned.


Good hint, but it doesn't work for me. For example, my USB connected
Nokia 6620 gets the following, "GUID" path (as I cen retreive using
the SHBrowseForFolder() API) :
::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

So I tried this :
MountVol W: \\?\Volume{20D04FE0-3AEA-1069-A2D8-08002B30309D}

And I got "The parameter is incorrect" (one of the most annoying
Windows error mesages BTW ;)

Any other ideas ?
/Mathias
Click to expand...

In my expirence the volume name has to be literally the same
string as the one reported by mountvol.exe. So, instead of using
an API to retrieve the GUID, use mountvol without any parameters,
then use it to mount the volume. It would also be a good idea for
you to practise the mountvol command with an existing drive,
e.g. you CD drive. It would certainly eliminate the "annoyance
factor" you're complaining about.
 
Not the Philips GoGear and my Nokia phone, they just get a new node
under "My Computer" without any driveletter assigned.


Good hint, but it doesn't work for me. For example, my USB connected
Nokia 6620 gets the following, "GUID" path (as I cen retreive using
the SHBrowseForFolder() API) :
::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

So I tried this :
MountVol W: \\?\Volume{20D04FE0-3AEA-1069-A2D8-08002B30309D}

And I got "The parameter is incorrect" (one of the most annoying
Windows error mesages BTW ;)

Any other ideas ?
Click to expand...

Do you have in fact a drive named W: ? If so, note that MOUNTVOL
requires the path to an existing empty directory on an NTFS volume as
the first parameter. Try:

MD W:\Nokia
MountVol W:\Nokia \\?\Volume{20D04FE0- ...
 
(e-mail address removed) wrote in
MountVol W: \\?\Volume{20D04FE0-3AEA-1069-A2D8-08002B30309D}
Click to expand...
^^^^
Does not look like a volume GUID (which would be much like -11DB- these
days).
In fact, this GUID smells like the one for MyComputer.


Antoine
 
Back
Top