Message-Id: <6.2.5.6.2.20120826013657.05a23d80@binnacle.cx>
Date: Sun, 26 Aug 2012 01:40:09 -0400
To: cygwin AT cygwin DOT com
From: starlight DOT 2012q3 AT binnacle DOT cx
Subject: Re: question: 'nxclient' won't connect with cygwin1.dll  1.7.16
In-Reply-To: <6.2.5.6.2.20120826010747.05a235d0@binnacle.cx>
References: <6 DOT 2 DOT 5 DOT 6 DOT 2 DOT 20120825232351 DOT 05a21ae8 AT flumedata DOT com> <6 DOT 2 DOT 5 DOT 6 DOT 2 DOT 20120826010747 DOT 05a235d0 AT binnacle DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Received-SPF: pass (mx.binnacle.cx: 172.29.87.10 is whitelisted by SPF-milter whitelist entry)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

The logs say that

   NXWin.exe

is failing on startup with an
exit code of 259

If anyone thinks then can make sense of
it, I could run 'procmon64' on NXWin and
trace the Windows systems calls in it.
Could run any applicable CYGWIN tools
as well.


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