Re: use a drives guid instead of its letter - where is the drive root ?

Vanguard,

> Comes back to the UNC pointing to the shared resource on a host,
> like a folder, not to the drive itself.

Nope.

As mentioned, I can redirect output to "\\?\Volume{guid}\bla.txt"*. But I 
can't, using the same filespec, do a "del" on that file afterwards.

* and yes, the file is created in the root of the drive, as a "dir \bla.txt" 
shows.

So yes, an "\\?\Volume{guid}\" specifies the drive itself.

... but not always.  And *thats* the problem.

Any idea why and/or how to fix that ?

Regards,
Rudy Wieser