IsoBuster 1.6 Final

By Waqas
in Back Page News

 Share

Recommended Posts

Proficient

Waqas

Posted
Posted

IsoBuster lets you explore a CD's File System while by-passing Windows. This way you get better error handling and several retry-mechanisms to aid you in getting the data, more CDs stay 'readable' after problems, read and extraction from CD-i, VCD, SVCD, CD-ROM, CD-ROM XA, DVD, DVCD, and more.

Get Down | ISO Buster Got Mirror

Link to comment
Share on other sites
Grand Master

DsnBehind

Posted
Posted
New:

- Support for UDF 2.50, the newest version of the UDF standard.

- Support for DVD+R DL (Dual Layer DVD+R)

- Implementation of an embedded Method 3 (Mount Rainier) remapper for CD-RW.

- Implementation of an embedded Method 3 (Mount Rainier) remapper for DVD+RW.

- Automatic detection of Mount Rainier CDs and DVDs in none-capable Mount Rainier drives.

- Ability to force Mount Rainier remapping (Options menu)

- Online check to see if there is a more recent version available (Check per day, week, ... , never)

- Added support for Virtual CD image files (*.vc4 and *.000 images)

- Open via the *.vc4 (track/session descriptor file) to get the proper track/session layout. 

- Open the *.000 (data container file) to treat as an ordinary image without extra layout data.

- Added support for BlindWrite CD/DVD image files (*.b5t and *.b5i images)

- Open via the *.b5t (track/session descriptor file) to get the proper track/session layout. 

- Open the *.b5i (data container file) to treat as an ordinary image without extra layout data.

- Integration of MD5 Checksum files.

- Creation of MD5 checksum file (.md5) of the currently opened image

- Creation of MD5 checksum file (.md5) for potential (future) image files extracted a certain way

- Verify if currently opened image file's checksums match with checksums in checksum file (.md5)

- Opening IsoBuster with an .md5 file or dragging an .md5 file onto IsoBuster will trigger IsoBuster to load the image file in the .md5 file and IsoBuster will do a verify automatically.

- Options to automatically create an MD5 checksum file after image file extraction.

- Fully supports image files which consist of multiple files, including cuesheet files etc.

- The progress bar now shows the progress of the entire operation instead of object per object. For nostalgic reasons, should you like the older approach better, an option to switch this back to object per object is available in the Options menu (GUI).

- The File and Directory Time Zone information, stored in the file-systems, is now taken in account to display the time in the ListView (right pane) and to assign a time stamp to an extracted file. This way IsoBuster does the same as Windows NT, 2K, XP as opposed to Windows 9x.

- For investigative or nostalgic reasons the local time stamps can still be seen and applied during extraction via the Options Menu (Options / File Systems / General)

- The second tab of the properties window for a file or directory now shows the time zone of where the file was put on disc.

- When multiple files are extracted, and one or more files already exist, IsoBuster now offers, besides the already existing option "Yes to All", a "No to All" option on the question whether files need to be overwritten or not.

- In case of a corrupt UDF 1.5 file-system on CD-R with a missing VAT  IsoBuster's default setting is to start looking for that VAT. This can take a while when there are a lot of errors on the disc. An option has been added to stop the search if there are too many errors. Default this option is set to 'On'.

- DLA has this habit of locking a device when it 'likes' the inserted CD or DVD, even though no writing or so is done to the media. This prevents any commands being sent to the locked drive by applications which were started after the lock was applied. As a result IsoBuster could not find the drive because even the simplest of commands were rejected. As of this version the lock is penetrated via negotiation with DLA drivers. Now, if IsoBuster has control, DLA will not write to the media until IsoBuster is closed again.

Improvements :

- Sometimes Windows passes a short file name (8.3) of an image file to the program, depending on how it is done. This can cause IsoBuster to not be able to find the 'attached' files when the file is the first file of a multi-file image. A workaround to deal with this problem has been implemented.

- Workaround for devices that return Full TOC data which is not MMC compliant.

- More file-types added to the automatic file-type recognition feature for orphaned files.

- Improved compression in the installer which cuts more than 1 MB of the 'all languages version'.

- Small speed improvement during the actual scanning for lost UDF files and folders. Probably only noticeable on DVDs.

- Significant speed improvement during the last part of the scanning for lost files and folder, the so called sanitizing part.  Especially noticeable on large recovered data-sets on DVDs.

- Directory content displayed in the right ListView pane is build up dynamically now, based on what the user sees.  So in case of very large directories, e.g. 10,000 files or more, building up the content is now very fast in comparison with older versions.

- Rewrite of part of the internal file-directory-data-management which probably won't be noticed but helps for future functionality.

- Small GUI changes and improvements, e.g. build number mentioned in the About box.

- Help Button on the registration window.

- Prompt the user on Cue-sheet file creation when the file already exists and is going to be over-written.

- Ability to ignore certain errors 'always' in case of a corrupt ISO9660 or Joliet File-System. Sometimes you could get certain errors for every directory or so, now you can make a selection for all subsequent errors as well.

- Improvements in the UDF scan "Find lost UDF files and folders" in case the partition start address cannot be determined via any surviving structures.

- On Extraction, when the file(s) already exist the user is asked to over-write or not. When the user selected 'Yes' but the file was write-protected the file could still not be over-written (The program would put up an error message). Now, when the user says to over-write a file, even when the file is write-protected, the file will be over-written as asked.

Bug Fixes :

- IsoBuster could run into a memory problem during the search for lost UDF files and in case of large data-sets, e.g. DVDs with 200,000 lost files or more. The problem could not be repeated on CDs because of the limited capacity.

- The progress bar during the finding of missing file extensions was not always working properly.

- The progress bar during the check to see if all files are physically readable was not always working properly.

- A memory management issue during the finding of missing file extensions could kill the speed on very large data-sets, e.g. DVDs with +200,000 missing files.

- Following is far fetched but under WinNT,2K and XP, when the user would switch from Aspi to SPTI or vice versa during the actual extraction of an object the program would crash. Now switching can be done but the object extraction will continue via the previously selected interface.

- Recognition of certain single file *.gi image files was broken in version 1.5

- An exception error during interpreting of certain corrupt UDF file-system data could occur and has been fixed.

- In case of auto-remap-detection on older SCSI drives the program could crash due to a 'Stack Overflow' problem.

- Fixed another problem that can occur with older SCSI drives. This problem can occur when the CD has less than 2 tracks and IF it occurs it occurs with unpredictable behaviour.

- Rare exception error that could occur when an ISO9660 file system was corrupt and if the user chose to keep parsing doubtful data after being prompted a few times.

- Rare exception error that could occur while scanning for lost UDF files and folders due to unexpected corrupt data in certain UDF data structures.

- When an image file contained 2048 bytes/block the last block could not be read in raw mode. Only raw was a problem, the user data could still be extracted normally.

- When an image file contained 2048 bytes/block and the user extracted raw, the user data was always converted to M2F1 data in the raw image despite a possible M1 track mode. This has been corrected. If the track mode is M1, the raw image will contain M1 as well.

Link to comment
Share on other sites
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.