Home / Test builds / v0.4 alpha 3
Name Modified Size InfoDownloads / Week
Parent folder
Win32 2016-07-20
Linux-i386 2016-07-20
Linux-x86_64 2016-07-20
ddrescueview-source-0.4~alpha3.tar.xz 2016-07-20 102.9 kB
ddrescueview-source-0.4~alpha3.zip 2016-07-20 161.8 kB
readme.txt 2016-07-20 3.2 kB
Totals: 6 Items   267.9 kB 0
These are the downloads for the 0.4 alpha 3 version of ddrescueview.

--> Please note: This version is not thoroughly tested and should not be relied upon in a production environment.
--> Use the bug tracker or email <mbit-kiel@users.sf.net> to report bugs and make suggestions.

The platform specific downloads include a binary and the source code.
Source-code only versions are availyble in .zip and .tar.xz format.

Please pick a download that suits your operating system and CPU architecture.

For Windows, there is a 32-bit build available, which runs on 32-bit and 64-bit versions of Windows.
This build should run on all desktop Windows versions from Win 98SE onward.

If you would like to run the program on GNU/Linux, there are 32-bit (i386) and 64-bit (x86_64) versions available.
They use GTK+ 2 and have been run successfully on the following distributions:
- Xubuntu 12.10 (32-bit)
- Xubuntu 14.04 (64-bit)

You should be able to compile ddrescueview for any other operating system and CPU architecture supported by Lazarus.
 
Q: How and where should I run ddrescueview?
A: Because ddrescueview only displays the mapfile produced by ddrescue, you can run it anywhere you 
   have access to that file, e.g. on the same machine as ddrescue. 
   You can also run it on another machine and monitor the progress from there. 
   Of course you need network file access to the mapfile, like SMB shares or NFS.
   Lastly, ddrescueview can also be used to view archived mapfiles.

Q: Why are the executables so big?
A: That's a well known and heavily discussed issue about applications using the LCL (Lazarus Component Library).
   Some library code that is not actually used (which the compiler can't prove) is included in the binary.
   Also, platform independence comes at a price. Lazarus applications do not use as many system 
   libraries as C/C++ applications do, but statically link lots of own library code.
   Currently, there is nothing I can do about the binary size.
   If you really need the space (e.g. on a Live CD), you can still compress the binary with UPX.


Changes in this version:

- Renamed 'logfile' to 'mapfile', to reflect the changes in ddrescue 1.20.
- Support for mapfiles from ddrescue 1.22 added. The current pass is displayed in the GUI.
- Improved speed of the mapfile parser for very large files.
- Added a bunch of command-line switches. ddrescueview now supports the following arguments:
    ddrescueview <options> -m domain-mapfile rescue-mapfile
    where rescue-mapfile must come last and <options> can be:
     -r (off|5s|10s|30s|1m|2m|5m)  Set refresh interval, e.g. -r 30s
     -lp                           Show log panel
     -gs (4|6|..|24)               Set grid size, e.g. -gs 10  
     -ub                           Use binary unit prefixes instead of decimal
     -x left                       X position of window on screen, in pixels
     -y top                        Y position of window on screen, in pixels
     -w width                      Client-width of window, in pixels
     -h height                     Client-height of window, in pixels
     -safe                         Turn off optimizations   
Source: readme.txt, updated 2016-07-20