Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: From: Tony Karakashian To: "'Steven Schram'" , cygwin AT sourceware DOT cygnus DOT com Subject: RE: why must cygwin be first in path? Date: Thu, 3 Feb 2000 13:23:18 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" This IS odd. I have seen some cases where the path, etc will become screwed up because things like %systemroot%\system32, etc aren't the first items in the path. What ends up happening is it can't find things like net.exe, , notepad...and then, even if you explicitely place the system32 directory in the path, it STILL can't find anything in there. Do you have that problem? How many items in YOUR path and the system path before the cygwin directory? What happens if you put it second or third? The items in your path prior to cygwin, are they stuffed full with files the system has to wade through before cygwin? If the directory paths are cached, that would explain the 10 second search the first time, then it shrinks to 3. -T > The only way I have found to get GNU Make to execute properly from the NT Command Shell is to put > the cygwin directory first in the PATH variable. Otherwise, 'make.exe' has that strange delay > (about 3 seconds) I mentioned a while back. Does this give anyone a clue as to why there is > a delay at all? -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com