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 From: "Dave Korn" To: Subject: RE: Inconsistent behavior for Win32 executable: starting from bash vs. starting from cmd.exe Date: Mon, 11 Jul 2005 16:39:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: ----Original Message---- >From: Igor Pechtchanski >Sent: 11 July 2005 16:26 > First thing I'd do is prepend 'c:\cygwin\bin' to the PATH in cmd.exe and > see if that reproduces the problem in cmd.exe. I couldn't reproduce this problem at all, using either g++ or msvc, running from either bash or cmd. I suspect there's an underlying problem with the network and the error code returned is misleading. > Would > > UNIVERSAL_NAME_INFO szBuff; > UNIVERSAL_NAME_INFO *puni = &szBuff; > > work better? I'm not familiar with UNIVERSAL_NAME_INFO, but the above > assumes it's no larger than 2k in size. No it doesn't. Check cbBuff. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/