Isto tako i ja A totalno si u pravu za LinX. Jeste odlichan program, ali ima bagove, no verujem da ce ga ispeglati. Sa druge strane, LinX zna da zagreje CPU do te mere da ni jedan druga aplikacija ili pak rendering ne moze. Mada, jedno je sigurno! Kada LinX prodje "glavu na panj" mozesh da stavish da ti je CPU stabilanPa osetno manje se koristi od pojave LinX-a, ali je i dalje jedan od boljih programa, pogotovo sto nema nekih bagova kao konkurent LinX
Svakako korisni linkovi.
Kakav si pravi prajmonostalgicharLepo podgreva novi prajmic, small fft's jos par stepeni pa kao linx. Meni je ovo omiljeni test tool.
Ni ovo ne mora da znaci, moze da ti pukne neki drajver u sistemu, tipa zvucna karta ili modem, nebitno sta i softver za testiranje ce to da vidi kao gresku i prijavice istu...Ja sam na dva treda terao LinX, a na druga dva Prajm. E ako to ne zakuje posle 12 sati drndanja, znas da ti je sistem stabilan
Igrao sam 16h sati neprekidno CSa ( ne pitaj kako ) , zaspao sam izmedju 2 runde i spavao 15 sati.Ima dugme i da se ugasi monitor.
Probaj 24h da se igras, nije tesko, samo treba dobra igra.
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.
8) 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.