DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=i+UCpKFyNkCZ1yJj7LZfdJZoMqszs/92usWf+MxpnxsOxsJ1K1jU7
	GeBIoPPFSq7vIrFgLe4WxgfN8WY36pp8bRUQkEMlKi/LvkZe7P0evc8Z67lNSAgP
	xitcAf3uJMw9q6nOUY6kHpwAtNk/a4JhReHipdzvJVRIBdBemmAP44=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 24 Jan 2014 20:32:15 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows 7 64 Bit - Mounting Network Drives
Message-ID: <20140124193215.GR2357@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5d086b5de9f248deae22fa7a6f8d7cc2@BL2PR02MB449.namprd02.prod.outlook.com> <20140124134543.GP2357@calimero.vinschen.de> <a85cced36f59429ab961dec7c79b41a6@BL2PR02MB449.namprd02.prod.outlook.com> <365386.43165.bm@smtp118.sbc.mail.ne1.yahoo.com> <5c1e82c6ed724e689dec23f168bb4809@BL2PR02MB449.namprd02.prod.outlook.com> <20140124154913.GQ2357@calimero.vinschen.de> <d180897c0fa9413aaabdfc96d0fe2a1e@BL2PR02MB449.namprd02.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="pwWdILMQNxDD/Cps"
Content-Disposition: inline
In-Reply-To: <d180897c0fa9413aaabdfc96d0fe2a1e@BL2PR02MB449.namprd02.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--pwWdILMQNxDD/Cps
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jan 24 15:58, Damian Harty wrote:
> > Are you starting mintty as admin?  That might explain it.
>=20
> 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 as=
king, then I apologise.
>=20
> It seems if I start a cmd shell "standalone" and run c:\cygwin\bin\tcsh.e=
xe -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.
>=20
> At this point, I am fully baffled but at least I have a workaround - star=
t 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

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

--pwWdILMQNxDD/Cps
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJS4r+/AAoJEPU2Bp2uRE+gF9wQAIAoTZJHJbeqy+aqbv+rDJV3
hT1AKHam0nmBicA6PEmfqhy/xWR6S9N/hZC12cPeQFdVPIZE0vrfsD2Ihw0kRazW
mTJnWVaSI0P27WXMUVcWUwLA3fd6D/YrjnEZDnm/kPUuFTz48+YkMDxiZ5wWUsdp
X735L4R5L2uvdeOSVQkQYOY0joA6sXOcdZLc6MF7mx26IVXszSo1he5XlByBfp5D
VOkyhyGDSFYnElkmYaXUV7L3q8mB5ntaszSgqydqvx5jfIv1AuCc/AHhpP3AIYcT
Fg5aebEWhgMFaEfGAE0Fz3nvho6EfLNiGjDyOuBhXHgZePPJWZyLm+vfjHf1CyfM
zHgt8O2izYo+xsfgEfjXev1egpbRHoEVm7mDh/p2RmJ96ZloMlNZVZa4Hjy8HzuA
cLZUZrKefLGeL+VkZHO0AMYoa9ulQW+5wDcIo/TnqSsZbd1QWpe7KQvL2FRS2/+u
dNxX4nKKEvY7pQrMp3IQ6HHgnm6A3gz1OgLkXVt6JyEvxGpmLYHr23fvsKJxaFcp
XJ/ACYLC07IT9RKVQBt4DI5NW9jLeCvIhLiFGN0fYCBVCNCyLaqQRbnxME3zz+7C
C6RLkHcslOQE7nEFYN0LoNEsWptQTZGAuiXxUYlZD3O7qH1ZDP14xQNxQ1fWttM1
usN33WE62mpFkrwTIF/w
=IkyV
-----END PGP SIGNATURE-----

--pwWdILMQNxDD/Cps--