Search options (Page 48 of 66)

Multi-track dumps won't get a green flag, yes. 1-track PSX (but only PSX and maybe PS2 CD) dumps are ok to be green, but the more important part is to add all the new serials and editions and remove them from the PSX missing list on wiki.

Why not to compare with EAC's 0 and +30 dumps?

IIRC, /a 30 should be used (unless there's a built-in drives/offsets db).

Well, usually the only question is if the drive supports 0xd8 to avoid the automatic descrambling. GD-ROMs and certain protections need specific drives, though, but it's a different story.

http://www.filedropper.com/tr3-macsuberror
http://www.filedropper.com/tr3-mac

First link - >1GB DIC error log for http://redump.org/disc/14386/ from GreyFox. First time he tried to dump it with DIC, it crashed with AppCrash message and the log was also more than 1GB, second time it haven't crashed, but the log was as huge.
Second link - subdump. S-W channels are filled with 0xFF, channel R has data and the last 50 sectors are filled with different data, even the P and Q channels.

Works now, but could you fix the text alignment inside the dat?
https://www.sendspace.com/file/9fgguh -- clrmamepro dat vs. dic dat

xmllite.dll is installed, event viewer logs look useless to me:

Faulting application name: DiscImageCreator.exe, version: 0.0.0.0, time stamp: 0x56dd9865
Faulting module name: DiscImageCreator.exe, version: 0.0.0.0, time stamp: 0x56dd9865
Exception code: 0xc0000005
Fault offset: 0x00004ef6

Faulting process id, Faulting application start time, Report Id are, of course, always different.

Hidden, status was changed to Red by Jackal on Mar 31 2010, 11:42.

I don't see any Puyo Puyo Fever hidden dumps, try to PM ir0b0t. A week ago ack2121 said he has submitted the [PSX] Doki Doki Poyatchio!! dump and it also disappeared (he resubmitted it later and it was added), so, maybe, some db glitches?

It was me, still using it sometimes (though, I'm trying not not to buy scratched discs), very helpful. The only hint I can give about when polishing with Brasso - never ever put your finger into the center hole while polishing, otherwise, it ends with lots of cracks in the middle.

Maybe worth to make a youtube video?

I've created the directory "C:\test", put the remove.exe tool there and created the datfile using Dir2Dat in ClrMAMEPro:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE datafile PUBLIC "-//Logiqx//DTD ROM Management Datafile//EN" "http://www.logiqx.com/Dats/datafile.dtd">

<datafile>
    <header>
        <name>-insert name-</name>
        <description>-insert description-</description>
        <category>Standard DatFile</category>
        <version>-insert version-</version>
        <date>-insert date-</date>
        <author>-insert author-</author>
        <email>-insert email-</email>
        <homepage>-insert homepage-</homepage>
        <url>-insert url-</url>
        <comment>-insert comment-</comment>
        <clrmamepro/>
    </header>
    <game name="test">
        <description>test</description>
        <rom name="remove.exe" size="99328" crc="65f5cd29" md5="8d4616abe8a949362b4b69d5417e678f" sha1="96d36b0cfa9240ef4c0502f4ea0d1f682ba277d9"/>
    </game>
</datafile>

So the ClrMAMEPro puts directory name into "game name" and "description". I think DIC can put the "filename" name there from the commandline (cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/a (val)]).

Any reason to use it?