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:reply-to:to:message-id:subject
	:mime-version:content-type:content-transfer-encoding:references;
	 q=dns; s=default; b=GFwBss4cd0cLeMtFxkgUiogobUyhRdOq5Si8oLmXZgx
	dIVJ4KeHug6qUplgZIbj+KZkPiaeKss5WhP3QpPjn23Ri8LxO20tnWH33enxXpNv
	eUxN8Hr2pKH5zDiXtmrgtK988KegIyE4BI8QfDASinO+IgqaD9Gg34gIcCQ/Ej6Y
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 22 Jun 2016 11:46:31 +0000 (UTC)
From:  <lloyd.wood@yahoo.co.uk>
Reply-To:  <lloyd.wood@yahoo.co.uk>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Message-ID: <707580695.12657516.1466595991066.JavaMail.yahoo@mail.yahoo.com>
Subject: Re: Piping on 64-bit Cygwin, STC found
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <707580695.12657516.1466595991066.JavaMail.yahoo.ref@mail.yahoo.com>

> I seem to have stumbled upon the actual STC. 

That is not the STC for SaVi and Geomview under 64-bit Cygwin.

The problem for SaVi and Geomview is in INITIALISING any
piping, as previously described. They simply cannot communicate
at all under 64-bit Cygwin, while they can under 32-bit Cygwin.

You appear to have demonstrated that Cygwin piping fails
when used heavily. Unfortunately, that is not news, and
has always been so...

Lloyd Wood
http://savi.sf.net/

--
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