Re: bash lockup

2003-02-03 Thread Barry Buchbinder
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.

- Barry

At 01:41 AM 2/1/2003, Sean McBride wrote:
I thank all of you who comented on my last post.

I have another small problem.

I installed the package with the installer and then
later, added pine to my
installation.  I don't think installing pine has
anything to do with my
problem, but I only noticed this after adding that
package.

occasionally when executing commands from bash the
command window locks up.
^c does nothing and I can't even close the window. 
Even Ctrl-Alt-Del End
task won't get rid of the misbehaving command window.
 Only if I shut down a
task called oldwinapp does the command window go
away.  Then I am able to
restart bash and rerun the same exact command I
attempted before with no
problem.  After a while, it locks up on another
command..  There seems to be
no pattern to the command or time it does this at.

Has anyone else experienced this problem?  Maybe I am
doing something wrong?

No and this doesn't look like a Cygwin issue per se. 
oldwinapp seems to 
be the problem here, whatever that is.  It certainly
doesn't come with the
Cygwin distribution.  I suggest you investigate this.

Larry Hall  [EMAIL PROTECTED]
RFK Partners, Inc. 
http://www.rfk.com
838 Washington Street   (508) 893-9779
- RFK Office
Holliston, MA 01746 (508) 893-9889
- FAX


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
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/




RE: bash lockup

2003-02-03 Thread Sean McBride

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/




Re: bash lockup

2003-02-01 Thread Larry Hall (RFK Partners, Inc)
At 01:41 AM 2/1/2003, Sean McBride wrote:
I thank all of you who comented on my last post.

I have another small problem.

I installed the package with the installer and then later, added pine to my
installation.  I don't think installing pine has anything to do with my
problem, but I only noticed this after adding that package.

occasionally when executing commands from bash the command window locks up.
^c does nothing and I can't even close the window.  Even Ctrl-Alt-Del End
task won't get rid of the misbehaving command window.  Only if I shut down a
task called oldwinapp does the command window go away.  Then I am able to
restart bash and rerun the same exact command I attempted before with no
problem.  After a while, it locks up on another command..  There seems to be
no pattern to the command or time it does this at.

Has anyone else experienced this problem?  Maybe I am doing something wrong?


No and this doesn't look like a Cygwin issue per se.  oldwinapp seems to 
be the problem here, whatever that is.  It certainly doesn't come with the
Cygwin distribution.  I suggest you investigate this.



Larry Hall  [EMAIL PROTECTED]
RFK Partners, Inc.  http://www.rfk.com
838 Washington Street   (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX


--
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/




bash lockup

2003-01-31 Thread Sean McBride
I thank all of you who comented on my last post.

I have another small problem.

I installed the package with the installer and then later, added pine to my
installation.  I don't think installing pine has anything to do with my
problem, but I only noticed this after adding that package.

occasionally when executing commands from bash the command window locks up.
^c does nothing and I can't even close the window.  Even Ctrl-Alt-Del End
task won't get rid of the misbehaving command window.  Only if I shut down a
task called oldwinapp does the command window go away.  Then I am able to
restart bash and rerun the same exact command I attempted before with no
problem.  After a while, it locks up on another command..  There seems to be
no pattern to the command or time it does this at.

Has anyone else experienced this problem?  Maybe I am doing something wrong?

Thanks for your patience.


--
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/