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 Message-ID: <4162B3E8.A3E4E9B@dessent.net> Date: Tue, 05 Oct 2004 07:47:04 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Weird bug with cp -f [solution that works for me] References: <000601c4a90d$0d18bad0$210110ac AT NEEEEEEE> <20041003040342 DOT GA25772 AT trixie DOT casa DOT cgf DOT cx> <20041003041441 DOT GB25772 AT trixie DOT casa DOT cgf DOT cx> <20041004231101 DOT E08D01B3F9 AT cgf DOT cx> <20041005000738 DOT GA6013 AT trixie DOT casa DOT cgf DOT cx> <4162A034 DOT 253DACBF AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Dave Miles wrote: > > Since re-starting the system and repeating the copy on drive O: (the > > newly created NTFS partition that 'cp' worked in) the "magically created > > directory" now appears when using 'cp'. > > So I tried to re-format it and was denied. On investigation > it turned out that Norton System Works had protection enabled > on this drive. I disabled it and 'cp' now works again. Also > if you check the exclusions on a drive that Norton is > protecting you'll see that '\temp' is excluded. > > So for me at least disabling Norton Protection on a folder > or drive that I intend to use Cygwin on is the way to go. Thanks for the resolution, for the archives' sake. The moral of the story is "Expect illogical issues to crop up if you run invasive programs that install low-level hooks all throughout various system APIs." Brian -- 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/