From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29620 invoked by alias); 13 Jan 2009 22:43:46 -0000 Received: (qmail 29610 invoked by uid 22791); 13 Jan 2009 22:43:45 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Jan 2009 22:43:14 +0000 Received: by nf-out-0910.google.com with SMTP id b11so39416nfh.18 for ; Tue, 13 Jan 2009 14:43:11 -0800 (PST) Received: by 10.210.59.14 with SMTP id h14mr11843701eba.31.1231886591042; Tue, 13 Jan 2009 14:43:11 -0800 (PST) Received: by 10.210.81.20 with HTTP; Tue, 13 Jan 2009 14:43:10 -0800 (PST) Message-ID: <2ca21dcc0901131443t28a9b585udb7401911632d29d@mail.gmail.com> Date: Tue, 13 Jan 2009 22:47:00 -0000 From: "Dave Korn" To: cygwin@cygwin.com Subject: Re: rm seems to fail In-Reply-To: <496D0F63.8080401@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5520d94f0901130852l310a9dfdk9821c26458d8d5e@mail.gmail.com> <5520d94f0901130901y66a7df50yca7e586998a3bea3@mail.gmail.com> <5520d94f0901130916l7669d8capa39587365237da4f@mail.gmail.com> <5520d94f0901131057o3cbb3915h95b824942d95be6c@mail.gmail.com> <5520d94f0901131152u3a3f8ae3y64654d175b5b37a4@mail.gmail.com> <496D0F63.8080401@cygwin.com> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-01/txt/msg00398.txt.bz2 Larry Hall (Cygwin) wrote: > Mark J. Reed wrote: >> On Tue, Jan 13, 2009 at 2:52 PM, greenup wrote: >> So at this point I'm at a loss. I'm running the same version of >> Cygwin (though on Vista, not XP) on the same type of filesystem (NTFS) >> and not seeing the issue. Is there any way this could be >> BLODA-induced? > > Sounds like it. His cygcheck output names one possible source of conflict: > >> Potential app conflicts: >> >> Sonic Solutions burning software containing DLA component > That's an unusual one for BLODA. It generally causes no problems, but if you disable the startup component (as you might do when tuning your boot times, for example) then it starts to malfunction very oddly. I haven't seen it cause problems other times myself. cheers, DaveK -- 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/