Differences

This shows you the differences between two versions of the page.

--- arma2:tools:patchpbo [2010/07/16 05:18] – created patchpbo initial page. snakeman
+++ arma2:tools:patchpbo [2024/08/02 11:43] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== PatchPbo ======
+====== ArmA 2 PatchPbo ======
-PatchPbo will patch your existing pbo automatically for specified files, it also deletes any specified files inside a pbo if selected. This util is useful if you want to upgrade / patch a 500mb characters.pbo with just one new model change; no reason to upload that much, when you can just patch in few hundred kilobytes.
+[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]
 Usage:
-<code>
-patchPbo  [-OverrideOption] <PatchPbo[.pbo]> <TargetPbo[.pbo]>
-</code>
+To Merge a pbo
 <code>
-options : -a Arma
+patchpbo OrigPbo[.pbo] [PatchPbo[.pbo]]
-          -A Arma w sha-key (recommended)
-          -APrefixOverride (see note)
-          -r Resistance
-	  -c cwc
-          -e elite
 </code>
-If options not specified, output pbo will be determined by highest order input file. Eg if patch is a CWC and target is an ArmA file, output is ArmA.
+Output will be to OrigPbo, and, original OrigPbo renamed to OrigPbo.old
-Prefix override for ArmA.
+if not specified. OrigPbo_Patch.pbo is expected in same folder
-Unless specifically stated, the engine searches for a suitable prefix name as follows:
+To Create a patch pbo
 <code>
-the name of the patchfile.pbo
+patchPbo  -C OldPbo[.pbo] NewPbo[.pbo] [[PatchPbo[.pbo]]
-the name of the targetfile.pbo
-the name of the outputfile.pbo
 </code>
+Output will be to NewPbo_Patch.pbo if not specified
-Example:
+Examples
 <code>
-patchpbo  MyPatches  APboFile
+patchpbo -c My\Old\GreatAddon My\New\GreatAddon
 </code>
-The output is sent to ApboFile.patched.pbo
+output to GreatAddon_Patch.pob in My\New folder
-NEITHER source files are affected.
-You can, as easily, reverse files to
 <code>
-patchbpo ApboFile MyPatches
+patchpbo MyGreatAddon
 </code>
+MyGreatAddon will be patched with MyGreatAddon_Patch.pbo in same folder
+The intention of patchpbo is to produce a 'no-brainer' difference file between original and new versions of, a pbo. I does NOT use delta comression and as a result can be exceptionally small.
+This difference file can be downloaded by your users INSTEAD of a completely new pbo with dramatically reduced footprint and bandwidth (often as little as 1% the size !!!!)
+Bisig keys are garanteed to be the SAME as if you had supplied the new pbo.
+Thus
+without patchpbo you would normally supply your new pbo AND it's bikey
-Output will be to MyPatches.patched.pbo
+MyGreatAddon.pbo        1meg <<< the NEW pbo
-Patchpbo returns NON zero on any error encountered.
+MyGreatAddon.bikey
-PatchPbo will STRIP resistance format out of pbo files as being entirely redundant.
+WITH patchpbo you supply
-PatchPbo RETAINS the original compression (if any) AND encryption (if any) of the original files.
+MyGreatAddon_Patch.pbo  10k
-DELETING PBO's
+MyGreatAddon.bikey      the same bikey as your new addon
-Simply supply a file of zero (0) length inside the <PatchPboFile>
+Given that your users have a copy of patchpbo (and it's dll) all they have to do is
-If this routine discovers the same name in the target pbo, it will remove it.
+patchpbo MyGreatAddon MyGreatAddon_Patch   <<the ORIGINAL pbo
-**Importantly**, if it does NOT discover one in the target pbo, it considers this to be a genuine attempt to add a zero length file. Such files are often used as version flags.
+Requires DePbo.dll - Check [[http://dev.withsix.com/projects/mikero-pbodll/files|Mikero tools homepage]] in Dev-Heaven.
-Requires DePbo.dll - Check [[http://dev-heaven.net/projects/mikero-pbodll|Mikero tools homepage]] in Dev-Heaven.