X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.7 required=5.0 tests=BAYES_50,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <380-220091516162941142@M2W022.mail2web.com> Reply-To: royman17 AT verizon DOT net X-URL: http://mail2web.com/ From: "royman17 AT verizon DOT net" To: cygwin AT cygwin DOT com Subject: Uninstall/reinstall Date: Fri, 16 Jan 2009 11:29:41 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id n0GGUwC9004914 I encountered a problem with v1.5.25-15 on Windows XP. My application is C/C++ with an embedded Perl interpreter. The C/C++ code worked fine until I attempted to invoke the perl script. I got an invalid DLL error. I'm not really asking about this -- it's the steps I took to address the DLL problem where I must have overlooked something. Thinking their might have been an install error or a conflict between multiple perl interpreters, I decided to uninstall/reinstall cygwin. ActivePerl had been installed on the machine as well. I checked out the web pages for uninstalling cygwin and cleaning out the registry and carried out the steps. When I re-installed cygwin, two things went wrong. The first was that bash was not installed by setup.exe. I was able to remidy this problem simple enough by finding the tar.gz file containing bash and restoring it to the right location. The second problem was that cygwin1.dll was not installed. Nor could I find it in the distribution package. (I assume it is built on the fly somehow.) Ultimately, the sys admin re-loaded windows on my machine. (Not only does this solve a re-install problem, but it would clean out the registry and possibly remove any corrupt dlls, so overall it made sense.) I am about to re-install a version of cygwin on my computer, but I am concerned about encountering the original dll problem again -- meaning that I could have to uninstall/reinstall cygwin again -- maybe go to a different version of Perl or an earlier version of cygwin. What I want to know is, what did I do wrong in the uninstall? Or in the reinstall? Thanks, Roy -------------------------------------------------------------------- mail2web.com - Microsoft® Exchange solutions from a leading provider - http://link.mail2web.com/Business/Exchange -- 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/