• Useful Info

RAR Notes:

• The .rxx extension is standard for RAR posts. But you may encounter other extensions that are still RAR files. Aside from .rxx, three common extensions: .sxx, .cxx, and .0xx, may also be seen (though rarely in the main groups TV & movie groups).
  
  
• When there are more than 100 files in a post, the standard “.rar, .r00, .r01...” extension switches to .sxx (.s01, .s02, .s03, etc.) for the later files. For huge file sets, WinRAR uses later letters in the alphabet (.t01, .u01, etc.). Download all the RARs and “SARs” into one directory, and start your extraction from the .rar file, as normal. WinRAR will automatically extract the encode from the files.
  
  
• The commonly used .rxx extension (the default in WinRAR, up to v3) can be changed when the RAR set is created; any sequential extension can be used.

  Occasional you will see posts using “.001, .002, .003...” instead of “.rar, .r00, .r01....” Unfortunately, since this is not standard usage, it confuses some downloaders. The extraction procedure is the same as for any RAR set - just make sure you start the extraction from the lowest-numbered file. However if this dosn't work then they have been created with HJsplit (a free utility)you can download it from my Tools section HJsplit also allows you to join files so try using it to recompile the split files.

  Since WinRAR's file association won't recognize the non-standard format, the extraction must be manually initiated. WinRAR can't start the process via the context menu, or by double-clicking.

  Put all the files in one directory, launch WinRAR, navigate to the files' folder with the “File” >> “Open Archive” dialog, then click the “Extract To [filename]” button. Extract to the default folder, or wherever you like. Not quite as direct as right-click-on-.rar >> “Extract files...” (But it does work.)

Handling CRC Errors In Downloaded RAR Files Using WinRAR Recovery Records

1. Most posters include an .SFV file or PAR files with their post. Use them to verify files as they are complete on your hard drive, if possible, rather than waiting until all RAR files download. Hopefully, you'll find errors before messages are dropped from your server(s). If PAR files are included with the post, use the small PAR2 file (rather than the SFV) for verification. This can alert you to problems, if the PAR set was improperly created. Or make a copy of the SFV file before you use it, so you have an unaltered “spare” SFV available.
   
   
2. If you get CRC errors reported, try downloading a new copy of the file right away. Try downloading the file again from the original server before requesting a repost. The file might be okay on the server, the error may have occurred en route to you. You may have to refresh your header list before you can re-download. I've had this work frequently, it's worth a try. If you have access to multiple servers try a new copy of the problem file from a different server. If PAR files are available for the post, consider downloading one of the Par volumes, instead of the RAR file. See the PAR File Guide section for more information.
   
   
3. Alternatively, if all RAR files have been downloaded and you get an error reported in WinRAR, try WinRAR's repair function: Open up WinRAR from the start menu, click the repair button, and select the file. It will create a new, corrected version, renamed “_recover.rar”, or something similar. Rename this file to the original filename, and test it with PAR or SFV.
4. WinRAR's repair function can introduce its own set of problems, however. If PARs are available for the post, use them to recover the problem RAR(s). See the section on PAR files for detailed instructions.
   
   
5. If you have trouble extracting from a set of RAR files, the files may not really be corrupt, just renamed. If the post includes PAR files, just use Quickpar or FSRaid (depending on whether they are par 1 files or par2's) and the par program will automatically rename the files. To work out what needs renaming when no PARs are available, make your own SFV file from the 'bad' files and open it and the original SFV in a text editor. If the CRC values match anything in the 'real' SFV then you need to rename the files. If they don't match anything, delete the RAR file and download a new copy of it.
   
   
6. If these attempts don't work - and PARs aren't available - ask for a repost. Since posters are reluctant to repost a whole file, explain your CRC problem and that you've attempted re-download and repair; they may take pity on you. Or one of your fellow downloaders might repost the file. The best way to get a repost of something you want is to post something yourself as posters will appreciate your effort at posting and are far more likly to post your fill files if you show you are not just a leecher. The best way to do this is in the title of what you post add the title of the files you request so that people can see what you have posted and what you need i.e.. "Here Is-Christmas recipes by santa claus - need .r16 or .r18 of New years left overs" If you have never posted before though use a test group to make sure you know what you are doing before you post to a proper group alt.binaries.test for example.

SFV Checker uses CRC-32 technology to check each file and notifies you of any potentially bad, corrupt, incorrect size or missing files to save you hours of downloading only to find you have 1 file missing or the last file has a CRC checksum error.

A download link can be found for both SFV checker and WinRAR in "Tools"

•NFO Files

NFO=iNFOrmation file

Most posts have an associated .TXT file, .NFO file, or 0 (zero) message - READ IT . The poster will spell out their repost policy, the posting schedule (if multi-day), or list the encode's technical details. I cannot over emphasize the importance of reading these information files. Posters go through enormous trouble to provide you with what they do so the very least we can do is read the small text file.

I highly recommend using Damn NFO viewer for viewing NFO files, to make your NFO files look nice.