X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CC073851C07 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1617927777; bh=RTRyZqBNdTp0RxjBUgnxnpI7rvrppMxgxnHftbG1bic=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=jjc1YoFSKzfkzXV/N5EW/k6WN94zY3ctCBCddUYL8Z18S+eurMH31l830Bf393dyp lb9/qwwFeXPxocvVJpJ7+iTfHkyCHxxHheuWFH+RQjj/roQ0ARz0tZw7OzWnZzhrBE Rf4Qqt4FphzsVf+n9h3ZnU/YXK5JBWqn5ELX07go= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5B6D93858004 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 1390MKtK031109 X-Nifty-SrcIP: [124.155.50.190] Date: Fri, 9 Apr 2021 09:22:25 +0900 To: cygwin AT cygwin DOT com Subject: Re: IBM MQ client application fails on latest cygwin Message-Id: <20210409092225.7117a11cb457dd94743b6965@nifty.ne.jp> In-Reply-To: References: <20210406233716 DOT 003ba116ca61f99632bb4dce AT nifty DOT ne DOT jp> <20210407195624 DOT d77b7459cbdd63504ea495d4 AT nifty DOT ne DOT jp> <20210407200441 DOT 860d8b421bf7d29d1e32a6ea AT nifty DOT ne DOT jp> <20210408201600 DOT 9f70ffa0b828a785e70a891c AT nifty DOT ne DOT jp> <20210408212559 DOT bfa088414864757d8c7dc19d AT nifty DOT ne DOT jp> <20210408230404 DOT 5083209095d8a184dd0b4de7 AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 1390N0mq009599 On Thu, 8 Apr 2021 18:30:25 +0200 Morten Kjærulff wrote: > Could it be a codepage issue? Maybe. What does chcp.com say in command prompt and in mintty? In cygwin 3.2.0, the codepage, when pseudo console is disabled, has been changed from the default codepage of the system to UTF-8 (65001). If pseudo console is disabled in your environment for some reason, this can affect. Please try to change the codepage using chcp.com to the default codepage of the system. The default codepage of the system is used also when the pseudo console is activated, so if possible, I recomend to enable it somehow. The reason why pseudo console is disabled, can be one of: - The system is older than Win10 1809. - disable_pcon is set in environment variable CYGWIN. - Terminal does not have enough capability to enable it. (e.g. TERM=dumb) - The "Legacy console" mode is enabled. https://docs.microsoft.com/en-us/windows/console/legacymode -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple