[sclug] CDRWIN .bin/cue format files

[John Stumbles]

I have <cough!> acquired a couple of files purporting to be a ripped 
DVD. One is xx.fooobar.kvcd.bin, at 790M about right to be an AVI 
version of the disk, and the other is a 127 byte .cue file:

$ hexdump -C xx.fooobar.kvcd.cue
00000000  46 49 4c 45 20 22 68 70  2e 61 7a 6b 61 62 61 6e  |FILE 
"xx.fooobar|
00000010  2e 6b 76 63 64 2e 62 69  6e 22 20 42 49 4e 41 52  |.kvcd.bin" 
BINAR|
00000020  59 0d 0a 20 20 54 52 41  43 4b 20 30 31 20 4d 4f  |Y..  TRACK 
01 MO|
00000030  44 45 32 2f 32 33 35 32  0d 0a 20 20 20 20 49 4e  |DE2/2352.. 
    IN|
00000040  44 45 58 20 30 31 20 30  30 3a 30 30 3a 30 30 0d  |DEX 01 
00:00:00.|
00000050  0a 20 20 54 52 41 43 4b  20 30 32 20 4d 4f 44 45  |.  TRACK 02 
MODE|
00000060  32 2f 32 33 35 32 0d 0a  20 20 20 20 49 4e 44 45  |2/2352.. 
  INDE|
00000070  58 20 30 31 20 30 30 3a  30 36 3a 30 30 0d 0a     |X 01 
00:06:00..|
0000007f

Neither 'file' nor konqueror tell me anything about the .bin file, but 
konq reports that the .cue file is a CDRWIN Cue-Sheet[1]

Googling for CDRWIN I find e.g. 
http://www.videohelp.com/tools?tool=CDRWIN which tells me that "What it 
does: ... Ripping: ... it makes images in the most compatible format, 
.bin/cue. From there you can anything with them, mount/burn/edit with 
any app u like."

I tried:

$ mount xx.fooobar.kvcd.bin mnt -t vfat -o loop 


but get

mount: wrong fs type, bad option, bad superblock on /dev/loop/0,
        missing codepage or other error
        In some cases useful info is found in syslog - try
        dmesg | tail  or so

$ dmesg | tail
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
UDF-fs: No VRS found
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
UDF-fs: No VRS found
ISO 9660 Extensions: RRIP_1991A
loop: loaded (max 8 devices)
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev loop0.


At present I'm out of clues. Anybody else have any?




[1] where does it get this information? I thought it should be the same 
as what 'file' reports

-- 
John Stumbles