Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



As we have added a number of new options to Blade v1.9, we have created a new Options windows.  This can be found by selecting Tools » Options from the main menu. 

Moving the options to this location makes it easier to configure the software, and assists in removing additional clutter from the main user interface.

The following options have been removed from the main user interface window and moved to the Options window:

  • Block Size (Sectors) - This is the size of the block Blade will read in with each cycle as it searches for data; the default is 512 Sectors (262,144 bytes).
  • Files per Folder - This is the number of files Blade will write out to any single folder during the recovery process.
  • Log Type - This changes the type of log written during the recovery process.  You may be asked to set the log type to 'debug' by our support engineers when trying to resolve a recovery issue, as it will contain further information.

 A new option added to Blade is to set the Code Page.  This is used when converting byte streams into ANSI characters.


Added handling of OMA DRM Content Format for Discrete Media Profile (DCF) to ISO Base Media Format Validation (Intelli-



DRM content format (DCF) is used to package and protect discrete media, such as ring tones, applications, and images.  The content in DRM content format is encrypted using a symmetric encryption key.  The content is then placed as a single content object in the DCF internal structure and layout.  The MIME type for objects conforming to the DRM content format is application/vnd.oma.drm.content.


Blade now supports the recovery of OMA DRM Content Format for Discrete Media Profile (DCF) for ISO Base Media Format files.  We have also enhanced the Intell-Carve™ Carve® profile to make it more robust when handling potentially damaged and corrupt video files.


With the addition of the length multiplier option in the recovery profile, we have added a recovery profile which utilises this feature.  The main database file consists of one or more pages. The size of a page is a power of two between 512 and 65536 inclusive. All pages within the same database are the same size. The page size for a database file is determined by the 2-byte integer located in the header of the file.  Also located in the header is a 4-byte integer recording the size of the database file in pages.  The multiplier feature can read this value and work out the correct size of the database.

UInt8 Length Option

We have also added an option for identifying 1-byte length markers.


We have renamed the VALIDATION_ERROR log to DATA_VALIDATION_LOG for clarification purposes as some users were confusing the purpose of the log.  The log is used by Intelli-Carve™ Carve® profiles to record instances were identified data has failed recovery validation.  Validation may fail for a number of reasons, such as non-contiguous clusters, or overwritten/corrupted data.  The log identifies any instances where a file or record header has been found and the recovery process has been halted because the data failed the Intelli-Carve™ Carve® validation.  This is not an error log, but an audit of data validation.