From: Webbed.Pete@gmail.com
To: cygwin@cygwin.com
Subject: Re: How to bring ddrescue up to date?
Date: Mon, 14 Dec 2015 15:56:00 -0000 [thread overview]
Message-ID: <566EE6A8.7616.27DA9D14@Webbed.Pete.gmail.com> (raw)
In-Reply-To: <566E62F4.5050700@t-online.de>
Christian wrote:
>I will provide ddrescue 1.21 soon after its release.
Great! I worked out how to build a new version for myself (but not the test 1.21
versions... how do I make a .sig file?)
The new features make a HUGE difference. I can still see some room for improvement,
but not much.
It now correctly detects drives that require power cycle after hitting a bad spot (can set it
to go back and re-read a good spot after hitting an error. If it can't read the good spot it
will quit.)
And, within limits, you can now control how far it jumps when it finds a bad spot.
Thanks, Christian!
Pete
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-12-14 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 23:29 Webbed.Pete
2015-12-14 6:34 ` Christian Franke
2015-12-14 15:56 ` Webbed.Pete [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566EE6A8.7616.27DA9D14@Webbed.Pete.gmail.com \
--to=webbed.pete@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).