Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 9 Feb 2004 23:47:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "entry point __getreent" not found errors with sshd and inetd Message-ID: <20040210044709.GA5893@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040209222037 DOT 020d7a88 AT ensim DOT dregg DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.0.20040209222037.020d7a88@ensim.dregg.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Mon, Feb 09, 2004 at 10:35:39PM -0600, Christopher G. Morlier wrote: >I have been attempting to setup sshd and inetd, and have consistently >received entry point not found errors when both try to execute >(specifically: "The procedure entry point __getreent could not be located >in the dynamic link library cygwin1.dll"). > >I have googled this problem and seen recommendations to ensure I have the >latest package versions, to reboot, and to ensure that I do not have >multiple copies of cygwin1.dll. I have done all of these and continue to >get the error. I am running Windows XP Home. > >Is there anything else I should try? What are the possible causes of this >problem? There is only one reason for this: You have an older version of the DLL on your system. If you have googled, you should have seen that every single time someone says "I don't have an older version" it eventually turns out that they do. The suggested way of finding the errant DLL is to do something like: c: cd \ dir /s cygwin1.dll/s and delete the older dll. It's probably in your windows system or system32 directory. And, before you argue that you already tried all that and that there must be some other reason, let me say it again: There is no other reason. As Larry says in another post, the other thing you can do is *attach* cygcheck output to a message here if you are still having problems. That may help us find your other DLL. cgf -- 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/