X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Chuck Subject: Re: Help. Cygwin corrupting files Date: Mon, 12 Feb 2007 11:10:38 -0500 Lines: 22 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Andrew DeFaria wrote: >> which makes me think that maybe its the writing to stdout that's failing. >> >> > At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm Haven't tried spinrite yet but I did do a "thorough" check of the drive using Tuneup Utilities. That's the one that requires exclusive access to the disk, reboots, and runs as the o/s starts to come up. It identifies and fixes bad sectors. It found nothing wrong with the HD. As stated before, I really do *not* believe this is a HD getting ready to fail. If it were I would expect problems in Windows and Cygwin, not just Cygwin. I could be wrong but my suspicion is that Daemon tools' uninstaller left something behind. Something that hooks into the filesystem api. I remember when installing it that it had to reboot *before* installing itself and I think it was adding some sort of virtual device driver or a hook into the Windows filesystem API. After rebooting, it installed itself. I am highly suspicious that whatever it installed during that first reboot is still hanging around and causing problems for cygwin. -- 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/