X-Spam-Check-By: sourceware.org Message-ID: <4611A225.8030503@benwylie.co.uk> Date: Tue, 03 Apr 2007 01:39:01 +0100 From: Ben Wylie User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: Cygwin Mailinglist Subject: Error with changing directory - No such file or directory References: <297343D29C14AA4D822142893ABEAEF302F44746 AT srv1163ex1 DOT flightsafety DOT com> In-Reply-To: <297343D29C14AA4D822142893ABEAEF302F44746@srv1163ex1.flightsafety.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ArGoMail-Authenticated: benout AT benwylie DOT co DOT uk Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Thrall, Bryan wrote: > Matthew Woehlke wrote on Monday, April 02, 2007 5:59 PM: >> Ben Wylie wrote: >>> [snip] >>> When I run the batch file I get: >>> >>> F:\>cd F:\cygwin\bin >>> >>> F:\cygwin\bin>bash --login -i deletescript.sh >>> F:/Progra~1/NAVIEG/queues/ >>>> No such file or directoryine 2: cd: F:/Progra~1/NAVIEG/queues/ >>> >>> [snip] >> Hmm, it seems you are not using the version of Cygwin that smacks you >> over the head with a wet tuna for doing such a thing (is that a >> feature in the Vista-only 1.7.0?). Try using POSIX paths instead of >> DOS-style paths, and see if that fixes it. > > Yes, plus d2u will probably also help. It doesn't seem to mind the DOS style paths as they are converted by cygwin, however the d2u resolved my problem. I notice when I reinstalled cygwin, I chose the Unix/binary default text file type which I believe is at the root of this problem. I have now reinstalled again with the DOS/text line endings option and it is happy again without having to convert all of the line endings to Unix style. Thanks for your help and sorry about the double post. Ben -- 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/