Search options (Page 1 of 2)

DICUI is fixed now in WIP builds. The error file was renamed between builds. This has been addressed. If anything like this comes up again, please ping on Discord in the #discimagecreator channel. I rarely look in this thread for DICUI related anything.

@sarami or @Square: do either of you know how to detect that "red hand" antimod screen? I'd like to see if I can get that working in part of DICUI.

Maybe split the difference, we already have the concept of "Enhanced CD", why not something like "Enhanced DVD" and "Enhanced BD"?

Thanks for the responses Sarami! Okay, knew it was probably some protection I didn't know about.

And I'm guessing for the GD-ROM stuff, that's why it has to be swapped. Unfortunate, but makes sense.

Quick question: What is the purpose of /ss ? I know that it scans every single sector looking for copy protection, but it seems like the only place that finds protection is at LBA -1, which seems to be covered anyway. Are there forms of protection that are on other sectors that I'm unaware of (seems like the most likely option)? And is the output of that scan stored somewhere if it finds something?

I'm going to do some gravedigging here, so I apologize in advance. I recently came across the issue of trying to detect SafeDisc v3/4 without ProtectionId. There seem to be no public instructions out there on how these protections are actually found. If anyone here has even the slightest conceptual idea, I'd love to hear it. Thanks in advance!

So, as the coder (of the 3) who is being called out here, I'd like to ask for clarification with a bit of back-explanation:

In most APIs that I've personally used, the data format that is expected has been ironed out by the group who created the API. This means that in most cases, as a programmer, I'd expect things like the XML structure to be a known thing and at least a DTD or XSD would be available for what is expected (including what is optional or required).

If this information could be provided, it would be semi-trivial to add another output format alongside the submission info that DICUI currently outputs. It raises a few more issues on our side (including pre-filling any required information), but that is not that big of a deal.

If this functionality can be exposed, we will do our best to conform to whatever standard is put forward so that dumpers can submit the standardized information in a more consistent way.

I have one possible suggestion: Every time my drive overheats, it starts throwing the "COMM" errors, which are hardware issues. If at all possible, can those be treated like C2 errors? I'd like for those sectors to be rescanned at the end just like that, since right now, if my drive decides to crap out like that in the middle of a dump, I have to stop it and start all over, since it won't be caught as an error until the very end.

Running the newest version, it gets to the same "Reading DirectoryRecord 34/ 68" and just cycles forever. It appears to be using both CPU and a lot of hard drive time. I left it running for about 15 minutes at that state, and managed to create a 19.5GB text file for "SimCity 3000 (USA)_volDesc.txt". Using glogg to open it, the last few billion lines (slight hyperbole) they all say the same thing:

Direcory record size of the prev sector maybe incorrect. Skip reading this sector
========== LBA[200205, 0x30e0d]: Directory Record ==========

I can't exactly compress this in a reasonable way and upload unfortunately.

Preface: I searched the forum for similar issues, finding something else that had been already fixed back in 2015. I've also tried a second drive to test if the disc was bad and I've made sure that there are no scratches. I have additionally tried multiple versions of DIC including a couple ancient ones that I got my hands on, all with the same (or similar) results.

With that out of the way, I'm running into an odd issue where the disc I'm dumping fails at the Reading DirectoryRecord phase. As far as I am aware, there is no copy protection on this disc that could be causing an issue. Below is the output that I am getting. Additional logs are available on request.

OS
        Windows 8 Professional  64bit
AppVersion
        x86, AnsiBuild, Oct  2 2017 21:36:02
/sf val is omitted. set [60]
/c2 val2 is omitted. set [4096]
/c2 val3 is omitted. set [4]
CurrentDirectory
        C:\Plextor
WorkingPath
         Argument: SimCity 3000 (USA).bin
         FullPath: C:\Plextor\SimCity 3000 (USA)
            Drive: C:
        Directory: \Plextor\
         Filename: SimCity 3000 (USA)
        Extension: .bin
Start time: 2017-10-04(Wed) 21:44:41
Set the drive speed: 54563KB/sec
Allocating packed memory for C2 errors: 8192
This drive supports [OpCode: 0xd8, SubCode: 0]
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
This drive supports [OpCode: 0xd8, SubCode: 3]
This drive supports [OpCode: 0xd8, SubCode: 8]
Checking reading lead-out -> OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Reading DirectoryRecord   34/  68

Thanks in advance for any pointers.

So... this is possibly the weirdest issue I've run into so far. With the last few builds, there is a single CD game of mine that will get to about 56000 sectors and then the drive pauses and then reboots. When the drive comes back, it doesn't recognize there's a CD inside anymore.

The reason that I'm even posting this here is that I have NOT had this issue (same drive, for clarity) with either IsoBuster or ImgBurn. I can attach the logs, if those would be helpful, but I was wondering if anybody else ran into this before and if there is any ways to get around this.

Hey again, I'm trying to dump a DVD game on my drive, and I'm running into an error that I have not been able to get past. For reference, I tried 2 different DVD-capable drives.

LBA[2075360, 0x1faae0]: [F:ReadDVD][L:131]
    Opcode: 0xa8
    ScsiStatus: 0x02 = CHECK_CONDITION
    SenseData Key-Asc-Ascq: 03-11-05 = MEDIUM_ERROR - L-EC UNCORRECTABLE ERROR

I did think at first that it was related to it being a DVD-9 but the sector it stops on is not the same as the layerbreak sector (2084960). If there's something I'm missing or need to attach, please tell me. Thanks in advance!