This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: bash lockup
- From: "Sean McBride" <smcbride at jvbfinancial dot com>
- To: "Barry Buchbinder" <bbuchbinder at yahoo dot com>, <cygwin at cygwin dot com>
- Date: Mon, 3 Feb 2003 12:34:31 -0500
- Subject: RE: bash lockup
- Reply-to: <smcbride at jvbfinancial dot com>
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/