DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=uyCBNeVAr1NQg/Qm0mUIK6GWem9XL
	WmyX8sVc9fzbaer8hk0cIGipcKHQeM1atI+1WZZ2zHY7lofWsoBY91A0bj5FOdVg
	O7JxbgQKrx8V7Rb9BqkOHtauIK3yIJNopZl722W5spqEZivY843cCv5cYJ2+tuv9
	sGBd63cXcmsbgE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Charles Butterfield <charles.butterfield@nextcentury.com>
To: Dave Kilroy <kilroyd@googlemail.com>,
        "cygwin@cygwin.com"	<cygwin@cygwin.com>
CC: Charles Butterfield <charles.butterfield@nextcentury.com>
Subject: RE: chere + mintty doesn't work with mapped drives
Date: Mon, 2 Dec 2013 23:58:23 +0000
Message-ID: <cb96aa9da1e44e2b825f20614a91c484@CO2PR07MB556.namprd07.prod.outlook.com>
References: <00ce27600b2e404cbb8f9e56c3994e8c@CO2PR07MB556.namprd07.prod.outlook.com> <e438b5ebbe69401b843342394f5a5ea9@CO2PR07MB556.namprd07.prod.outlook.com> <5299A4BF.8070201@gmail.com> <e25e9576d2a2415ea90019117708d9d5@CO2PR07MB556.namprd07.prod.outlook.com> <529B529F.7080608@googlemail.com> <9ce71b17ad604e5c943e3c3731b145d1@CO2PR07MB556.namprd07.prod.outlook.com> <20131201210920.GA11800@calimero.vinschen.de> <529CDBE8.8000003@gmail.com>
In-Reply-To: <529CDBE8.8000003@gmail.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> -----Original Message-----
> From: Dave Kilroy [mailto:kilroyd@googlemail.com]
> On 01/12/2013 21:09, Corinna Vinschen wrote:
> > Are you starting mintty with "run as administrator" by any chance?
> Corrina's right - check that the same user is being used in both cases.
> I don't think this would explain why it's not working from the context menus
> though. Finding out why bash under mintty doesn't think /cygdrive/y/apps is
> a directory is the key.

SOLVED

Yes, I was starting mintty "as admin" and yes this was the culprit.
I was doing this by using a shortcut (similar, but not identical to the installed
"Cygwin Terminal" shortcut), that had the checkbox 
"Compatibility|Run this program as an administrator" enabled.

I ASSUMED this would only affect mintty when launched from this shortcut.

HOWEVER, it seems that this changes a property associated with mintty
regardless of how it is launched.  Apparently another "Wonder of Windows".

Unchecking the "run as admin" fixed the problem associated with accessing
the mapped drives everywhere (including the "Bash Prompt Here" xhere
Processing).

The reason I was running as admin was that many of the network centric
scripts that I use frequently during certain phases of various projects seem
to require admin privs and simply fail without any attempt to escalate (which
I seem to recall is due to a mismatch between the Windows and Unix
Security models).  I guess I'll have to rethink that approach.
 
Any suggestions on how to have a shortcut (or something similar) that
runs mintty as admin, but has no global effect on other mintty launches?