Re: #! not a recognized internal or external command

2003-10-03 Thread Neil Messmer
The problem ended up being the extention of my script file. It was *.cmd as it was under my Sun OS. This force the cmd.exe to execute it and never allow the cygwin environment to take hold. "Corinna Vinschen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Thu, Oct 02, 2003 at 03:3

Re: #! not a recognized internal or external command

2003-10-03 Thread Corinna Vinschen
On Fri, Oct 03, 2003 at 09:43:35AM +0100, Chris January wrote: > Did you check the line endings? Very good hint! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubsc

Re: #! not a recognized internal or external command

2003-10-03 Thread Corinna Vinschen
On Thu, Oct 02, 2003 at 03:30:28PM -0700, Neil Messmer wrote: > I should also mention that the script was executed within a cygwin shell > window when this error occurred. > "Neil Messmer" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > I would have thought the paths set in your p

RE: #! not a recognized internal or external command

2003-10-03 Thread Chris January
Did you check the line endings? > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Neil Messmer > Sent: 02 October 2003 23:30 > To: [EMAIL PROTECTED] > Subject: Re: #! not a recognized internal or external command > > > I s

Re: #! not a recognized internal or external command

2003-10-02 Thread Neil Messmer
I should also mention that the script was executed within a cygwin shell window when this error occurred. "Neil Messmer" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I would have thought the paths set in your particuliar environment would > have enabled to the find the correct shel

Re: #! not a recognized internal or external command

2003-10-02 Thread Neil Messmer
I would have thought the paths set in your particuliar environment would have enabled to the find the correct shell for proper execution. I am still convinced it is a setup issue as it works on another machine here. OS versions and hardware are identical. "Corinna Vinschen" <[EMAIL PROTECTED]> wr

Re: #! not a recognized internal or external command

2003-10-02 Thread Corinna Vinschen
On Thu, Oct 02, 2003 at 12:08:25PM -0700, Neil Messmer wrote: > I have just installed the latest version of cygwin and get the following > error message when running my scripts while running cygwin under Win XP. It > does not matter what shell I specify for the script. > > My paths on the win pc i

Re: #! not a recognized internal or external command

2003-10-02 Thread Neil Messmer
gt; wrote in message news:[EMAIL PROTECTED] > remove the space between #! and /bin/tcsh > > > -Original Message- > > From: Neil Messmer [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 02, 2003 8:08 PM > > To: [EMAIL PROTECTED] > > Subject: #! not

RE: #! not a recognized internal or external command

2003-10-02 Thread Vince Hoffman
remove the space between #! and /bin/tcsh > -Original Message- > From: Neil Messmer [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 02, 2003 8:08 PM > To: [EMAIL PROTECTED] > Subject: #! not a recognized internal or external command > > > I have just install

#! not a recognized internal or external command

2003-10-02 Thread Neil Messmer
I have just installed the latest version of cygwin and get the following error message when running my scripts while running cygwin under Win XP. It does not matter what shell I specify for the script. My paths on the win pc is set to /usr/local/bin; /usr/bin; /bin; /usr/x11r6/bin. The simple tes