X-Recipient: archive-cygwin AT delorie DOT com 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:message-id:in-reply-to:references :subject:mime-version:content-type:content-transfer-encoding; q= dns; s=default; b=TyaeDYVC1BzW9vV23Q+wHd+E35hAsII69mZHHtnS/RpNIJ EuMAe7cdG940UsBnbJEVWQSpHOvH0kIDGqEPtTXpSgqdL9Ur+DfH6+PJLW3HludY TPw+FAGXXyju826hQCzO0NAQImQD7XPijeS2/8o5yztvwkPXuWjZWcRjcQCjM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:message-id:in-reply-to:references :subject:mime-version:content-type:content-transfer-encoding; s= default; bh=FxyqjEZe6dcyoo1v/Xt6kQC7zac=; b=JER984SKloUXWx5n1L4/ i7xXrxb0tjIkF0ffJwpY3cCskZO2XnNqMkZ8jVFTfZhymPX5/8zIuaH1xD1vsNGJ 6DBDAVBzssK5BU73nYJHC/+12Ei5wL33oQQzqh26fDYc4B5igwP1CBBa7w2zwIwL PqNVtAdn/vPy2Hoh8jgloII= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.5 required=5.0 tests=AWL,BAYES_60,FREEMAIL_FROM,SPF_SOFTFAIL,URI_HEX autolearn=no version=3.3.2 X-HELO: mwork.nabble.com Date: Thu, 9 Apr 2015 06:39:22 -0700 (MST) From: tmacchant To: cygwin AT cygwin DOT com Message-ID: <1428586762844-117366.post@n5.nabble.com> In-Reply-To: <55267798.4040004@dronecode.org.uk> References: <1428279221468-117317 DOT post AT n5 DOT nabble DOT com> <1428447703670-117329 DOT post AT n5 DOT nabble DOT com> <5525619B DOT 5060307 AT dronecode DOT org DOT uk> <1428538901493-117348 DOT post AT n5 DOT nabble DOT com> <1428540058818-117349 DOT post AT n5 DOT nabble DOT com> <55267798 DOT 4040004 AT dronecode DOT org DOT uk> Subject: Re: xterm fails after update cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Because 32-bit and 64-bit cygwin are completely independent, it's not possible for a a 32-bit cygwin X client to connect via a unix-domain socket to a 64-bit cygwin X server (and vice versa) Thank you for your conprephensive explanation. Now I made a windows (Dos) batch file to start both 32 and 64 bit X. Tatsuro -- View this message in context: http://cygwin.1069669.n5.nabble.com/xterm-fails-after-update-cygwin-tp117317p117366.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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