Message-Id: <dbce23$4hksjl@dmzms99802.na.baesystems.com>
From: "Cooper, Karl (US SSA)" <karl.cooper@baesystems.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Fri, 22 Jan 2010 14:10:07 -0500
Subject: RE: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows   server  2008
In-Reply-To: <20100122185044.S088B.246358.root@cdptpa-web20-z01>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> Hi - I found that this error occurs on a 32 bit windows system, so
> its not 64 bit related as I initially thought. The problem is only
> occurring in Cygwin 1.7.1, not 1.5.24 so I will use the older version
> of cygwin until there is a fix for this.=20=20=20
>=20
> Thanks
>=20
> ---- jenniferlee@nc.rr.com wrote:
>> Hi - I am trying to run various windows commands from an ssh session
>> to my Windows 2008 64 bit server running Cygwin 1.7.1.=20
>>=20
>> Everything I run with 'cmd.exe' fails with "bad address" as shown
>> below, note that I can run the command natively without cmd.exe in
>> the=20
>> last example so in general things work, its just this cmd.exe that is
>> causing my program to fail;
>>=20
>> Administrator@nc042046 ~
>> $ cmd.exe /c 'mkdir C:\WINDOWS\temp'
>> -bash: /cygdrive/c/Windows/system32/cmd.exe: Bad address
>>=20
I get the same result you do when I use "/c" (lower case c), but the comman=
d is processed as expected when I use "/C" (upper case C).

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