Search options (Page 25 of 27)

Hello and welcome! We'll get your account added in a bit.  In the meantime, I'll do what I can to assist you via discord.  Thanks!

That information should be contained in the param.sfo.   If you use DIC, it automatically populates it in the ***_disc file toward the bottom by "TITLE_ID"

It is exactly as Agent said.  The version numbers for PS2, for example, are internal to the data, and thus accurate versions for those releases.  Whereas PS1 has no internal version numbers, so identifiers such as Rev 1, Rev 2 are used.

How many sectors are detected as bad?  Is it just 110740 or is it many of them?

Unfortunately there are a lot of variables here - do you have another drive to test it on?  Even a non-plextor / non-redump drive just to see if it can read/dump the disc with no errors/unreadable sectors?  It's also possible it is a mastering issue.

Cool.  From what I understand, there could also be an issue with cd-i ready discs that is known atm, but you could certainly give this a try.  I believe some others are looking into issues with cd-i ready.

Hello,

Redump only stores metadata / hash information in the database, and does not store actual game images.

Hello and thank you for your interest!  Please bear with us, and an administrator will get your account added soon.  In the meantime, feel free to join the VGPC Discord, where we can discuss and support contribution efforts: Discord
Thanks!

We don't allow multiple / alternate accounts.  You can use your existing login info with DICUI, or if you'd prefer not to use that, it's not required.  You can PM me if you have any additional concerns/questions about this.

The convention most used on redump for volume titles, is a space between the "." and the number, so you'll find most entries will say "Vol. 2" instead of "Vol.2" even if there is no space on the disc.  This is a sort of normalization/standardization that is done with the romanization here. 

I am working on a rough guide for some of these conventions, but it currently is a WIP.  When I have something remotely organized, I'll share for further review and discussion to help address things like this so everyone can be on the same page.

so, I already submitted this information to DICUI for update, but I wanted to share here also.  I was talking with Enker about the layerbreak information for xbox discs, and apparently people (myself included until I discovered the issue) have been submitted the incorrect layerbreak for xbox discs, when they should essentially all be the same default one. 

Here is what Enker shared with me:

"Hey, yes the DICUI layerbreak for Xbox/Xbox360 (and also Blu-ray discs) is incorrect. It's caused by DIC reporting two layerbreaks, one for the video partition and one for the game partition (DICUI uses this one). It never logs the actual layerbreak that takes into account the video partition+middle zone that comes before the game partition. If you add the video LayerZeroSector + Middle Zone + game LayerZeroSector, then you get the default value on the disc page.

DICUI could omit the layerbreak for Xbox/Xbox360/Blu-ray discs, since we never need to enter one for those discs."

As I said, I've already sent this to DICUI to pull the correct one, but I wanted to share with you as well sarami, in case anything has to be done on the DIC side.

The correct layerbreak is apparently the default of 1913776, and not the 1715632 that often/sometimes gets reported.

I was having the same problem - but I tried with the new test version you shared here - and it worked.  Thanks!