X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 13 Oct 2008 10:16:38 -0400 From: "Andrew Medico" To: cygwin AT cygwin DOT com Subject: Re: dd fails with iflag=direct In-Reply-To: <20081009124216.GY9289@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081009124216 DOT GY9289 AT calimero DOT vinschen DOT de> 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 On Thu, Oct 9, 2008 at 8:42 AM, Corinna Vinschen wrote: > I fixed that in CVS for Cygwin 1.7. Apparently when reading over the > end of a drive (but not a partition), Windows decides to return a weird > error code ERROR_CRC instead of just returning EOF. > > For Cygwin 1.5.25, the workaround is not using iflag=direct but standard > buffered reading. It's much faster most of the time anyway. Ok, thanks. I'll be on the lookout for 1.7. I'm mostly using this in situations where getting all possible data is more important than speed (a single bad sector in buffered mode usually causes a much larger region to be reported as unavailable), so unbuffered is preferrable. -- Andrew Medico -- 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/