Quick BIN/CUE burning FAQ.
Utils needed:
notepad
winimage(http://members.aol.com/gvollant/winima50.zip)
pdsfvwin32(http://205.134.182.35/files/pdsfvwin32.zip)
FIREBURNER(http://www.fireburner.com/downloads/FireBurner106.zip)
winrar(ftp://ftp.download.com/pub/win95/utilities/wrar270.exe)
Table of contents.
1. Testing the distribution files
1a. using pdsfvwin32.
2. Decompressing
3. Checking the contents.
4. Testing the bin.
5. Binchunking.
6. Burning.
in this faq, i will be using AVP gold iso cd1 as an example.
1. Testing the distribution files
CRC errors are a big problem and checking the files before extraction is quite important.
The most common utils used are winsfv32 or the new one, pdsfvwin32.
personally i prefer using pdsfvwin32 since it's easier to use.
a. using pdsfvwin32.
right after you fire up pdsfvwin, you can see four buttons:"create sfv file", "verify single file(s)",
"CHECK WHOLE RELEASE", "exit". You guessed it-we will be using "CHECK WHOLE RELEASE" button.
Now, click "check whole release". A big window pops up. now click "browse for SFV file..."
and point it to the place where you got your files. After you select SFV sheet, click "check sevected sfv file now!"
The process takes around 3 minutes to complete-notice how much faster it is compared to testing inside your
compression program. Also it insures that the files are exactly the same as they came out from the release group.
After the process completes, you get the following kind of output:
-------------------------------------------------------------
No SFV file selected currently ...
Selected SFV file C:\downloads\CD1\flt-apg1.sfv
Processing file C:\downloads\CD1\flt-apg1.sfv
Processing FLT-APG1.001...
... local CRC32 = 0x66FCF642...
... checksum matches, file is OK!
Processing FLT-APG1.002...
... local CRC32 = 0xA57E79EC...
... checksum matches, file is OK!
Processing FLT-APG1.003...
... local CRC32 = 0x65DF1AD9...
... checksum matches, file is OK!
Processing FLT-APG1.004...
... local CRC32 = 0x5DAE7553...
... checksum matches, file is OK!
Processing FLT-APG1.005...
... local CRC32 = 0xBEF9055A...
... checksum matches, file is OK!
Processing FLT-APG1.006...
... local CRC32 = 0x1D8F2108...
... checksum matches, file is OK!
Processing FLT-APG1.007...
... local CRC32 = 0xA7A55006...
... checksum matches, file is OK!
Processing FLT-APG1.008...
... local CRC32 = 0x5ADE866E...
... checksum matches, file is OK!
Processing FLT-APG1.009...
... local CRC32 = 0xA0860A55...
... checksum matches, file is OK!
Processing FLT-APG1.010...
... local CRC32 = 0xC904A85A...
... checksum matches, file is OK!
Processing FLT-APG1.011...
... local CRC32 = 0xDC80D9B0...
... checksum matches, file is OK!
Processing FLT-APG1.012...
... local CRC32 = 0xBC07FE34...
... checksum matches, file is OK!
Processing FLT-APG1.013...
... local CRC32 = 0x42CB066D...
... checksum matches, file is OK!
Processing FLT-APG1.014...
... local CRC32 = 0x4ABD98A8...
... checksum matches, file is OK!
Processing FLT-APG1.015...
... local CRC32 = 0x28E9C3BF...
... checksum matches, file is OK!
Processing FLT-APG1.016...
... local CRC32 = 0x04B31A13...
... checksum matches, file is OK!
Processing FLT-APG1.017...
... local CRC32 = 0xD94ECBE7...
... checksum matches, file is OK!
Processing FLT-APG1.018...
... local CRC32 = 0x3B23B79D...
... checksum matches, file is OK!
Processing FLT-APG1.019...
... local CRC32 = 0x96466B5F...
... checksum matches, file is OK!
Processing FLT-APG1.020...
... local CRC32 = 0xEFF8F082...
... checksum matches, file is OK!
Processing FLT-APG1.021...
... local CRC32 = 0x68D39FF7...
... checksum matches, file is OK!
Processing FLT-APG1.022...
... local CRC32 = 0x9333D6FD...
... checksum matches, file is OK!
22 files processed, 22 good, 0 bad, 0 missing...
Ready...
Selected SFV file C:\downloads\CD1\flt-apg1.sfv
-------------------------------------------------------------
The most important part part is the last few lines:it's the summary of the test. In this case, all the files are OK.
If any files are bad-it's easier to releech them. Some programs have some kind of fixing function but putting
the recovery record(additional info required to repair the file) takes additional space and therefore is omitted.
2. Decompressing
Obviously most isoz are very big and they are compressed to make 'em smaller. Also they are spanned into
multiple volumes to ease uploading. Usually the size is around 15mb-20mb.
Here's what compressed AVP gold cd 1 looks like.
This is a "dir" command's printout so bare with me.
----------------------------------------------------------------
size date time name
15,000,000 04-15-00 1:35a flt-apg1.001
15,000,000 04-15-00 6:15p flt-apg1.002
15,000,000 04-15-00 6:38p flt-apg1.003
15,000,000 04-15-00 7:02p flt-apg1.004
15,000,000 04-15-00 7:25p flt-apg1.005
15,000,000 04-15-00 7:51p flt-apg1.006
15,000,000 04-15-00 8:15p flt-apg1.007
15,000,000 04-15-00 8:32p flt-apg1.008
15,000,000 04-15-00 8:47p flt-apg1.009
15,000,000 04-15-00 8:57p flt-apg1.010
15,000,000 04-15-00 9:09p flt-apg1.011
15,000,000 04-15-00 9:25p flt-apg1.012
15,000,000 04-15-00 9:42p flt-apg1.013
15,000,000 04-15-00 10:01p flt-apg1.014
15,000,000 04-15-00 10:19p flt-apg1.015
15,000,000 04-15-00 10:35p flt-apg1.016
15,000,000 04-15-00 10:54p flt-apg1.017
15,000,000 04-15-00 11:11p flt-apg1.018
15,000,000 04-15-00 11:33p flt-apg1.019
15,000,000 04-15-00 11:54p flt-apg1.020
15,000,000 04-16-00 12:13a flt-apg1.021
8,986,715 04-16-00 12:24a flt-apg1.022
----------------------------------------------------------------
flt-apg1.022 is the last volume of the distribution.
Usually isoz come compressed using RAR format. Usually, RAR's volumes look like .rar, .r01, r02, r03....
In this case it's .001, .002, .003...
You will need to use a program called WinRAR to unpack those files.
If you have trouble doing it, look at the help files(RTFM). One hint:
if you got pattern like .001, .002, .003... start with the first file
(the smallest digit in teh extention-.001 is the head volume).
3. Checking the contents.
When the decompression is complete, you will likely end up with two files xxxxxxxx.bin(jumbo file) and xxxxxxxx.cue
Here's one thing you want to do: check the bin's path inside the .cue.
Example of a bad cue:
----------------------------------------------------------------------------------------
FILE "E:\porno\beastality\horsesuck\cuz\im\a\sicko\FLT-APG1.BIN" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
----------------------------------------------------------------------------------------
Example of good cue:
----------------------------------------------------------------------------------------
FILE "FLT-APG1.BIN" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
----------------------------------------------------------------------------------------
Notice that the good cue has no path, just the file's name.
By the way, the quotes are optional, you can remove them as well.
Also note that if you get your iso from a release group, this is usually taken care of for you.
If somebody rips a cd for you, you better check the path because it's not likely to be done.
4. Testing the bin(data tracks only).
Here's an important part. This isn't really important when you get an "official" release,
but it's a necessity when somebody rips a cd for you to d/l.
To test the .bin's integrity, do the following: Launch FireBurner, click "visual cue burner/binchunker",
right click inside the new window and choose "load tracks from *.cue", now point it to your cue sheet,
after you do that, you will see the track list.
Now select the data track, right click and choose "scan track for corruption".
if there are no errors, you will get something like that:
---------------------------------------------------------------------------
Checking Mode2/2352 Track 1 from C:\downloads\CD1\flt-apg1\FLT-APG1.BIN
Verification complete (No errors found)
---------------------------------------------------------------------------
if you get that, you are ready to burn. If you get error messages,
and the iso is from a release group(not reripped by someone), then it might be a bad release.
5. Binchunking.
If you don't have a burner(well sometimes rips are bad and it's easier to d/l the iso),
you can still convert the contents into .iso format
To do that, you have to load the cuesheet, select the data track, right click and choose "save track as(BINChunker)"
The files will be named automatically. You can also extract the audio, but it's pointless.
After you extract the data track, you get a big .iso file.
To extract files from .iso, you have to use WinImage.
Read the online help for more info on extracting if you can't figure it out yourself(RTFM).
6. Burning.
Here's the moment you have been waiting for. Load the cue. right click and choose "burn / test burn",
unclick "test burn" and "multisession" and click "OK"
After the burn completes, install the stuff you just burned.
Notes: don't use cdrwin, too many cracked copies burn coasters.
No comments:
Post a Comment