Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: Determining the location of a Cygwin installation Date: Wed, 26 Mar 2003 12:23:31 -0800 Lines: 17 Message-ID: <3E820C43.8080400@Salira.com> References: <200303261832.53052.jld@ecoscentric.com> <3E81FE8B.9060008@Salira.com> <00ab01c2f3d4$e9b05920$cf6d86d9@ellixia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en, ru, zh Elfyn McBratney wrote: > But as cgf (the Really Cool Manager) said the registry keys are not to > be relied on as they might not be there forever. Yeah but what I'm saying is that there should be a commitment to at least one registry entry which denotes the [active] installation path of Cygwin. IOW I was sort of requesting it. Again, it's only my opinion. But to me it seems logical that you gotta know where to start... and the registry is there, partially for such a purpose.... > Thinking about this I'd use Win32 API calls (FindFirstFileEx and > CreateFile) to search a drive for items named "bin" and see if it's a) > a folder and b) contains cygwin1.dll . Sounds like a potentially expensive proposition. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/