X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A8FA902.2090904@veritech.com> Date: Sat, 22 Aug 2009 04:14:58 -0400 From: "Lee D. Rothstein" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygstart not searching $PATH References: <2bf229d30908212025p49b563fft855f7df35b88f916 AT mail DOT gmail DOT com> In-Reply-To: <2bf229d30908212025p49b563fft855f7df35b88f916@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Chris Sutcliffe wrote: > At one point I seem to remember cygstart would search the $PATH > variable for an application? It absolutely did and was helpful with one or two problematic Windows apps. These problematic apps, that were helped by the non-standard use of 'cygstart', typically operate on a directory rather than file argument, and require startup in a directory different than the argument (to load one or more DLLs), if I remember correctly. I remember that finding that solution took a significant amount of trial and error. > This doesn't work > anymore, is this by design? As you say, it no longer works and I am am unable to start these problematic apps from a Windows command line, as a consequence. > Chris Lee -- 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