X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <14472041.post@talk.nabble.com> Date: Sat, 22 Dec 2007 10:41:44 -0800 (PST) From: cwcarlson To: cygwin AT cygwin DOT com Subject: Re: child_copy: linked dll data write copy failed In-Reply-To: <000001c61beb$8b1806f0$025ca8c0@starwhite.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: cwcarlson AT cox DOT net References: <000501c61bce$e52bbe60$025ca8c0 AT starwhite DOT net> <000001c61beb$8b1806f0$025ca8c0 AT starwhite DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I'd like to know how you determined that a DLL was loaded with every process. I'm having the same problem, but I don't know how to debug it. I had some time to debug this, and found that it was the "Logitech Process Monitor" service, which I had recently installed (and forgotten about). It apparently causes a DLL to be loaded into every process, which was causing the problem. Once I set the service to Manual start, Cygwin-X started perfectly. I'm good to go for now, if someone has any insights to help figure out why this is happening, or wants to look into it further, I'm still interested. -- View this message in context: http://www.nabble.com/child_copy%3A-linked-dll-data-write-copy-failed-tp2438176p14472041.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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/