About "bad" headers and image errors
Re: About "bad" headers and image errors
These results are after doing resize.
-
pepsidrinker
- Posts: 414
- Joined: Mon Jun 08, 2026 1:26 am
Re: About "bad" headers and image errors
What Gex version is that, the games in the PSX part don't have audio tracks? Which then you won't have to do resize. What I had to do once with NFL GameDay once I resized it, I checked with CDMage and it gave no errors but when I used psxt001 to see if it had EDC it fixed a whole bunch of errors which I thought was strange so I made a cue of the tracks and loaded it in daemon tools so I could see if the sectors match the original which it didn't (it was lower) so if the game does have audio, I suggest you redump it, resize it check with cdmage (Make sure there is no errors), do what has to be done with audio make a cue and check the sector size like said before.
Also if the dumping tools give you a weird gap, you can just dump the first track and check with cdmage and the amount of errors as long as they are at the end of the image and one right after each other like in your fix log that's the pregap. 150/149 2 sec ect.
Again MODs if anything I say is wrong please correct.
Also if the dumping tools give you a weird gap, you can just dump the first track and check with cdmage and the amount of errors as long as they are at the end of the image and one right after each other like in your fix log that's the pregap. 150/149 2 sec ect.
Again MODs if anything I say is wrong please correct.
Re: About "bad" headers and image errors
Yeah that Gex dump shouldn't be fixed..
we're gonna have to update the guide, but I think it's best to have a new psxt001z version that only fixes the last data track sector (and after that reports the remaining errors for reference.. and maybe move the current fix command for foreign image fixing to --fixall for instance)..
we're gonna have to update the guide, but I think it's best to have a new psxt001z version that only fixes the last data track sector (and after that reports the remaining errors for reference.. and maybe move the current fix command for foreign image fixing to --fixall for instance)..
Re: About "bad" headers and image errors
I'm sure Gex has 4-second gap. Theoretically there shouldn't be any errors in sync or header — otherwise the sector would be unreadable (because drive used these two fields to automatically fix offset for data tracks).
Re: About "bad" headers and image errors
Well I followed the guide to the very last detail... I checked the gaps and they were 2 seconds... Although I might try to dump it again with a different gap detection method to see if it does come out to 4 seconds... I used the same settings with my other games and they were ok... The gex version that I have is from 1999 I believe, it's a version which has a demo for Gex: Enter the Gekko as well, so it is a version that was released well after the first version of the game... It's not a platinum version, it's not a Greatest Hits, it has a normal cover. I didn't post the crc data or anything else like that yet because it found it strange that it would have so many errors. I'll get you guys that data when I get back home.