Downloads:

6,650

Downloads of v 1.3.0.501:

287

Last Update:

25 Jun 2019

Package Maintainer(s):

Software Author(s):

  • Yukata Sawada

Tags:

multipar parchive NG data protect

MultiPar

1.3.0.501 | Updated: 25 Jun 2019

Downloads:

6,650

Downloads of v 1.3.0.501:

287

Maintainer(s):

Software Author(s):

  • Yukata Sawada

Tags:

multipar parchive NG data protect

MultiPar 1.3.0.501

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Failed

Details

To install MultiPar, run the following command from the command line or from PowerShell:

>

To upgrade MultiPar, run the following command from the command line or from PowerShell:

>

To uninstall MultiPar, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade multipar -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade multipar -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure multipar installed
  win_chocolatey:
    name: multipar
    state: present
    version: 1.3.0.501
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'multipar' do
  action    :install
  version  '1.3.0.501'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: multipar,
    Version: 1.3.0.501,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller multipar
{
   Name     = 'multipar'
   Ensure   = 'Present'
   Version  = '1.3.0.501'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'multipar':
  provider => 'chocolatey',
  ensure   => '1.3.0.501',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install multipar version="1.3.0.501" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 29 Jul 2019.

Description

MultiPar can do file verification, error detection, correction and recovery to protect your files and folders from deletion, copy errors, download errors, software errors, hardware errors, virus infection, malicious tampering, and all other forms of data corruption.

MultiPar was made as an alternative to QuickPar. While it looks like a multi-lingual version of QuickPar, there are some good features; Unicode characters, directory-tree, faster repairing, smaller recovery files, batch scripting, and so on.

Features

MultiPar supports both PAR 1.0 and PAR 2.0 specifications.

See the Parchive project for details of Parchive.

screenshot

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
MultiPar 1.3.0.501 287 Tuesday, June 25, 2019 Approved
MultiPar 1.3.0.500 154 Friday, May 24, 2019 Approved
MultiPar 1.3.0.5 107 Saturday, May 11, 2019 Approved
MultiPar 1.3.0.4 89 Saturday, April 20, 2019 Approved
MultiPar 1.2.9.9 923 Wednesday, December 21, 2016 Approved
MultiPar 1.2.9.8 287 Tuesday, November 15, 2016 Approved
MultiPar 1.2.9.7 312 Thursday, October 20, 2016 Approved
MultiPar 1.2.9.6 326 Saturday, July 30, 2016 Approved
MultiPar 1.2.9.5 246 Wednesday, July 20, 2016 Approved
Discussion for the MultiPar Package

Ground Rules:

  • This discussion is only about MultiPar and the MultiPar package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or MultiPar, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus