 |
This article needs additional citations for verification. Please help improve this articlebyadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "BlindWrite" – news · newspapers · books · scholar · JSTOR (May 2009) (Learn how and when to remove this message) |
 | |
BlindWrite main interface
| |
| Developer(s) | VSO Software |
|---|---|
| Stable release | 7.0.0.0 / January 25, 2013; 11 years ago (2013-01-25)[1] |
| Operating system | Microsoft Windows |
| Available in | 33[citation needed] languages |
| Type | Optical disc authoring |
| License | Shareware |
| Website | www |
BlindWrite, the successor to BlindRead, is a computer program that writes to recordable CDs. The Blindread software, which reads CDs and writes CD image files, has been discontinued as a separately released product, but BlindRead's code is included in the newer BlindWrite suite of software that also code to control[clarification needed] CD writers. BlindWrite's most distinctive feature touted over other pre-existing CD writing software was to use the CD images BlindRead made. BlindRead's main features were the use of Sub codes and its willingness to be "blind" to errors and continue the copying process, rather than quitting when encountering reading errors often caused from hardware trouble or disk damage (such as scratches or even intentional "damage" created by the manufacturer as a form of copy protection) that would often cause many other software packages to terminate the reading process.
Support for "Sub codes", also known as "Sub Channel Data", distinguished the files created with BlindRead from other software that created CD image files. The "Sub code" data could be written in *.SUB files added to either of two already-existing popular formats (ISO image and Cue sheet), or the Sub code data could be written in *.BWS files in BlindRead's native format that consisted of writing a CD image in a group of three files. This format, which has become known more widely as the BlindWrite native format (now that BlindRead is not maintained and distributed as a separate product anymore), has two or three files for a proper image. The *.BWS Sub code image is optional and may or may not get created depending on an option selected in the software that created the image. The *.BWT control file is another relatively small file (that may be a very small number of kilobytes when part of a multi-file CD image for a full-sized 650MB CD) that is typically the file referred to in the user interfaces of software that supports this format and chooses just one file extension per CD image for the purposes of filename selection. (This includes VSO's software and Daemon Tools.) The *.BWI file is the large image file.
BlindWrite version 5 (released in Q4 2003) has been found using new native files that come in pairs. The files use the extensions *.B5T (a relatively small file) and *.B5I image files.
BlindWrite version 6 (released in Q3 2006) also has been found using new native files that come in pairs. The files use the extensions *.B6T (a relatively small file) and *.B6I image files. This has also added support for Blu-Ray discs.
The BlindRead format has been supported by software other than BlindRead and BlindWrite, including Daemon Tools, which was some of the earliest supporting software (capable of using *.BWT files even before Blindwrite was released). The format was embraced by enthusiasts who were interested in making "more perfect" copies of CDs by using a process that used the Sub code data that other computer software did not support (and so ignored, instead of used).
BlindWrite won the TopTenReviews Bronze Award in 2009.[2]
