Reply to thread

Message

<blockquote data-quote="mnmr" data-source="post: 1064218" data-attributes="member: 86308">Nice. It doesn't mention the VC++ redistributables though.A solution can be dumb, even if the person who wrote it isn't. You can argue however much you like that it's &quot;clever&quot; or &quot;working as designed&quot;, but in my book it is incomprehensible that I am not allowed to choose a locally available drive. MP doesn't even need to know that it's a network share, which is the whole point of being able to map UNC paths to drive letters in the first place. Hence my point that locally available drive letters should be treated as local drives.Now, when I add a network resource, it ALSO does not allow me to use my existing drive letter. It uses some weirdo GUID+UNC-path syntax (that I presumed was Dokan's syntax, but even if it has nothing to do with Dokan, it is still not intuitive that I cannot use my existing shares).Don't take it personally, but I really do think the implementation in MP is incredibly dumb. Windows has a perfectly fine built-in mechanism of accessing network locations and MP decides to ignore this completely.There are probably a ton of good reasons for why MP does things differently, but I can think of no reasons why it should actively work to prevent me from using my existing shares (and yes, I know Windows by default limits access to network shares in various scenarios, but my system is not configured that way).</blockquote>

[QUOTE="mnmr, post: 1064218, member: 86308"] Nice. It doesn't mention the VC++ redistributables though. A solution can be dumb, even if the person who wrote it isn't. You can argue however much you like that it's "clever" or "working as designed", but in my book it is incomprehensible that I am not allowed to choose a locally available drive. MP doesn't even need to know that it's a network share, which is the whole point of being able to map UNC paths to drive letters in the first place. Hence my point that locally available drive letters should be treated as local drives. Now, when I add a network resource, it ALSO does not allow me to use my existing drive letter. It uses some weirdo GUID+UNC-path syntax (that I presumed was Dokan's syntax, but even if it has nothing to do with Dokan, it is still not intuitive that I cannot use my existing shares). Don't take it personally, but I really do think the implementation in MP is incredibly dumb. Windows has a perfectly fine built-in mechanism of accessing network locations and MP decides to ignore this completely. There are probably a ton of good reasons for why MP does things differently, but I can think of no reasons why it should actively work to prevent me from using my existing shares (and yes, I know Windows by default limits access to network shares in various scenarios, but my system is not configured that way). [/QUOTE]

Verification