I found myself with BIN & CUE files and not being able to access the files inside of it. I run OS X Mavericks, and just like most operating systems you can’t directly access BIN & CUE files. There are also very few applications on OS X that can access the data inside unless it’s some sort of video… which applications like VLC can access inside of the BIN file. Fortunately/unfortunately, the files I tried accessing were data files.
After lots of bouncing around the net, I found a console app called “bchunk” which is a typical Unix application. I downloaded it, unzipped it, tossed it into my /usr/bin directory (sudo cp chunk /usr/bin) so it’s in my path whenever I want it, then “sudo chmod a+x /usr/bin/bchunk” for to change permissions to execute for all.
http://jamesnsears.com/code/bchunk.zip
This is a Mach-O i386 binary, and I ran it on OS X 10.9.4 (Mavericks) so it’s known functional.
The syntax is as follows:
Usage: bchunk [-v] [-r] [-p (PSX)] [-w (wav)] [-s (swabaudio)]
<image.bin> <image.cue> <basename>
Example: bchunk foo.bin foo.cue foo
-v Verbose mode
-r Raw mode for MODE2/2352: write all 2352 bytes from offset 0 (VCD/MPEG)
-p PSX mode for MODE2/2352: write 2336 bytes from offset 24
(default MODE2/2352 mode writes 2048 bytes from offset 24)
-w Output audio files in WAV format
-s swabaudio: swap byte order in audio tracks
It’s super simple to run. I went to my downloads directory on the commandline and ran “/usr/bin/bchunk mybin.bin mycue.cue iso” of course with the names changed. iso is the base name of the output ISO file, and of course the BIN & CUE names are respective of the ones being converted.
Thought I’d share!