Bad Block Copy for Windows

Alter.Org.UA

<< Back

Home

www/www1/www2

Bad Block Copy for Windows

Copies file ignoring Bad Blocks. If target file doesn't exists, instead of unread blocks ZEROs are written. If target file exists, its blocks, coresponding to Bad Blocks in source are not touched. Thus, if you have some copies of the same file with Bad Blocks in different places, it is possible to completly restore the original file. To do this you should run bbcopy.exe with same target, but different sources.

Works under all Windows versions - Windows (95/98/Me/NT/2000/XP/etc.).

Usage:
  bbcopy.exe [-<switches>] <source file> <target file>
Switches:
  -b <blocksize>      sets physical block size for media. 2048 is default.
  -o[b|k|m] <offset>  offset in bytes (or optionally in blocks, KBytes or MBytes)
                      to start recovery from
  -c[b|k|m] <count>   number of bytes (or optionally in blocks, KBytes or MBytes)
                      to recover
  -r <retry>          number of retry attempts. 3 is default
  -l <logfile>        log unreliable and bad blocks to <logfile>
  -s                  fill unreadable parts with '** BAD BLOCK ***'
  -S <string>         fill unreadable parts with <string>
           "          Do not use fill patterns if you restore from multiple copies
  -?                  display this help
Note:
  1 KByte = 1024 bytes
  1 MByte = 1024 KBytes = 1024*1024 bytes
  byte offset or byte count is specified, it will be rounded to blocksize
Examples:
  bbcopy.exe -o 5000000 X:\Video.dat E:\Temp\Restored_Film.dat
    will copy data starting from byte offset 5000000 to end of file
  bbcopy.exe -om 1300 -cm 1000 X:\Video.dat E:\Temp\Restored_Film.dat
    will copy not more than 1000Mb of data starting from byte offset 1300Mb

The latest version with sources - bb_copy_v1g.rar/tgz (31.4 Kb/33.4 Kb)

History

Added -s and -S options, prompted by Jiri. These options specify fill pattern for unreadable blocks. I do not recommend using this option when target file already exists. This may happen when you restore data from multiple copies or make 2nd attempt to read damaged file, With this options previously read blocks may be overwritten if 2nd attempt fails.

I've found and fixed bug with recovering small files (those have size less than device block size).
bb_copy_v1g.rar/tgz (31.4 Kb/33.4 Kb)
2007.10.25

Fixed bug with crash on files of size between 2Gb and 4Gb.
Thanks to Jiri for bug-report.
bb_copy_v1f.rar/tgz (30.9 Kb/32.7 Kb)
2007.05.11

Fixed still some mistakes in text messages.
bb_copy_v1e.rar/tgz (30.6 Kb/32.4 Kb)
2004.11.03

Fixed minor bugs with text messages under Windows 95/98/Me.
bb_copy_v1d.rar/tgz (30.6 Kb/32.3 Kb)
2004.10.31

Due to customer's requests I have added Windows 95/98/Me support. Enjoy!
bb_copy_v1c.rar/tgz (29.7 Kb/31.4 Kb)
2004.10.26

bb_copy_v1b.rar/tgz (26.1 Kb/27.4 Kb)

Implemented options for setting recovery start position and amount of data to be recovered. For example if midle part of file cannot be read in 3 attempts, you can specify greater number specially for this part. These values can be specified in bytes, KBytes and MBytes.

Still one new feature - bad and unreliable block logging. You can leave utility alone and later view information about damaged parts of file.
2004.06.30

This version allows you to specify number of read retries for bad blocks. bb_copy_v1a.rar/tgz (24.6 Kb/25.8 Kb)
2004.03.03

Distribution (with sources): bb_copy_v1.rar/tgz (19.3 Kb/20.1 Kb)
2003.11.14

Please, send your comments and propositions here: alterX@alter.org.ua (remove X)