X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<20100127042943.T419P.253110.root@cdptpa-web19-z01>
Date:	Tue, 26 Jan 2010 23:29:43 -0500
From:	<jenniferlee AT nc DOT rr DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows server 2008
Cc:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
In-Reply-To:	<20100125112209.GL2402@calimero.vinschen.de>
MIME-Version:	1.0
Sensitivity:	Normal
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Wow, thank you so much, that was very fast!  

Is there a way I can refer my customers to this patch? Or should I put the workarounds in my code for now until this is in an official release?

I appreciate all the help with the workarounds, that got me going again, but at this point I either need to ship a patch on my end with the work around, or somehow get my end users to put the cygwin patch on, but I am not sure how to do that?

Thanks for all the help,

Jennifer


---- Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote: 
> On Jan 23 12:03, Corinna Vinschen wrote:
> > On Jan 22 19:52, Dave Korn wrote:
> > > On 22/01/2010 19:10, Cooper, Karl (US SSA) wrote:
> > > >> ---- jenniferlee@ wrote:
> > > 
> > > >>> Administrator AT nc042046 ~ $ cmd.exe /c 'mkdir C:\WINDOWS\temp' -bash:
> > > >>> /cygdrive/c/Windows/system32/cmd.exe: Bad address
> > > >>> 
> > > > I get the same result you do when I use "/c" (lower case c), but the
> > > > command is processed as expected when I use "/C" (upper case C).
> > > 
> > >   I get the same, and found a different workaround: it works by using "cmd"
> > > instead of "cmd.exe".
> > 
> > If nobody beats me to it, I'll look into that one next week.
> 
> Should be fixed in CVS now.
> 
> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
> 
> --
> 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
> 


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

- Raw text -