Message-ID: <21536420.post@talk.nabble.com>
Date: Sun, 18 Jan 2009 19:31:03 -0800 (PST)
From: LMHmedchem <lhall833@comcast.net>
To: cygwin@cygwin.com
Subject: Re: Question about windows shortchts to start a bash script
In-Reply-To: <4973EA07.2030909@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <21536086.post@talk.nabble.com> <4973EA07.2030909@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


I added "c:\cygwin\bin;" to the path and that seems to have corrected the
problem, thanks for the tip.

Two questions if you have a minute,

1. At first I tried adding cygwin to the end of the path, but that didn't
work. I checked my other machine and found cygwin immediately after
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;
I stuck cygwin in as the first entry after Wbem, and it worked after that. I
am surprised that it matters where it is in the list. Does it actually
matter or do you think I made an error in my first entry?

2. There was another variable on my other machine,
Variable name:
CYGWIN
Variable value:
ntsec tty

I did not set up that environment and I am wondering if that really needs to
be there.

Thanks again for your help.

LMHmedchem

-- 
View this message in context: http://www.nabble.com/Question-about-windows-shortcuts-to-start-a-bash-script-tp21536086p21536420.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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