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 Reply-To: From: "Sean McBride" To: "Barry Buchbinder" , Subject: RE: bash lockup Date: Mon, 3 Feb 2003 12:34:31 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20030203172148.61269.qmail@web40608.mail.yahoo.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Yes, this is true, however, I am not having the problem, anymore. I traced the crash to an old version of cvs I was using in windows. Apparently, it installed the cygwin1.dll(an older version, god knows what build) in its directory and added its dir to my path. Once I deleted that dll, I no longer recieve a crash. CYGWIN works great now! no problems that I can see now. I'm going to travel around with a CD and go nuts and install it on every machine I see. I'll be a walking file installation virus. Thanks! Sean -----Original Message----- >>Sent: Monday, February 03, 2003 12:22 PM >>Subject: Re: bash lockup >>I see this all the time, too (in Win98se). >>WINOLDAP seems to be how Windows handles the >>cygwin console. It also uses it for win95cmd. >>And it is there even when nothing is locked up. >>Windows doesn't seem to use WINOLDAP for a >>COMAND.COM DOS box. >>Don't think of it as a problem or bug (or even >>a "feature"); think of it as a behavior. >>It's not that hard to live with. -- 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/