DDRescue-GUI 1.7.1 is out! See the important fix and download.

Hi,

Just a quickie post to let you know about the new DDRescue-GUI.

If this is a minor update to DDRescue-GUI, why download it?

My minor updates are usually still fairly major :P. Also, this new release fixes a bug with v1.7 that, while otherwise low-importance, would eventually cause the GUI log file to become very large and would eventually become a problem when doing an extended recovery.

To download it, see the launchpad page or my website.

That’s all for now, but I have more stuff coming up very soon.

Hamish

Programming / , , , ,

About Hamish McIntyre-Bhatty

Iā€™m a programmer, I write in Python, am learning C++, and I will be learning Java soon as well. I have written and maintain 3 open-source programs, hosted on launchpad.net. In my free time I also enjoy cycling, acting, photography, and play bass guitar. I go climbing every now and then as well. As you may have guessed, blogging is also a hobby of mine :)

2 thoughts on “DDRescue-GUI 1.7.1 is out! See the important fix and download.

  1. Curtis on said:

    Hello, I use DDRescue-GUI, and it’s a wonderful program! From what I can tell, the smallest it can read/rescue is 32 kilobytes at a time. I was just wondering, if in a future update, the read/rescue size can be made as small as 16, 8, 4, 2, or even 1 kilobyte.

    • Hamish McIntyre-Bhatty on said:

      Hi,

      Sorry for the confusion, but I believe what you’re looking at is the number of clusters to copy at a time. This size might be smaller or larger than 32 KB, because it varies based on the filesystem and disk size šŸ™‚

      In theory I could give the user more of a selection here, but it’s very likely to make the recovery go a lot slower for not much benefit, as a cluster is supposed to be a chunk of data at a size that makes it easy to read quickly, essentially. This is because reading very small amounts of data on modern drives can be very slow, as they can be incapable of reading less than 4KB of data at a time, and for example just have to read 4KB and throw 3KB away when reading 1 KB of data.

      Hope this helps,
      Hamish

Leave a Reply

*