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!

Edit: talked to OP and he said he didn't need an account anymore.

3

(2 replies, posted in General discussion)

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"

4

(2,834 replies, posted in General discussion)

samari,

my computers keep detecting a 'virus' with the later versions of dic, I know 20210102 for sure. 
Trojan:Win32/Wacatac.D4!ml

I'm assuming it is a false positive of sorts, but I wanted to pass this along, as it could be concerning to some, plus I know some of my devices just outright delete it.

Edit: tested with latest test version - same issue.

5

(2 replies, posted in General discussion)

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.

6

(3 replies, posted in Guests & account requests)

Hey there Cheebs! Thanks for joining up.  Please bear with us and we'll get your account added as soon as we can.

Thanks.

7

(9 replies, posted in General discussion)

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.

8

(9 replies, posted in General discussion)

It sounds counterintuitive, but try a higher speed, or try a lower speed and change /c2 20 to something like /c2 200 to give it more attempts. 

If the disc looks really clean with no identifiable scratches, give it a few more attempts at different speeds and you might have some success.

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.

Hey there, what version of DICUI are you using?

I know that this was an issue on some previous versions.  You might want to try the latest DICUI 1.17.1 and see if that fixes the problem:

https://github.com/SabreTools/DICUI/releases

If you are still having issues with it after that, let us know!

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!

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!

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!

15

(1 replies, posted in Guests & account requests)

fuzzball wrote:

I need an account for DICUI.
username: fuzzball_for_dicui

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.

For those of you wondering about the PS1 method I've been using to easily get ringcodes, this is VERY similar to what I've been doing, and it works extremely well.

The attached photo is acquired using only my cellphone.  No special bulbs, IR flashlight, other hardware, or even post-photo modifications on this one.

17

(6 replies, posted in General discussion)

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.

In my opinion, Region [as it relates to game releases] should be distribution, not where it was manufactured, assembled, etc. 

If a game was ONLY sold in a certain region, and we have proof of that, then that country is where the region should be.  If it is sold in multiple regions (without packaging variance), that is another story.

I don't know the details about this particular example, nor am I an expert in unlicensed, but if it truly was only distributed in the USA, then it should be USA Region and not Europe.

19

(2,834 replies, posted in General discussion)

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.

20

(2,834 replies, posted in General discussion)

sarami wrote:
sadikyo wrote:

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

Thanks test. I want to see your disc log. Would you upload them?

Yes - this is the one that worked with the test version

21

(2,834 replies, posted in General discussion)

sarami wrote:

Transfer length was too large.

uiDirPos: 341431, TransferLength: 82

Fixed it. Test plz. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

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

Please give sir LastCat wiki access.  He's dumped many discs and works on a variety of systems, and would like to update wiki as he goes or purchases things.  Thanks!

23

(3 replies, posted in Guests & account requests)

superg is an awesome PS contributor.  Let's get him some access! smile

24

(1 replies, posted in Fixes & additions)

fuzzball - I understand this issue has been discussed before without a perfect resolution.  I have reached out to the redump mods and admins, so that we can have a discussion and then get this settled once and for all, about guidance for correct EXE dates. 

I will update as soon as I find out.  Thank you for your patience as we discuss and get it settled.

25

(11 replies, posted in General discussion)

Works for me!

As I said before - I don't really have an issue with the change itself so if this enables more consistency - sounds good!