[face=courier]Since cm_OpenDrives started to show fixed disks free/occupied size in a file panel I use it more often. But the problem is in a way Commander passes paths from that "folder". I don't know why it uses UNC format for that, but this is very inconvenient. For example I want to open permission dialog for some NTFS partition from "My Computer" folder (opened by cm_OpenDrives) via build in cm_EditPermissionInfo command. But I got an error as result - the command expect local, not UNC path as argument. The same situation with my AV software - generated by "%L" list from "My Computer" is not acceptable for it, 'cause it includes paths in UNC format.
Christian, is it possible to change this painful situation somehow?[/face]
UNC paths in My Computer - what for?
Moderators: Hacker, petermad, Stefan2, white
As far as I understand it, UNC paths is supposed to be the standard way by which drives (local and networked) are accessed with drive-mapping being a legacy from Novell. Recently, I unmapped all of my network drives and access everything via UNC which, to me at least, makes a lot more sense and is easier to remember and maintain across multiple computers.
As for programs I use, if they do not properly support UNC paths, I hound the author of the program to support them as they are supposed to be the standard. I highly recommend you do the same.
My soapbox aside, I don't see why it wouldn't be possible to have a path returned from TC commands be a drive-letter path rather than UNC as long as UNC remains an option as well.
As for programs I use, if they do not properly support UNC paths, I hound the author of the program to support them as they are supposed to be the standard. I highly recommend you do the same.
My soapbox aside, I don't see why it wouldn't be possible to have a path returned from TC commands be a drive-letter path rather than UNC as long as UNC remains an option as well.
[face=courier]On 13-01-2004 19:15:55 +0000 Randy wrote:
R> I unmapped all of my network drives and access everything
R> via UNC
And your local drives too? :)
R> As for programs I use, if they do not properly support UNC
R> paths, I hound the author of the program to support them
R> as they are supposed to be the standard. I highly recommend
R> you do the same.
Well, this is exactly what I'm doing - I ask Christian to make his own program's internal commands work with Commander generated filelist :).
R> I don't see why it wouldn't be possible to have a path
R> returned from TC commands be a drive-letter path rather
R> than UNC as long as UNC remains an option as well.
Golden words.[/face]
R> I unmapped all of my network drives and access everything
R> via UNC
And your local drives too? :)
R> As for programs I use, if they do not properly support UNC
R> paths, I hound the author of the program to support them
R> as they are supposed to be the standard. I highly recommend
R> you do the same.
Well, this is exactly what I'm doing - I ask Christian to make his own program's internal commands work with Commander generated filelist :).
R> I don't see why it wouldn't be possible to have a path
R> returned from TC commands be a drive-letter path rather
R> than UNC as long as UNC remains an option as well.
Golden words.[/face]
[face=courier]The Protoss do NOT run from their enemies.
It is here, that we shall make our stand.[/face]
It is here, that we shall make our stand.[/face]
Black Dog wrote:[face=courier]On 13-01-2004 19:15:55 +0000 Randy wrote:
R> I unmapped all of my network drives and access everything
R> via UNC
And your local drives too?
As far as I know, you're supposed to be able to access them via \\[localhost_name]\c$ ... d$ ... etc although I don't think Windows follows that paradigm. I could be wrong, however.
[face=courier]On 14-01-2004 00:45:32 +0000 Randy wrote:
R> As far as I know, you're supposed to be able to access them
R> via \\[localhost_name]\c$ ... d$ ... etc
Well, of course via UNC I can access any local drive with any share name I create but as you can see in "My Computer" Commander generate not even Admin share names but some strange fakes - there is no such share on my computer - "\\HOST\C:\" :).[/face]
R> As far as I know, you're supposed to be able to access them
R> via \\[localhost_name]\c$ ... d$ ... etc
Well, of course via UNC I can access any local drive with any share name I create but as you can see in "My Computer" Commander generate not even Admin share names but some strange fakes - there is no such share on my computer - "\\HOST\C:\" :).[/face]
[face=courier]The Protoss do NOT run from their enemies.
It is here, that we shall make our stand.[/face]
It is here, that we shall make our stand.[/face]