Need help with dumping

[Rocket]

To me this step is not clear at dumping multitrack disc for PSX:

Removing the pregap using Resize
To remove the Track02 pregap from Track 01, we will use a tool called 'Resize'

To use this tool, download it and extract it in the same folder as the 'Track 01.bin' file. Resize.com requires you to work in Command Prompt.

If EAC reported a pregap of 2 seconds = 352800 bytes and the filename of the image is 'Track 01.bin', the command would be as follows:

RESIZE -r -352800 "Track 01.bin"

When the correct amount of bytes is removed from the end of the image, you can go to the next step. For PSX discs, this is 'Checking and repairing the postgap'. For other discs, it's 'Ripping the audio tracks'.

I have made all precisely as is written in this section, but utility Resize does not check a file "Track 01.bin". The help is necessary!

[Rocket]

Please explain step-by-step, that it is necessary to make that utility Resize has checked up a file "Track 01.bin"

[velocity37]

The resize utility trims the padding from the end of the track, which is present on multi-track PSX games.

So what you do is place resize.com in the same folder as the Track 1 bin file.
Open a command prompt and cd to the folder where the bin and .com file are.
Then run the command: RESIZE -r -352800 "Track 01.bin"

The number is the length of track 2's pregap in bytes. For two seconds (the most common) this is 352,800 bytes.

This trims the unnecessary padding from the end of the data track. Now you can repair the track with psxt001z by issuing the following command:
psxt001z.exe --fix "Track 01.bin"

psxt001z.exe should only correct errors in 1 sector, that being the last. Sometimes no errors are detected.

[Rocket]

1) Track 01 and resize.com files in the same folder.
2) I create .BAT file with this command: RESIZE -r -352800 "Track 01.bin"
3) I try launch .BAT file, but nothin hapands.

What do I do wrong?

P.S. This is my first multi-track dump. 

[velocity37]

If you launch the bat (on XP 32-bit or earlier) the filesize of Track 01.bin should decrease by ~345KB (F5 to refresh folder). If you've run that command multiple times, you'll have to dump the track again since the track will be damaged.

resize.com doesn't pause when it's done, so the cmd window will disappear right after it shows up. If you want verification that the command has run successfully, open a cmd prompt and navigate to the folder, so the window doesn't disappear after it has finished.
Alternatively, you can pipe the output to a txt file in your BAT, like:
RESIZE -r -352800 "Track 01.bin" > resize.log

[Rocket]

Thanks, velocity37! Has write in the command end "Pause". Now all is ОК! 

[Rocket]

English text:

So, the help is again necessary to me!

The first track successfully dumped, but how correctly to dump the second track I do not know.

The disc contains two tracks. The second track - as a matter of fact not music - only a noise.

Here that the shows EAC:

                        Gap
Track01       0:00:02:00
Track02       0:00:00:00

Now I use a Optiarc DVD RW AD-7170S drive (Correction Offset +48).
http://www.accuraterip.com/driveoffsets.htm

That has put what correctly to take further audio a track?

Russian text:

Мне снова нужна помощь.

Первый трек я успешно задампил, "обрезал" утилитой Resize, пофиксил утилитой psxtoolz, прогнал через датник - трек определился. Однако мне так до конца не понятно как именно извлечь второй трек.

Диск содержит два трека. Второй трек - по сути даже не музыка, а всего-навсего какой-то шум.

Вот что показывает программа EAC:

                        Gap
Track01       0:00:02:00
Track02       0:00:00:00

Сейчас подключён привод Optiarc DVD RW AD-7170S (Correction Offset +48).
http://www.accuraterip.com/driveoffsets.htm

Что делать дальше что-бы правильно извлечь аудио трек?

[velocity37]

That's a "fun" EAC bug where 2 track data+audio discs will have bad gap detection. You can add the pregap manually, or dump the whole entire track manually with ISOBuster.

Anyways, here's what you can do to solve this:

The easy way:
Dump the disc as normal. The resulting track will be missing the pregap (since it was determined gapless).

The gap is probably two seconds. So what you'll want to do is use ISOBuster, right-click track 2 and go into the sector view. Subtract 149 from the sector counter in the box. Now hit the back arrow once (a total of 150) and you should see some garbage data followed by many 00s (This is the same process as the guide "Determining the (factory) write offset"). So, take the number of sectors there are from the start of the track to the garbage data (150 most of the time, or what you determined yourself) and multiply that by 2352.

Grab a hex editor (like XVI32). Now, edit>insert string. Click "Hex string" and type 00. Under "Insert <n> times" hit decimal and put the number you did earlier. We've now successfully added the missing pregap, so all should be well if no mistakes were made.

The hard way:
[ISOBuster completely manual, not really that hard once you're used to it.

First, we need to determine the pregap length. The gap is probably two seconds. So what you'll want to do is use ISOBuster, right-click track 2 and go into the sector view. Subtract 149 from the sector counter in the box. Now hit the back arrow once (a total of 150) and you should see some garbage data followed by many 00s (This is the same process as the guide "Determining the (factory) write offset").

So, take the number of sectors there are from the start of the track to the garbage data (150 most of the time, or what you determined yourself) and multiply that by 2352. Note this for later, denote as "gap length, bytes". You can also dump the disc with Slysoft CloneCD and run the resulting sub through Subcode analyzer to have the gap length automatically determined (in seconds).

Now, ISOBuster doesn't give us offset correction, so we will have to do that manually. Look at the sector with garbage data and determine the combined offset (as per the guide). Because the data is going to be pushed forward or backward, we have to dump an extra sector worth of data. So right-click the track and click extract from-to. The start sector depends on the combined offset. If your offset is <-588 or >588, you'll divide it by 588, round up (or down if negative offset) (-617 would be -2, +1566 would be +3, etc), and start dumping that many sectors early or late. Unless the offset is evenly divisible by 588, we will need to add +1 to the length.

In the unlikely event that the combined offset is evenly divisible by 588, we don't have to trim. Otherwise:
Let us pretend that we determined the combined offset to be +32 (+2 disc, +30 drive). What we'll do is open the Track 2 bin in a hex editor (such as XVI32). Now, because the offset is positive, the data will be pushed forward (if the offset was negative, it'd be pushed backward, so we subtract 2352 from offset*4 until we get a negative result. Convert to positive, and that's the 00 bytes to skip). There are 4 bytes in a sample, so the data is pushed forward 128 bytes in our example. Open the file so that the 1st byte is highlighted, and Address>Goto. Click decimal and "relative down". Set the number to our offset -1 (since we start at 1 and want to get to 128, we go down 127). Now some 00s should be skipped. Go to edit>delete to cursor. The extra bytes will be removed.

Now, edit>insert string. Click "Hex string" and type 00. Under "Insert <n> times" hit decimal and put the number as your previously noted gap length in bytes. Hit OK.

Now there's just one final step, and that is to remove the extra data from the end. Drag the scroll bar all the way to the bottom. The last byte should be highlighted. Take the number of bytes you deleted from the beginning (128, in our example) and subtract that from 2352 (2224, in our case). This is how many extra bytes remain from that "extra sector" we dumped in ISOBuster, which we have to remove. So, Address>Goto, decimal relative up, our number - 1 (2223 in our ex). Now choose edit delete from cursor. This will remove the garbage data from the end of the track.

So, the steps we've done: Dumped the data track with an extra sector to account for offset. Trimmed the extra sector from the beginning and end of the track, correcting the offset in the process. Inserted the pregap.

It's worth noting that since we're dumping the last track, it would be ideal if the combined offset was negative

Now, not in your case, but in the event that the track we are dumping isn't the last, we have to delete the next track's gap from the end of the file. In a 2s 2s 2s common disc, this would involve deleting 352,800 bytes from the end in addition to the bit from the extra sector.

[RiMMER]

Rocket, just remember that the biohazard 3 trial dump you did is CORRECT.

I am sure of it, trust me, I'm too much of a hardcore fan of the series to know. There's nothing more to be done about that dump.

[Specialt1212]

I just ran into a game with this same problem (Monster Rancher), it only has two tracks....

I extracted the first track like normal then I opened the sector viewer of track 2 in IsoBuster and subtracted 150 from the starting point of 138340 which was 138190 and determined it has a pregap of 2 seconds or 2 full rows or garbage which meant 150 * 2352 = 352800

Now should I use the resize (FPCopy) and psxt001z tool on the track01.bin file and do the typical

- FPCopy64 -r "track01.bin" -352800
- psxt001z.exe --fix "track01.bin"

Also what file should I be editing with the hex editor track01.bin?

Lastly do I extract the audio with EAC or Isobuster?