From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17985 invoked by alias); 7 Dec 2003 20:46:47 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 17978 invoked from network); 7 Dec 2003 20:46:46 -0000 Received: from unknown (HELO sys07.mail.msu.edu) (35.9.75.107) by sources.redhat.com with SMTP; 7 Dec 2003 20:46:46 -0000 Received: from [207.179.68.222] (helo=msu.edu) by sys07.mail.msu.edu with asmtp (Exim 4.10 #3) (TLSv1:RC4-MD5:128) id 1AT5ni-000GWg-00 for cygwin-xfree@cygwin.com; Sun, 07 Dec 2003 15:46:46 -0500 Message-ID: <3FD391B3.9040001@msu.edu> Date: Sun, 07 Dec 2003 20:46:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: Error: procedure entry point in cygwin1.dll References: <8009.1070620639@www48.gmx.net> <20031205145805.GI8193@redhat.com> <200312061102.52003.rasjidw@openminddev.net> <200312071033.25138.rasjidw@openminddev.net> <20031207005916.GA32485@redhat.com> In-Reply-To: <20031207005916.GA32485@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-12/txt/msg00138.txt.bz2 List-Id: Christopher Faylor wrote: > On Sat, Dec 06, 2003 at 07:24:29PM -0500, Jack Tanner wrote: > >>Rasjid Wilcox wrote: >> >>>C:\>dir /s > filelist.txt >>>C:\>start wordpad filelist.txt >>> >>>Do an edit/find for 'cygwin1.dll'. See if you have more than one. (In >>>case the Windows find file missed it for some reason.) >> >>Better: >> >>dir cygwin1.dll /s /a /b >> >>/a will catch cygwin1.dll even if it should be marked as a hidden or >>system file, and /b will optimize the output format (one line per file). > > > What's wrong with using the Windows Find/Search utility? It works fine in Windows 2000, but they broke it horribly in Windows XP when they "extended" it to ignore certain directories and types of files. You have to jump through all sorts of hoops and enable the indexing service in order to get it to search all files in XP. So, the results of the utility cannot be trusted in XP. Harold