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 From: "Dave Korn" To: Subject: RE: A vexing installation problem Date: Tue, 30 Nov 2004 13:38:39 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20041130011421.GA20359@sonic.net> Message-ID: X-OriginalArrivalTime: 30 Nov 2004 13:38:39.0656 (UTC) FILETIME=[E6833280:01C4D6E1] > -----Original Message----- > From: cygwin-owner On Behalf Of David Hinds > Sent: 30 November 2004 01:14 > On Mon, Nov 29, 2004 at 06:22:35PM -0500, Larry Hall wrote: > > > > Yeah, I understand. This is certainly not your everyday > issue, as you've > > noticed. I suppose it's worthwhile to look at the settings > for the Windows > > firewall to see if it's being overly restrictive or > limiting in some way. > > Sorry, I don't have any other ideas other than getting down > into it with > > more details... > > Ok, this is really odd... > > I just noticed that every now and then, when I run a cygwin program > with the new DLL, it actually does work. Maybe 10% of the time when I > invoke a shell, I actually get a working shell, which then appears to > be fully functional: all its children behave normally. Also, once I > have a working shell running, I can also open new shells from the > desktop and they work 100% of the time. I reckon you most likely have faulty hardware in there somewhere. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/