Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 24 Mar 2003 20:35:14 -0500 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: cygcheck calling id.exe with nontsec Message-ID: <20030325013514.GA34027175@hpn5170x> Mail-Followup-To: "Pierre A. Humblet" , cygwin AT cygwin DOT com References: <3 DOT 0 DOT 5 DOT 32 DOT 20030324193705 DOT 007f0100 AT mail DOT attbi DOT com> <20030325012220 DOT GA12098 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030325012220.GA12098@redhat.com> User-Agent: Mutt/1.4i On Mon, Mar 24, 2003 at 08:22:20PM -0500, Christopher Faylor wrote: > On Mon, Mar 24, 2003 at 07:37:05PM -0500, Pierre A. Humblet wrote: > >cygcheck calling id.exe with CYGWIN=nontsec has a problem... > > At the risk of sounding ungrateful, can I point you at > http://cygwin.com/bugs.html? > > The fact that you are reporting a problem in cygcheck doesn't mean that > the hints there are not still useful. It would hvae saved me some time > trying to puzzle out what you'd discovered if you'd 1) described it > and 2) included cygcheck output. I suspect that you may even have > figured out why the problem was happening. Chris, If I had figured it out I would have told you. Normally I would even have tried to patch it but I have never been able to make cygcheck on WinME, due to include file problems that I never felt the need to try to solve. Thanks for the fix. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/