X-Spam-Check-By: sourceware.org Date: Mon, 30 Apr 2007 13:41:50 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: "Michael D. Adams" cc: cygwin AT cygwin DOT com Subject: Re: Setup.exe Problems on Vista In-Reply-To: Message-ID: References: <462B002F DOT A1E27066 AT dessent DOT net> <462C0C88 DOT F09E959B AT dessent DOT net> <006801c785fe$e9e058d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <462D4611 DOT 6090407 AT cygwin DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: Content-Disposition: INLINE Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sun, 29 Apr 2007, Michael D. Adams wrote: > On 4/24/07, Larry Hall (Cygwin) wrote: > > Michael D. Adams wrote: > > > On 4/23/07, Dave Korn wrote: > > >> On 24 April 2007 00:19, Michael D. Adams wrote: > > > >> What's going on here could be related to security changes in the > > >> way Vista handles dll and executable search paths, perhaps, but > > >> that's fairly speculative. > > >> > > >> Which reminds me. Isn't it about time this conversation had some > > >> input from cygcheck on the various systems involved? > > > > > > Do you just want a 'cygcheck -c' or is there another option you'd > > > like the output from? > > > > 'cygcheck -srv', attached, not included, please. > > Sorry for the delay in responding. Here are the files with the > output. Let me know if there are any tweaks to how I run these that > you would like to see (e.g. running setup.exe with C:\cygwin\bin > already in the path, etc.). > > cygwin-510.txt: Fresh install with setup.exe version 2.510. > C:\cygwin\bin is *not* added to the path beforehand. Ran cygcheck from > the windows cmd.exe in the C:\cygwin\bin directory. Note that cygcheck > also emits to stderr "'id' program not found" twice. (Adding > C:\cygwin\bin to the path while running cygcheck doesn't fix that > message.) Michael, Can you also run one from a bash shell (invoking it explicitly as /bin/cygcheck)? Also, if you change the system PATH variable, you need to restart cmd.exe, otherwise the changes won't be picked up. If c:\cygwin\bin is in the PATH as cmd.exe sees it, cygcheck should be able to find 'id'. > cygwin-562.txt: Same as cygwin-510.txt except that setup.exe version > 2.562 was used. BTW, the version of setup doesn't seem to matter much. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- 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/