http://phuck.me/2011/02/15/567/
Windows: ftp://mersenne.org/gimps/p95v265.zip
Windows 64-bit: ftp://mersenne.org/gimps/p64v265.zip
Mac OS X: ftp://mersenne.org/gimps/Prime95-MacOSX-265.zip
Linux: ftp://mersenne.org/gimps/mprime265.tar.gz
Linux 64-bit: ftp://mersenne.org/gimps/mprime265-linux64.tar.gz
FreeBSD: ftp://mersenne.org/gimps/mprime265-FreeBSD.tar.gz
FreeBSD 64-bit: ftp://mersenne.org/gimps/mprime265-FreeBSD64.tar.gz
Windows NT service: ftp://mersenne.org/gimps/winnt265.zip
Windows NT service 64-bit: ftp://mersenne.org/gimps/win64nt265.zip
看看都更新了啥
另外就是有人在寻简体中文汉化版本,其实我觉得吧……这软件一共就那俩选项,有啥不懂的呢…我个人只是看着英文界面别扭而已,完全不影响使用的哈哈~
1) Pentium 4s and Celerons with L2 cache size of 256K or less choose a length 4M FFT when they could use an FFT between 1600K and 4M in size. Fixed in next release.
2) The on screen message reporting that errors have occurred during the LL test was wrong. The counts for "SUM(INPUTS) != SUM(OUTPUTS)" and "ROUNDOFF > 0.4" were reversed. Fixed in next release.
3) Dual-boot users running a 32-bit and 64-bit executable on the same exponent may experience "Unable to initialize FFT" message. This happens when prime95 writes an FFT size to worktodo.txt and that FFT size is only supported by just one of the two executables. For example, the 2240K FFT length is supported for 64-bit Core 2 but not 32-bit Core 2. Fixed, somewhat inelegantly, in 26.5 — unimplemented FFT lengths are ignored when worktodo.txt is read.
4) Prime95 will sometimes inexplicably unreserve exponents. I think this happens when prime95 incorrectly calculates the CPU speed. Version 26.5 will only use a new slower CPU speed measurement after several slower CPU measurements. Hopefully, this will resolve the unreserve problem caused by a single erroneous CPU speed measurement.
5) Prime95 would lose the how_far_factored and tests_saved information on PRP= lines in worktodo.txt. Fixed in 26.5.
5) Prime95 did not offer an option to delete P-1 save files when a work unit completes. Fixed in 26.5.
6) Prime95 did not fully understand Sandy Bridge CPUID output. Fixed in 26.5.
7) Prime95 did not accurately report the CPU speed. Fixed in 26.5.
At startup, the workers threads do not start up properly until communication with the server completes. If you have a large worktodo.txt file, this will result in wasted CPU time and many "use count" error messages. Fixed in 26.5.
9) Time estimates for trial factoring to 2^79 and above were incorrect. Fixed in 26.5.
2) The on screen message reporting that errors have occurred during the LL test was wrong. The counts for "SUM(INPUTS) != SUM(OUTPUTS)" and "ROUNDOFF > 0.4" were reversed. Fixed in next release.
3) Dual-boot users running a 32-bit and 64-bit executable on the same exponent may experience "Unable to initialize FFT" message. This happens when prime95 writes an FFT size to worktodo.txt and that FFT size is only supported by just one of the two executables. For example, the 2240K FFT length is supported for 64-bit Core 2 but not 32-bit Core 2. Fixed, somewhat inelegantly, in 26.5 — unimplemented FFT lengths are ignored when worktodo.txt is read.
4) Prime95 will sometimes inexplicably unreserve exponents. I think this happens when prime95 incorrectly calculates the CPU speed. Version 26.5 will only use a new slower CPU speed measurement after several slower CPU measurements. Hopefully, this will resolve the unreserve problem caused by a single erroneous CPU speed measurement.
5) Prime95 would lose the how_far_factored and tests_saved information on PRP= lines in worktodo.txt. Fixed in 26.5.
5) Prime95 did not offer an option to delete P-1 save files when a work unit completes. Fixed in 26.5.
6) Prime95 did not fully understand Sandy Bridge CPUID output. Fixed in 26.5.
7) Prime95 did not accurately report the CPU speed. Fixed in 26.5.
At startup, the workers threads do not start up properly until communication with the server completes. If you have a large worktodo.txt file, this will result in wasted CPU time and many "use count" error messages. Fixed in 26.5.9) Time estimates for trial factoring to 2^79 and above were incorrect. Fixed in 26.5.
当然,新装电脑后第一件事儿就是想方设法榨干其性能,无论是cpu,内存…那么为了测试稳定性,这个软件就是必备产品啦!
我的方法是默认电压,找到cpu极限,然后在极限外频下压榨内存,降低延迟,二者统一后把外频适度降低10-20~然后就日常使用啦!
