DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=HK3F99K1MViUG+zc
	dvF6XheFV0sOPiaFXZ+gzLuchHp5L5ObxgS0sohAl2J+sSdqq5gukCAaC4Uff2Br
	1FSLaefrhy9yszXvcgcxlU5ClKlqmjo2H8EPhkU+KXbOd+SoM5hoMGAl6kVeUaDn
	/N6amtjUig0ybzgVEOv9NKh+D5Q=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: cygwin@cygwin.com
Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates
To: cygwin@cygwin.com
References: <345b8a7a-bcbb-450b-08c0-943f3bb3b683@astrofoto.org> <20200303185335.5f4369c163b3a4b241ef429d@nifty.ne.jp> <f5b1rq9k4wr.fsf@ecclerig.inf.ed.ac.uk> <20200303213524.5ddf37854e2eb85eca50ed96@nifty.ne.jp> <f5bsgipipce.fsf@ecclerig.inf.ed.ac.uk> <20200303215912.6c72af3e17e8ef0f0f58b8a6@nifty.ne.jp> <f5b36apicb6.fsf@ecclerig.inf.ed.ac.uk> <f5by2shgkqv.fsf@ecclerig.inf.ed.ac.uk>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Message-ID: <5dd4f9c8-5e69-3355-6b80-6ab953475715@SystematicSw.ab.ca>
Date: Wed, 4 Mar 2020 09:57:07 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <f5by2shgkqv.fsf@ecclerig.inf.ed.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2020-03-03 15:02, Henry S. Thompson wrote:
> cygcheck output attached, just in case...
> 
> Per previous message, had to interrupt id, which was hanging, which
> produced
> 
>   garbled output from "id" command - no uid= found
> 
> while cygcheck carried on...
> and then hung with Process Explorer showing
> 
>   bash.exe
>      bash.exe
>         cygcheck.exe
>            cmd.exe
>              cygrunsrv.exe

As cygcheck is a Windows msvcrt.dll program, not a Cygwin cygwin1.dll program,
it uses Windows popen which runs commands under $COMSPEC rather than $SHELL, and
that can be affected by {HKLM,HKCU}/Software/Microsoft/Command Processor/
registry entries e.g.:

$ regtool list -v /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Command\
Processor/
DefaultColor (REG_DWORD) = 0x00000000 (0)
EnableExtensions (REG_DWORD) = 0x00000001 (1)
CompletionChar (REG_DWORD) = 0x00000040 (64)
PathCompletionChar (REG_DWORD) = 0x00000040 (64)
$ regtool list -v /proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Command\
Processor/
Autorun (REG_EXPAND_SZ) = "@chcp 65001 >nul"
CompletionChar (REG_DWORD) = 0x00000009 (9)
DefaultColor (REG_DWORD) = 0x00000000 (0)
EnableExtensions (REG_DWORD) = 0x00000001 (1)
PathCompletionChar (REG_DWORD) = 0x00000009 (9)

runs chcp 65001 at cmd startup, but could also do much more and different.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple