X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Chuck <skilover AT bluebottle DOT com>
Subject:  Re: Help. Cygwin corrupting files
Date:  Mon, 12 Feb 2007 11:10:38 -0500
Lines: 22
Message-ID: <eqq3hu$tv8$1@sea.gmane.org>
References:  <eqik0d$df7$1 AT sea DOT gmane DOT org> <eqis71$9ej$1 AT sea DOT gmane DOT org> <eqpts6$49d$1 AT sea DOT gmane DOT org> <eqq0bl$dq7$1 AT sea DOT gmane DOT org>
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: <eqq0bl$dq7$1@sea.gmane.org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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/