Downloads:

4,253

Downloads of v 28.9.20161009:

670

Last Update:

09 Oct 2016

Package Maintainer(s):

Software Author(s):

  • George Woltman

Tags:

prime95 stress test burn-in portable

Prime95 (Portable)

This is not the latest version of Prime95 (Portable) available.

  • 1
  • 2
  • 3

28.9.20161009 | Updated: 09 Oct 2016

Downloads:

4,253

Downloads of v 28.9.20161009:

670

Maintainer(s):

Software Author(s):

  • George Woltman

  • 1
  • 2
  • 3
Prime95 (Portable) 28.9.20161009

This is not the latest version of Prime95 (Portable) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Prime95 (Portable), run the following command from the command line or from PowerShell:

>

To upgrade Prime95 (Portable), run the following command from the command line or from PowerShell:

>

To uninstall Prime95 (Portable), run the following command from the command line or from PowerShell:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade prime95.portable -y --source="'INTERNAL REPO URL'" --version="'28.9.20161009'" [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 prime95.portable -y --source="'INTERNAL REPO URL'" --version="'28.9.20161009'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install prime95.portable
  win_chocolatey:
    name: prime95.portable
    version: '28.9.20161009'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'prime95.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '28.9.20161009'
end

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


cChocoPackageInstaller prime95.portable
{
    Name     = "prime95.portable"
    Version  = "28.9.20161009"
    Source   = "INTERNAL REPO URL"
}

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


package { 'prime95.portable':
  ensure   => '28.9.20161009',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

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 by moderator gep13 on 16 Jul 2017.

Description

Screenshot of Prime95

CPU Stress / Torture Testing

Prime95 has been a popular choice for stress / torture testing a CPU since it's introduction, especially with overclockers and system builders. Since the software makes heavy use of the processor's integer and floating point instructions, it feeds the processor a consistent and verifiable workload to test the stability of the CPU and the L1/L2/L3 processor cache. Additionally, it uses all of the cores of a multi-CPU / multi-core system to ensure a high-load stress test environment.

From the most recent "stress.txt" file included in the download:

Today's computers are not perfect. Even brand new systems from major manufacturers can have hidden flaws. If any of several key components such as CPU, memory, cooling, etc. are not up to spec, it can lead to incorrect calculations and/or unexplained system crashes.

Overclocking is the practice of increasing the speed of the CPU and/or memory to make a machine faster at little cost. Typically, overclocking involves pushing a machine past its limits and then backing off just a little bit.

For these reasons, both non-overclockers and overclockers need programs that test the stability of their computers. This is done by running programs that put a heavy load on the computer. Though not originally designed for this purpose, this program is one of a few programs that are excellent at stress testing a computer.

The Prime95 Wikipedia page has an excellent overview on using Prime95 to test your system and ensure it is working properly. The tips presented there should be helpful regarding how long to run the torture test and provide a solid guideline on how long to run the Prime95 stress test.

Performing a stress test is simple:

  1. Download the software and unzip the files to your desired location. (Chocolatey does that for you!)
  2. Run the Prime95 executable and select "Just Stress Testing" when asked.
  3. The default options are sufficient to do a well balanced stress test on the system.

tools\chocolateyuninstall.ps1
$packageName= 'prime95.portable'
$ShortcutName = 'Prime95'

if((get-process "prime95" -ea SilentlyContinue) -eq $Null){ 
        Write-Host  "prime95 not running. (Good!)" 
}
else{ 
    Write-Host  "Stopping Prime95..."
    Stop-Process -processname "prime95"
    Start-Sleep -s 3
 }

remove-item "$env:Public\Desktop\$ShortcutName.lnk" -Force -ErrorAction 'SilentlyContinue'
remove-item "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\$ShortcutName.lnk" -Force -ErrorAction 'SilentlyContinue'
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'
$packageName  = 'prime95.portable' 
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url          = 'http://www.mersenne.org/ftp_root/gimps/p95v289.win32.zip'
$url64        = 'http://www.mersenne.org/ftp_root/gimps/p95v289.win64.zip'
$ExeFile      = 'prime95.exe'
$ShortcutName = 'Prime95'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'ZIP' 
  url           = $url
  url64         = $url64
  checksum      = 'F8C58AB55A2578B243711D3CB1640F62C501AC515E9DC076009AF7E6525D66A4'
  checksumType  = 'sha256' 
  checksum64    = '6DEAA2C6C07FBF0E4259A66ABF56A5E7A69A7623D5AA0803D567D7A75CD513E8'
  checksumType64= 'sha256'  
}

Install-ChocolateyZipPackage @packageArgs

Install-ChocolateyShortcut -shortcutFilePath "$env:Public\Desktop\$ShortcutName.lnk" -targetPath "$env:ChocolateyInstall\lib\$packageName\tools\$ExeFile"
Install-ChocolateyShortcut -shortcutFilePath "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\$ShortcutName.lnk" -targetPath "$toolsDir\$ExeFile" -WorkingDirectory "$toolsDir"

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
Prime95 (Portable) 29.4.5 2087 Sunday, November 26, 2017 Approved
Prime95 (Portable) 28.9.20161009 670 Sunday, October 9, 2016 Approved
Prime95 (Portable) 28.9 410 Sunday, August 21, 2016 Approved
Prime95 (Portable) 28.7 428 Tuesday, April 19, 2016 Approved

added checksum


This package has no dependencies.

Discussion for the Prime95 (Portable) Package

Ground Rules:

  • This discussion is only about Prime95 (Portable) and the Prime95 (Portable) 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 Prime95 (Portable), 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