
              
      ۲  ۲  ۲  ۲  ۲  ۲  ۲   ۲   
      ۲  ۲ ۲  ۲ ۲ ۲ ۲  ۲ ۲ ۲ ۲ ۲ ۲   ۲
        ۲   ۲ ۲ ۲ ۲ ۲   ۲
            ۲  ۲      ۲ ۲ ۲ ۲ ۲   ۲
     ۲۲ ۲ ۲ ۲ ۲ ۲ ۲ ۲ ۲     ۲ ۲ ۲ ۲   
                                                                      sorT8!SAC

    
    ===========================================================================
    BREAKPOiNT Release Packager v1.0 - coded 10/03/1999 by Decline [BREAKPOiNT]
    ===========================================================================
    

    
    1. Introduction
    
    Ok, yet another utility by BREAKPOiNT. The Release Packager compiles
    releases for preing them to the warez-scene. It creates a directory with a 
    name containing release type, application name, group addendum, and the
    files needed for the release inside this directory. Releases are usually
    zipped with filenames beginning with letters identifying the group (like
    bpx for BREAKPOiNT). If a release exceeds a special size, it has to be
    splitted into smaller zip archives which have on most hqs to be smaller
    5 megs. The Packager involves RAR to do this, because zipping only supports
    multivolumes on removable data media. So a RAR multivolume archive is
    created and each volume is packed into a zip. The file_id.diz (which
    contains the disk number) is automatically updated for each volume.
    
    

    2. Requirements
    
    You need WinRar installed to run this program.
    
    

    3. Using the Packager
    
    When you run the program, it opens a tabbed control with three tabs:
   
    3.1. Release Files
       
       Here you can add files to your release. These can be spread all over
       your hard drives. The Packager does not store paths inside your
       release, so no matter from where you collect your files, no folders
       will be created in the zip files. Files required for every release
       are your NFO file and 'file_id.diz'.
      
       
       3.2. Packaging Options
       
       Make selections about packaging your release here. When you click on
       'fill in data' the Packager will open your NFO (it must be in the
       Release File list) and check the release name and make a directory
       name for it. Furthermore, the release type (crack, keygen... is
       scanned).
       Selecting either 'crack only' or 'release' will affect the way, the
       name is build. If you change between these options, you have to hit
       'fill in data' again, to apply changes. Just an example:
       
       crack only: Arlington Browsershield v5.0.Keygen.only-BPX
       release   : Arlington Browsershield v5.0.incl.Keygen-BPX
       
       Multivolume spanning affects the way, dealing with multivolumes. If you
       select automatic here, the Packager will first zip the release, then
       check, wether it exceeds the Volume Size, and repack it with RAR, if
       necessary. By selecting yes/no, you can override this detection saving
       valuable time.
       
       In the boxes single/multiple volume, you can enter names for the created
       archives (zip/rar). These names have to follow the 8.3 naming convention.
       Hitting 'fill in data' puts in default values here. A '#' at the end of
       Zip Filename (multiple volume) indicates, that this char is counted as a
       digit (0-9), when the digit exceeds '9', it restarts at '0' and the
       preceeding character is increased. If you place a '$', the digit is
       counted as letters (a-z).
       
       3.3. Go
       
       Hitting go will start packaging. The Log will keep you up to date on the
       programs actions.
       
       3.4. About
       
       Have a guess ;-)
       
       

    4. Configuring the Packager to fit your needs
    
    When you first launch the Packager (or no packager.ini is created, it will
    pop up with a setup, where you can enter the values for the ini-file). If
    you press ok, all values will be stored, if not, the packager will run with
    default values, but ask for setup again, next time you start it.
    
    
    [TempPath]
    c:\windows\temp
   
      The packager needs a tempary path to work. If you don't specify one, the
      program will use '/temp' inside your windows path.
   

    [OutPath]   
    c:\temp
   
      The output path is the place, where your releases will be created. When
      not specified, the packager will use 'c:\'.
   

    [WinRarPath]
    c:\programme\winrar
   
      This is the place, where WinRar is installed. If you don't specify it,
      the program will look up the WinRar directory in your registry.
   

    [NFOFileName]
    bpx.nfo
   
      This sets the name of you group NFO. Guess the default ;-)
   

    [NFONameOffset]
    829
   
      This is the offset of the release name (in the group NFO). Using the
      offset, the packager can fill in the application name when you hit
      'fill in data'.


    [NFOTypeOffsets]
    1247,1248,1249,1250
   
      Ok, this is the difficult part :), the packager knows 5 types of
      releases: Cracks, Serials, Keygens, Keyfiles and Regkeys. To filter out
      the type of release, the program opens the group NFO, reads the 4 bytes
      at the above entered addresses and glues them to a string. The resulting
      string is then compared with the 5 strings below (NFOTypeValues), to
      retrieve the type of the release.
      The reason, why I made it so complicated is, that some groups mark the
      type of release by using [X] at a special location in the NFO. Just an
      example:
   
      The group NFO looks like this:
    
      [.] CRACK  [.] SERIAL  [X] KEYGEN  [.] KEYFILE  [.] REGKEY
       ^    +     ^     +     ^      +    ^      +     ^     = ..X..
    
      From the resulting string, you can determine the type of release. If you
      use the plain name, it's even simpler:
   
      Release Type: KEYGEN  << K+E+Y+G
   
      [NFOTypeValues]
      CRAC,SERI,KEYG,KEYF,REGK
   
      These 4 char strings define the releases, the order (Crack, Serial...) is
      mandatory. 
   

    [GroupAddendum]
    BPX
   
      The Group Addendum is the string added at the end of the release
      directory.
   
      Arlington Browsershield v5.0.incl.Keygen-BPX 
                                                ^-- Group Addendum
                                             

    [GroupPrefix]
    bpx
   
      The Group Prefix marks zip/rar files at the beginning.
   
      bpxabs50.zip
   
   
    [DIZDiskIndex]
    230,233
   
      The disk index is the offset of the current volume and number of volumes
      (in the 'file_id.diz' file). The volumes are printed as two digits.
   


    5. Final Words
   
    Hi Mom. ;-)
   
    -Decline [BREAKPOiNT], 10/15/1999



    ===========================================================================
    BREAKPOiNT Release Packager v1.0 - coded 10/03/1999 by Decline [BREAKPOiNT]
    ===========================================================================
          
    
              
      ۲  ۲  ۲  ۲  ۲  ۲  ۲   ۲   
      ۲  ۲ ۲  ۲ ۲ ۲ ۲  ۲ ۲ ۲ ۲ ۲ ۲   ۲
        ۲   ۲ ۲ ۲ ۲ ۲   ۲
            ۲  ۲      ۲ ۲ ۲ ۲ ۲   ۲
     ۲۲ ۲ ۲ ۲ ۲ ۲ ۲ ۲ ۲     ۲ ۲ ۲ ۲   
                                                                      sorT8!SAC

    
