Search options (Page 2 of 3)

There are cases where different pressings of the discs have completely different ring codes (e.g. Sanitarium PC), so you can never really be sure. Unless you require everyone to post photos of the games, of course, but that would be crazy. Not even the SPS guys go that far, and that's saying something.

I used ddump for my MDK2 dump and it seems to work well. If there's a way of getting the actual data of the sectors I've been unable to find it.

I think "illegal TOC" is being used incorrectly here; long ago, some people started using that term to refer to discs with more than one data track, but that's actually within the standards, and the BIN/CUE format should be more than enough to make a full dump (just like in the PC Engine games).

IsoBuster defaults to .iso for single tracks and .bin for images of the entire disc, but you can change the extensions if you want: Options -> Image Files -> ISO/BIN/TAO

My dumps were made with an LG drive and rawdump, so they should be good.

There are exceptions, though... for example, here in Spain we got the French versions of the SNES Dragon Ball games, yet they are marked as (France) in the No-Intro dat. And I'm talking about official releases, not imports.

If you have a (real) Plextor drive you can use PerfectRip, it should detect the gap properly.

But aside from that, this is a real annoyance. Has anyone tried to contact Andre Wiethoff and tell him about this issue? Perhaps he'd be willing to fix it...

More specifically you should use pSX, because ePSXe apparently ignores the region of the BIOS and the game always boots.

This reminds me that I should check my old PSX dumps for anti-mod protection...

Well, getting a drive that can overread into the leadout is definitely the easier solution, but not the only one. It's still possible to dump the last track correctly if you use a drive with a combined negative offset for that particular disc.

You can use the "reMove" tool by themabus, it's even better because you get the removed part in a separate file, in case you want to check it. It's also better in that it works with 64-bit operating systems (resize doesn't). Get it here.

For example, to cut the last 150 sectors (352800 bytes) from a file called track01.bin:

remove -size=150sec track01.bin gap.bin

With that, track01.bin gets resized and gap.bin contains the removed part.

Don't worry, the 162C is functionally identical to the 162D. But be warned that it's a DVD reader only. If you want to burn DVDs you'll need another drive.