published on: mingster

The .BIN & .CUE CD image format was made popular by the CDRWin software. Afterwards many programs have started supporting or partially supporting it, including: Nero, BlindWrite, CloneCD, FireBurner. The .CUE file contains the track layout information, while the .BIN file holds the actual data.

ISO is also a CD image format, but is sometimes used for 'ISO9660 format' (standard, recognized by all applications) and sometimes for unique Easy CD ISO format.

There are varity ofsoftware that can handle .BIN, .CUE,and .ISO files. Each extension can be burnedinto aCD-R or a CD-RW. Below listed some of the popular software available in the market today:

  • Alcohol 120% - My favourite, excellent software, easy and yet very advanced (burns ISO, BIN/CUE, CCD, CDI, BWT files!)
  • BlindWrite - easy to use
  • FireBurner - also very good, a single .EXE file!
  • BurnAtOnce - A handy and FREE tool for burning .bin/.cue/.iso. Easy to use.
  • Nero - many of you have this, but it can't handle all image files.
  • CDRWin - This is the original BIN/CUE software.

In case you don't have CD/DVD burner, or in case you just want to read the content without any CD/DVD media. You can "mount" the image files as virtual CD-ROM drives using:

There are also several softwares you can use to exploit & manipulate BIN/CUE files in various ways:

FAQs

1. I have a .BIN file but no .CUE?
You will need to hand made the .CUE file. .CUE can be made with just Notepad. A typical PC CD-ROM .CUE looks like this:

</p>

FILE "image-name.BIN" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00

A typical Playstation(One or Two) .CUE file looks like this:

</p>

FILE "image-name.BIN" BINARY
TRACK 1 MODE2/2352
INDEX 1 00:00:00

"image-name.BIN" being the name of the image file (IWDII.BIN, CIV3.BIN and so on...)
Notice the difference of the track mode - PC-ROMs being Mode 1, Playstations CDs Mode 2 and (Super)Video CDs are also MODE2/2352.

2. How do I make .BIN & .CUE files?
CDRWin or the BIN/CUE format is not ideal for distributing. BlindWrite suite and CloneCD perform a lot better in this purpose and can also handle various copy protections. Both of these softwares can also create .CUE files for increased compatibility.

3. I have a .BIN & .CUE, but my CD writing software can't locate the .BIN file?
Edit the .CUE file with Notepad (or similar) and verify that the FILE "C:\path\image.bin" matches the location of your image file.

4. My image file is IMAGE.BIN.EXE and I can't rename it!
Read here - http://forums.afterdawn.com/thread_view.cfm/23982

5. Sector sizes of CD image files (by Aldaco12)?
When you talk about images must think on SECTORS not on DATA SIZE. The rules are:

Facts:

  1. A standard 74 min CD is made by 333,000 sectors.
  2. Each sector is 2352 bytes big, and contains 2048 bytes of PC (MODE1)Data, 2336 bytes of PSX/VCD (MODE2) Data or 2352 bytes of AUDIO.
  3. The difference between secor size and data content are the Headers info and the Error Correction Codes, that are big for Data (high precision required), small for VCD (standard for video) and none for audio.
  4. If you extract data in RAW format (standard for creating images) you always extract 2352 bytes per sector, not 2048/2336/2352 bytes depending on data type (basically, you extract the whole sector).
  5. This fact has two main consequences:
  6. You can record data at very high speed (40x) without losing information, but if you try to do the same with PSX or Audio you get unredable CD (for PSX) od audio CD with lots of clicks because there are not error correction codes (and error are more likely to occur if you record at high speed.
  7. On a 74 min CD you can fit very large RAW images,up to 333,000 x 2352 = 783,216,000 bytes (747 Mb). This should be the upper limit for a RAW image created from a 74 min CD. Remember that if you store standard data (backup files), you can burn only 333,000 x 2048 = 681,984,000 bytes (the well known 650 MB limit).

    Note that an image size is ALWAYS a multple of 2352 bytes (you extract SECTORS), if extracted in RAW mode.</li> </ol>