Topic: Data track offsets (PSX)

Here are the offsets from my data-track only dumps from px_d8

-647 offset:
Alundra 2 (U): http://redump.org/disc/2996/
Spyro: Year of the Dragon (v1.1) (U): http://redump.org/disc/1217/
FInal Fantasy Tactics (U): http://redump.org/disc/55/
Syphon Filter 2 (Disc 1) (U): http://redump.org/disc/356/
Syphon Filter 2 (Disc 2) (U): http://redump.org/disc/357/
You Don't Know Jack (Disc 1) (U) http://redump.org/disc/2961/
You Don't Know Jack (Disc 2) (U) http://redump.org/disc/2963/


+2 offset:
Area 51 (U) http://redump.org/disc/2810/
Ball Breakers (U) http://redump.org/disc/2771/
Bomberman World (U) http://redump.org/disc/2774/
Bushido Blade (U) http://redump.org/disc/2698/
Bust-A-Groove (U) http://redump.org/disc/2781/
Crash Bandicoot (U) http://redump.org/disc/2250/
Crash Bandicoot 2: Cortex Strikes Back (U) http://redump.org/disc/2688/
Disruptor (U) http://redump.org/disc/2777/
Frogger 2: Swampy's Revenge (U) http://redump.org/disc/1543/
Gran Turismo (U) http://redump.org/disc/1421/
Jumping Flash! (U) http://redump.org/disc/2697/
Kensei: Sacred Fist (U) http://redump.org/disc/2834/
King's Field (U) http://redump.org/disc/94/
Metal Gear Solid (Disc 1) (U) (v1.0) http://redump.org/disc/102/
Metal Gear Solid (Disc 2) (U) (v1.0) http://redump.org/disc/103/
No One Can Stop Mr. Domino (U) http://redump.org/disc/2823/
Oddworld: Abe's Oddysee (v1.0) (U) http://redump.org/disc/1858/
Parasite Eve (Disc 1) (U) http://redump.org/disc/116/
Parasite Eve (Disc 2) (U) http://redump.org/disc/117/
Tenchu: Stealth Assassins (U) http://redump.org/disc/2993/
Xenogears (Disc 2) (U) http://redump.org/disc/178/
Final Fantasy VII (Disc 1) (U) http://redump.org/disc/66/
Final Fantasy VII (Disc 2) (U) http://redump.org/disc/67/
Final Fantasy VII (Disc 3) (U) http://redump.org/disc/68/
Metal Gear Solid: VR Missions (U) http://redump.org/disc/1386/ (Also hash match with the database dump)

Re: Data track offsets (PSX)

Thanks, but how come you aren't added as a dumper for a lot of these games? (Syphon Filter 2, Spyro, etc)

Re: Data track offsets (PSX)

What can we do with a offset for a data-only disc?

4 (edited by iR0b0t 2008-03-10 19:48:22)

Re: Data track offsets (PSX)

ssjkakaroto wrote:

What can we do with a offset for a data-only disc?

It serves only the purposes of information roll

PX-760A (+30), PX-W4824TA (+98), GSA-H42L (+667), GDR-8164B (+102), SH-D162D (+6), SOHD-167T (+12)

Re: Data track offsets (PSX)

Oh sorry I sould have mentioned that. Those are verified games. My dumps' hashes matched the database entries but as they already had green dots I didn't include them in my matching game post. Since I got a plextor drive I thought I should post the offsets as they weren't already listed.
So my green-dot matching dumps are:

On the list already:
Spyro: Year of the Dragon (v1.1) (U): http://redump.org/disc/1217/
Final Fantasy Tactics (U): http://redump.org/disc/55/
Syphon Filter 2 (Disc 1) (U): http://redump.org/disc/356/
Syphon Filter 2 (Disc 2) (U): http://redump.org/disc/357/
Metal Gear Solid (Disc 1) (U) (v1.0) http://redump.org/disc/102/
Metal Gear Solid (Disc 2) (U) (v1.0) http://redump.org/disc/103/
Final Fantasy VII (Disc 1) (U) http://redump.org/disc/66/
Final Fantasy VII (Disc 2) (U) http://redump.org/disc/67/
Final Fantasy VII (Disc 3) (U) http://redump.org/disc/68/

Green-dot games with audio tracks that I dumped with matching hashes:
One (U) http://redump.org/disc/2012/
Dino Crisis (U) http://redump.org/disc/459/


ssjkakaroto: As I understand it you wouldn't do anything with the data track offset, it's historical information about the structure of the original disc. Anyone please correct me if I'm wrong.

6 (edited by pepsidrinker 2008-03-10 19:50:28)

Re: Data track offsets (PSX)

Huygens, it is of my opinion if it's dumped from original media the dumper should be included. I will go through the list and edit what hasn't been added yet. The time and effort you put in to get the data-only track offset is appreciated.

This is not a requirement, but as I found some games that wasn't on a list of anti-modchip games when I went through all my dumps, if you ever play the dumps with an emulator and it's unknown could you pop in and say not protected or protected if you get a red circle with a line through it. I also see some games haven't been tested for libcrypt protection.

EDIT: I had to help the kid with school came back to finish editing and it's been done, thanks Vigi.

Three years and still going strong.

Re: Data track offsets (PSX)

Thank you very much pepsidrinker and Vigi!

In regards to modchip protection, my playstation is unmodified so I don't have a way to check other than looking up the games on modchip protected game lists. I'm going to modify my PSX so I should be able to check directly soon. As soon as I do so I'll verify the protection status of my dumps. (I don't need much of an excuse to solder things). In the meen time, is there a way to tell in ePSXe or another emulator if a game is protected? I loaded Dino Crisis (U) and Spyro: Year of the Dragon (U) in ePSXe and both loaded with no problems (I believe both of these are protected).

Re: Data track offsets (PSX)

Anti-modchip games are well known for having this protection, so it's pointless that every new dump gets set to 'unknown' anti-modchip status.. the same about all the libcrypt unknown games.. If there was a way for me to set all of them to 'no' after comparing to some protection lists I would have done it immediately, but it seems like Dremora is always too busy to do this neutral .. it's definately not a reason for you to mod your playstation..

I guess the data track offset fits in the same category of useless dump information, along with the NTSC libcrypt checking, 'error count' etc.. at the end none of this info is of any significance for the dump itself.. It just adds to the mess, because only a small portion of the dumps are actually checked..

Now dumpers are even checking the error count of PS2 cd images.. this madness has got to stop (nobody is ever instructed about these new fields.. Dremora just adds them and their usage isn't controlled).

I think I'm at the point where I no longer care about all the 'information' in the database.. only the datfile is important. To sum up the imho messy db fields:

- LibCrypt and Anti-modchip 'unknown' - nobody checks these anyway! The best thing you can do is just set them to 'No'.. and also make 'No' the default option when adding new games for anti-modchip games.. remove libcrypt for non-pal regions and demo's in current entries and for new dumps.. remove anti-modchip for non-ntsc games in current entries and for new dumps..
- Error count.. what's the use of including error count '0' anyway?? If a game has errors and you happen so notice, you can add it (also useful for SafeDisc games etc).. but there's absolutely no use in checking each new dumps - and of course nobody checks the old dumps anyway!
- Ring.. also no STANDARD on when (for which system) and how this info gets added.. some dumpers add it for PSX games (I don't blame them, they don't know what they're supposed to do).
- Also the 'Added' and 'Modified' fields are really useless to the public.. they should be at least hidden for normal users imho.. and the 'Added' and 'Modified' fields should be merged (once a dump gets modified, the added field becomes invisible)..
- Some members insisted on having a 'Shared' button, but they aren't using it.. will they ever use it or is this another useless piece of info?

Just my $0,02

9 (edited by iR0b0t 2008-03-11 14:07:22)

Re: Data track offsets (PSX)

- How can you recognise when the game has the anti-modchip protection? Would it not run then? Where would it break off?

- When you runs your original game in modified console and the game has anti-modchip protection, would it run then on it?

- What concerns libcrypt, you can check now for LC1 and LC2 only, but there is also LC3 and LC4, is it sensibly to be checked now?

PX-760A (+30), PX-W4824TA (+98), GSA-H42L (+667), GDR-8164B (+102), SH-D162D (+6), SOHD-167T (+12)

10 (edited by pepsidrinker 2008-03-15 19:54:25)

Re: Data track offsets (PSX)

http://img84.imageshack.us/img84/1056/antimodchipie7.th.jpg

Here is what an anti-modchip game looks like when you run a game with it's protection on either a emulator or with a modded playstation that the mod chip doesn't overcome the protection.

It won't let you play a game with the US bios in a emulator if it's anti-modchip protected.

huygens wrote:

I loaded Dino Crisis (U) and Spyro: Year of the Dragon (U) in ePSXe and both loaded with no problems (I believe both of these are protected).

If you tried playing them with US bios and they worked they aren't protected and it should be set to no.  You don't have to mod a playstation unless you want to play games on it.

http://www.megagames.com/psx/psx_protec … s_us.shtml

Here is a list that they got of anti-modchip protect games, they say Dino Crisis is protect but you able to run it on an emulator without patching the image, without playing it on a PAL bios show it's erroneous, it also doesn't have NFL GameDay 2002 on it's list which it is as I verified it.

http://www.geocities.com/psxcplist/

Here is another list of protected games, it doesn't have any of the NFL GameDay games on it, which again I verified that they do.

Those are the only two lists I found.

Now why is an accurate game list important? Depends on the goals of redump. If the project want's build trust in it's end users as either a way to verify they backed up their original properly, or any trust in us at all, everything we display has to be accurate for if caught in deceptive behavior about something simple as modchip protection or libcrypt could potentially diminish that trust of our dumps as a whole, that is why I rather have it unknown then defaulted to no, also it will let another dumper know it needs to be checked and that other dumper might take the time to check it. if dumpers aren't going to check for that information and it's not going to be accurate I rather have it all taken off then having it to be inaccurate.

As far as Vigi said a lot I agree with him, EDIT:[Thinking about it, I believe it's wise to include the 0 error count.] But when I first asked to include error count it was with the purpose of people had the idea that the image shouldn't have any errors even though it's correct they either delete the image and not add it or do what is possible to fix all errors and screwing up the image making it a bad dump and adding it to the database, and example I see you dumped mega man legends and it has 760 errors, well in the past I dumped it and had the same amount of errors I don't remember the checksums but I had the mods delete it from the WIP as then I wasn't comfortable enough with the errors. Again to the end user we are a relatively new project with the error count documented we aren't hiding anything nor or we having people put blind faith that those dumps are correct and the errors should be there as we have it documented.

If no pal games really don't have any anti-modchip protected games I agree it should be taken off all dumps and new dumps, like when someone uses the new cd feature when they put in the flag for region it hides that option. Or demo's ect.

The ring I don't know what that is used for or what system so I leave it alone anyways.

I also agree with the added and modified as to me that's like a numbering system for GBA roms but we aren't keeping ours listed in a dat.

But again I say have a FAQ in the general discussion so people can get answers without having to post something and stickying it. It can include the various options to put in information with the new cd feature so dumpers don't put in information that isn't needed.

Three years and still going strong.

Re: Data track offsets (PSX)

Done. On a modded physical console (in non-stealth mode) both Dino Crisis (U) and Spyro: Year of the Dragon (U) come up with the red mod-chip warning. It appears that the latest ePSXe defeats mod-chip protection automatically.  (and doesn't indicate that the game is protected).

I agree about the errors! Check out my dump of Alundra 2 (U). 87664 "bad" Headers! I almost didn't submit it but it dumbed exactly the same on two drives. I did a search of the forum and finally realized what the errors box was for.

I think it would also be a good idea to explain mastering errors some in the guide so people know some images might have errors on both images and get the same checksum and that's ok.

Thanks pepsidrinker :-)

This is important to point out as there could be quite a few games that don't get added because the dumper thinks they're bad dumps.

Re: Data track offsets (PSX)

Interesting about ePSXe, I use psx v.1.13 I guess in keeping it as close as possible to the original playstation he wouldn't program it to over-come that protection. Thank you also.

Three years and still going strong.