Hi,
What’s the best way to normalize the native path for shared drives?
For example,
on Windows 7, if the drive is mapped to z:, I get something like:
LanmanRedirector;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
on Windows 7, if the drive is NOT mapped, I get something like:
LanmanRedirector\some.share.drive.com\MY_SHARE\uploads.DS_Store
on Windows XP, I get something like:
;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
etc.
Is there a way to put it in some format so that I can compare the
paths easily? My application creates a prefix-trie and places the
paths in it so that it can do a look up on them later. The problem
though is that if they are not all formatted uniformly, then my
lookups fail 
Thanks,
J
This is really a question for NTFSD…
Where are you getting these names from? Filter Manager should be normalizing
them where you don’t see the, “;Z[blargh]” junk.
However, depending on what you’re trying to do, network names are have all
kinds of aliasing issues. For example, I can access the same share from:
\ServerName\Share
And:
\ServerIpAddress\Share
Would you want to treat these as different or the same? Also, DFS can
further complicate this.
-scott
“JonathonS” wrote in message news:xxxxx@ntdev…
Hi,
What’s the best way to normalize the native path for shared drives?
For example,
on Windows 7, if the drive is mapped to z:, I get something like:
LanmanRedirector;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
on Windows 7, if the drive is NOT mapped, I get something like:
LanmanRedirector\some.share.drive.com\MY_SHARE\uploads.DS_Store
on Windows XP, I get something like:
;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
etc.
Is there a way to put it in some format so that I can compare the
paths easily? My application creates a prefix-trie and places the
paths in it so that it can do a look up on them later. The problem
though is that if they are not all formatted uniformly, then my
lookups fail
Thanks,
J
Thanks Scott. Actually I moved my question over to NTFSD 
J
On Thu, Sep 20, 2012 at 11:23 AM, Scott Noone wrote:
> This is really a question for NTFSD…
>
> Where are you getting these names from? Filter Manager should be normalizing
> them where you don’t see the, “;Z[blargh]” junk.
>
> However, depending on what you’re trying to do, network names are have all
> kinds of aliasing issues. For example, I can access the same share from:
>
> \ServerName\Share
>
> And:
>
> \ServerIpAddress\Share
>
> Would you want to treat these as different or the same? Also, DFS can
> further complicate this.
>
> -scott
>
>
> “JonathonS” wrote in message news:xxxxx@ntdev…
>
>
> Hi,
>
> What’s the best way to normalize the native path for shared drives?
>
> For example,
>
> on Windows 7, if the drive is mapped to z:, I get something like:
> LanmanRedirector;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
>
> on Windows 7, if the drive is NOT mapped, I get something like:
> LanmanRedirector\some.share.drive.com\MY_SHARE\uploads.DS_Store
>
> on Windows XP, I get something like:
> ;Z:000000000000a165\some.share.drive.com\MY_SHARE\uploads.DS_Store
>
> etc.
>
> Is there a way to put it in some format so that I can compare the
> paths easily? My application creates a prefix-trie and places the
> paths in it so that it can do a look up on them later. The problem
> though is that if they are not all formatted uniformly, then my
> lookups fail
>
> Thanks,
> J
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer