X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_93 X-Spam-Check-By: sourceware.org Date: Mon, 17 Aug 2009 17:53:54 +0100 From: Robin Walker Reply-To: Robin Walker To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: run-1.1.11-1 Message-ID: <4385EB0C1AF79960A02CC313@qjunbur.quns.cam.ac.uk> In-Reply-To: <20090817135758.GZ32408@calimero.vinschen.de> References: <200908161558.n7GFwZ16011900@StraightRunning.com> <4A883A1D.10109@cwilson.fastmail.fm> <20090817084750.GP32408@calimero.vinschen.de> <4A894A82.2010109@cornell.edu> <20090817135758.GZ32408@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com --On 17 August 2009 15:57 +0200 Corinna Vinschen wrote: > The [...] as well as your startxwin.bat script don't work on W7. On any NT-class Windows, calling a *.bat file causes a 16-bit sub-system to be spawned, and the .bat file is interpreted within the 16-bit command interpreter. Given that Cygwin 1.7 no longer supports Windows 9x systems, it would probably make sense to convert as many .bat files as possible to .cmd files, so that they run within the normal 32-bit command interpreter. Does the startxwin.bat script work when it is renamed startxwin.cmd ? -- Robin Walker -- 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