public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows 7 64 Bit - Mounting Network Drives
Date: Fri, 24 Jan 2014 19:32:00 -0000	[thread overview]
Message-ID: <20140124193215.GR2357@calimero.vinschen.de> (raw)
In-Reply-To: <d180897c0fa9413aaabdfc96d0fe2a1e@BL2PR02MB449.namprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Jan 24 15:58, Damian Harty wrote:
> > Are you starting mintty as admin?  That might explain it.
> 
> I'm not observing a difference between running mintty as normal and right-clicking and doing "run as administrator". If that wasn't what you were asking, then I apologise.
> 
> It seems if I start a cmd shell "standalone" and run c:\cygwin\bin\tcsh.exe -l then it works. If I put "C:\Windows\System32\cmd.exe /K C:\cygwin\bin\tcsh.exe -l" into the properties box and start it, then it fails.
> 
> At this point, I am fully baffled but at least I have a workaround - start the shell from the windows command prompt.

But that should really not be necessary.  There's no reason that
starting from a Windows console shows the drives as OK but starting
mintty shows them as Unavailable.  The drives are user token bound, and
the user token in the mintty window is the same as the token in the a
console window.

Just for testing, did you try to access the drives from mintty?

I mean, assuming you start mintty, what happens if you do this (and only
this) after starting it:

  $ net use
  $ id
  $ ls /cygdrive/h
  $ net use


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-01-24 19:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  9:53 Damian Harty
2014-01-24 11:20 ` Andrey Repin
2014-01-24 11:31   ` Damian Harty
2014-01-24 12:35     ` Andrey Repin
2014-01-24 13:31       ` Damian Harty
2014-01-26  6:20         ` Andrey Repin
2014-01-24 16:28     ` Christopher Faylor
2014-01-24 16:29     ` Larry Hall (Cygwin)
2014-01-24 12:53   ` Frank Redeker
2014-01-26  6:35     ` Andrey Repin
2014-01-24 13:45 ` Corinna Vinschen
2014-01-24 14:00   ` Damian Harty
2014-01-24 14:51     ` Damian Harty
2014-01-24 14:52     ` tednolan
2014-01-24 15:10       ` Damian Harty
2014-01-24 15:49         ` Corinna Vinschen
2014-01-24 15:58           ` Damian Harty
2014-01-24 17:53             ` Alexander Kriegisch
2014-01-24 19:32             ` Corinna Vinschen [this message]
2014-01-24 16:42   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-01-24 17:30 Damian Harty
2014-01-24 19:14 ` Christopher Faylor
2014-01-24 19:32 ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140124193215.GR2357@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).