This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Error accessing mapped drive >2TB?

Andrey Repin <anrdaemon <at>> writes:

> Greetings, Brian Inglis!
> > $ ls $(cygpath '\\\tools\') # works - list contents
> > About_This_Site.txt  ctrl2cap.amd.sys*  Eula.txt
> > ...
> > $ ls `cygpath '\\\tools\'`  # fails - should be same as
> > above 2
> > ls: cannot access /cygdrive/c/ No such file or
> > directory
> Not necessarily. This is why using the backticks is discouraged.
> They have weird escaping rules and generally non-obvious.
> Stick to $( ... ).

Never noticed any issues previous to this but generally don't use
backslashes except as escape character, and MS utilities which require
legacy path separators (even under DOS, many non-MS utilities would accept
normal path separators, as the underlying APIs didn't care, and neither do
most of the Windows APIs). 

> > Windows Explorer drive mappings are not visible from cmd or mintty/bash
> > windows, but "net use x: \\\tools" mappings are visible
> > from separate cmd and mintty/bash windows as drive X: or /cygdrive/x, but
> > x:\ is not accessible from Windows Explorer. 
> Are you sure you're looking from the same user session?

Same user session, different (elevated) cmd and mintty/bash console sessions. 

> If you start mintty/cmd elevated, you won't see drives mapped in Explorer
> (non-elevated).

Kind of figures on Windows - I would expect elevated sessions to be able to
see mappings on non-elevated sessions. 

> For me, everything works as expected. Drives mapped in batch file on system
> start visible in Explorer without an issue.

Found that when I started using W7 console sessions, net utilities, both MS
and Cygwin nslookup, ping, tracert, etc. could not see the network unless
they were run in elevated sessions, so set up all console sessions to start
elevated. Was that something that happened on early releases and was fixed
later, or some incorrect assumption or setting on my part years ago? 

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]