Changes

Jump to navigation Jump to search

Talk:MAME

1,053 bytes added, 20:46, 18 March 2018
no edit summary
:::I believe you are. Chdman does not take the <code>-i</code> parameter like other programs do, as the input is specified right after the output (in the example anyways). You also shouldn't be telling chdman what it already knows; the cue sheet describes how the CD is laid out and will point to the bin file so that programs can lay it out properly (use any text editor and you'll see ".bin" somewhere in it as a track). This is why dragging the cue file onto an emulator like Mednafen works.<br/>The correct syntax in this case is: <code>&gt;chdman.exe createcd -o "Game.chd" "Game.cue"</code><br/>-[[User:FosterHaven|FosterHaven]] ([[User talk:FosterHaven|talk]]) 20:15, 17 March 2018 (EDT)
::::Thankyou for the clarification. The problem turned out to be the cue file's reference to its bin file's path. On the top line in Notepad was a path pointing to an esoteric location on an F drive for God knows what reason. I fixed the cue text by just pointing it to the bin's relative path in the same folder, and later also got rid of a two-second "PREGAP" that was set to always cut off the start of Track 02 (again... for some reason). Anyway once that first change was made, to my joy chdman converted the cue/bin to a working chd file. I should note though that while the conversion went as it should with the '''<code>-o</code>''' and '''<code>-i</code>''' in front of the output and input files respectively (and in either order), leaving out the '''<code>-i</code>''' always resulted in a '''<code>expected option, not parameter</code>''' error. [[User:Jack Ryan|Jack Ryan]] ([[User talk:Jack Ryan|talk]]) 08:41, 18 March 2018 (EDT)
:::::<code>-i</code> started being enforced after a version of the mame-tools package I might not have received (which explains a lot, actually). After reading [http://www.thekillerinstinctproject.com/kiproject/chdman.html this guide], which explains this was part of a rewrite sometime during 0.145 or after, I've been left to assume my package didn't get that version. I'll update the guide later. Thanks for bringing it to light. -[[User:FosterHaven|FosterHaven]] ([[User talk:FosterHaven|talk]]) 16:46, 18 March 2018 (EDT) Just to be certain, chdman can only handle conversions from cue/bin archives? [[User:Jack Ryan|Jack Ryan]] ([[User talk:Jack Ryan|talk]]) 12:53, 18 March 2018 (EDT) :For CDs, yes because it is the closest representation of the CD without being the CD itself (the cue sheet can be thought of as the master boot record by specifying multiple tracks or "partitions" with different kinds of data like audio, filesystems, game data, etc). But chdman works with hard drives and laserdiscs as well, so they probably require their own format (or like the guide above shows, can be worked with directly). -[[User:FosterHaven|FosterHaven]] ([[User talk:FosterHaven|talk]]) 16:46, 18 March 2018 (EDT)
927
edits

Navigation menu