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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 9 Apr 2015 06:39:22 -0700 (MST)
From: tmacchant <tmacchant@yahoo.co.jp>
To: cygwin@cygwin.com
Message-ID: <1428586762844-117366.post@n5.nabble.com>
In-Reply-To: <55267798.4040004@dronecode.org.uk>
References: <1428279221468-117317.post@n5.nabble.com> <1428447703670-117329.post@n5.nabble.com> <5525619B.5060307@dronecode.org.uk> <1428538901493-117348.post@n5.nabble.com> <1428540058818-117349.post@n5.nabble.com> <55267798.4040004@dronecode.org.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