IsoBuster 2.0

Smart Projects - (Shareware)

Data recovery from a damaged or poorly written optic supports is possible and easy to make with IsoBuster which also allow to browse the contents of an image file.

ISOBuster is an excellent tool developed to recover damaged or poorly written data stored on a CD, DVD, HD-DVD or BD, regardless of their format (Video, Audio, Image, Data). It is effective because it can recover files that can be read by Windows which makes it very convenient.

The application is also able to extract the contents of disk images to ISO, BIN, IMG, DAO, TAO, NRG formats, etc. Very easy to use, this program lists all the available items for all sessions on the media inserted in the drive, and user just have to select the documents to be retrieved.

One of the most interesting thing about IsoBuster is its ability to recognize the CD image files namely: DAO (Duplicator), TAO (Duplicator), ISO (Nero, Blindread, Creator), BIN (CDRWin), IMG (CloneCD), CCD (CloneCD) ,CIF (Creator), FCD (uncompressed), NRG (Nero), GCD (Prassi), P01 (Toast), C2D (WinOnCD), CUE (CDRWin), CDI (DiscJuggler) CD (CD- i OptImage), GI (PrimoDVD) PXI (PlexTools), MDS (Alcohol), MDF (Alcohol), VC4 (Virtual CD) B5T (BlindWrite) B5i (BlindWrite) DMG (Apple Macintosh) IBP (IsoBuster) or IBQ (IsoBuster).

Title:: IsoBuster 2.0
File Size:: 2.6 MB
Requirements:: Windows (All Versions)
Language:: en-us
License:: Shareware
Date Added:: 23 Dec 2006
Publisher:: Smart Projects
Homepage:: http://www.smart-projects.net
MD5 Checksum:: 9FD5653D8E3F5C2BDFB037615A827670

Changes:
- BD (Blu Ray) and HD DVD support.
- UDF 2.6.
- Implemented the ability to use other system installed code pages, such as MAC, SYMBOL, UTF8 etc., for ISO9660.
- Properties for drives show, next to CD and DVD, also BD and HD DVD Read and Write capabilities.
- Installation and IsoBuster.exe are now code signed to make Windows (more or less) happy.
- Implemented ASynchronous Drag and Drop (file extraction) on VISTA systems to avoid the VISTA over-write dialogue to become stuck under the IsoBuster window, which looks like a hang, but it isn't.
- VISTA style directory icons when ran on a VISTA system.
- Start with font Tahoma on XP or Segoe UI on VISTA.
- Smaller changes here and there.

Improvements:
- Default to SPTI on a VISTA system, even when the app is not running in admin mode.
- Now possible to drag files immediately to the XP writer drive letter (staging area)
- HTML help would not launch on VISTA due to OS changes. This is now correctly implemented.
- On VISTA the Panel with image-file-name was often not properly painted. Changed the Panel with a another Windows component.
- File-extension associations setting in the installer now improved with 'set all', 'clear all' buttons.
- HFS(+) Mac File System, with multiple of 512 byte blocks support.
- Cut long boot image-file name to spec value (if not delimited by terminating zero) to avoid illegal filename according to Windows.
- Improvements in the file-type-recognition code (files found based on their signature): *.qt, *.kbf
- Added *.VRO to the file-type list that gets the dialogue that also offers to replace with all zeroes on read errors.
- Directory (Folder) names are now ALWAYS trimmed on the right side, if the file-system contains such folder names. Windows cannot create a folder name with a trailing blank, so file extractions to that folder would fail.
- Release SPTI handle immediately of all non-optical devices. No reason to keep it open during program execution.
- Do not automatically suggest to create an IBP/IBQ file anymore if the "drive" is in fact an image file ! (any image file).
- Properties' dialogues for files and folders now show the attributes (A,R,S,H,C)
- Various small improvements here and there.

Fixes:
- In certain situations, with certain DVD discs, on certain DVD drives, not all sessions were seen. This is now fixed in the new CD/DVD recognition engine.
- Fix in Boot Emulation size determination. Before, the actual amount of 512 byte blocks was not correctly taken in account. In real life however the implementation was correctly dealing with most situations out there.
- Fixed that +VR recording-sizes were wrapped when the recording is larger than 4 GB