Old Differential Backups
Differential backups created prior to IFW/IFD/IFL 2.05 may contain metadata which prevents TBIView from properly accessing the file.
It's highly recommended that you view image files with all files available on the same media. Viewing files spread across removable media may require excessive amounts of disk swapping.
.IMG files on optical media
If you are working with an .IMG files that resides on removable media (e.g. CD/DVD discs), you may use multiple removable media drives to ease the process. For example, if you are opening an image that is spanned across two DVD discs, you can insert the first DVD of the set in one DVD drive, and the second DVD in another DVD drive. TBIView will automatically check all applicable drives for the second disc. NOTE: This only applies to .IMG files and NOT .TBI files. If you'd find this feature useful for .TBI files, please notify TeraByte Unlimited support. In the mean time you can simply copy the files to a hard drive for access.
If you find that .IMG or .TBI files are not opened by TBIView when you double click them, you need to restore the file association to TBIView. To do this, simply reinstall TBIView. (Your existing TBIView settings, and your images and index files, if any, will not be affected.) Please note that if you are using another program that takes over the file association, this situation may recur.
Direct Burned Optical Media
Direct burned CD/DVD/BD discs may result with "Error 3 while reading meta data from TBI file.". This is because the last disc of a direct burned disc has file sizes that include unused areas of the disc. This cause windows read-ahead feature to report any reads that would extend beyond the used space to be reported as a read failure with zero bytes read. The reason Image creates discs with the full disc allocated as files and doesn't burn extra sessions for the last disc is because it tries to use all the disc rather than using some arbitrary number of reserved sectors for session closing at the end. When media was expensive there was a desire to not push a a small amount of data to another disc when it would actually fit and there is no reliable method to determine the number of sectors a drive/media will require to close an existing session and open/close a new one. The work around is to use TBICD2HD to copy the files off the CD/DVD/BD then use those files or burn another disc using BINGBURN. The new disc will not have the Error 3 issue.
You can tweak the parameters used by TBIView by creating a DWORD value named IndexSize under the registry key:
The minimum value is 20 and maximum value is 1000.
The default value is 200 for the low word and 100 for the high word. The low 16-bit word is used with .IMG files and the high 16-bit word is used with both .IMG and .TBI files. The values control the amount of information the application uses to track the location of data. A large value may be slower from too many lookups and a small value may be slower due to more random disk IO.