grep Posted January 15, 2021 Share Posted January 15, 2021 (edited) Hello. I've been dumping several mixed-mode CDs with ImgBurn recently and the only way it seems, to make an image is to save its TOC and subchannel data. Once I got the dump ready, it appears to be really... non-standard. The .toc file doesn't look like a .toc file that cdrdao produces because it would be in plaintext with normal (LF) newlines. It's a binary file and I've no idea how to use it, or is it compatible with cdrdao. 00000000 00 39 01 01 01 14 00 a0 00 00 00 00 01 20 00 01 |.9........... ..| 00000010 10 00 a1 00 00 00 00 02 00 00 01 10 00 a2 00 00 |................| 00000020 00 00 3c 35 04 01 14 00 01 00 00 00 00 00 02 00 |..<5............| 00000030 01 10 00 02 00 00 00 00 38 35 04 42 04 |........85.B.| 0000003d If anyone's wondering, this is TOC+subchannel data for Formula 1 97 for PSX, PAL region. Is this kind of image compatible with cdrdao and if not, is there any easy way to convert it to a much more familiar bincue image? This is required to simplify my work. All of the images are stored and burned from a Linux host which has bincue images and cdrdao can burn them easily. Currently, I need to copy ImgBurn isos with the TOC to a Windows host, burn them to a CDRW with ImgBurn and then dump the CDRW into bincue. This takes usually up to an hour due to network speed and the fact the CDRW I have can only be burned with 10x speed and dumped back again at 5x-6x. Also Windows is slow on its own. I sure do enjoy heroically fighting with issues that do not exist on free operating systems. Edited January 15, 2021 by grep Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 15, 2021 Share Posted January 15, 2021 ImgBurn outputs iso or bin/cue. I do not understand where you’re getting this toc and subchannel from?! Link to comment Share on other sites More sharing options...
Recommended Posts