I may be wrong (because I'm basically taking a stab in the dark), but if
that machine has an original Pentium processor, it may be experiencing the
floating point division bug. Anyone else have any ideas?

- Steven Noonan

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Peter Owen
Sent: October 18, 2005 9:17 AM
To: The Great Internet Mersenne Prime Search list
Subject: [Prime] Incorrect factor found

I am trial factoring using Prime95, version 23.8.1, on on old 233 MHz 
machine running Windows 95. On the number I am working on now I am 
getting a series of "Incorrect factor found" errors. Here is an extract 
form the results.txt file.

[Mon Oct 10 02:13:57 2005]
ERROR: Incorrect factor found.
[Mon Oct 10 19:12:39 2005]
ERROR: Incorrect factor found.
[Tue Oct 11 12:11:43 2005]
ERROR: Incorrect factor found.
[Wed Oct 12 05:11:30 2005]
ERROR: Incorrect factor found.
[Wed Oct 12 22:09:54 2005]
ERROR: Incorrect factor found.
[Thu Oct 13 15:08:07 2005]
ERROR: Incorrect factor found.


I am also getting some strange figures in the onscreen progress report, 
as the extract below shows. The percentage complete figure goes down as 
well as up and sometimes gives strange figures such as -1.#J%. The time 
per step also has some crazy numbers, eg 3613650 secs is over a month.


[Oct 13 12:55] Factoring M30740051 to 2^63 is 86.68% complete. Time: 
634.903 sec.
[Oct 13 13:06] Factoring M30740051 to 2^63 is 10.75% complete. Time: Unknown
[Oct 13 13:16] Factoring M30740051 to 2^63 is 86.81% complete. Time: 
3613650.421 sec.
[Oct 13 13:27] Factoring M30740051 to 2^63 is 86.88% complete. Time: 
659.305 sec.
[Oct 13 13:38] Factoring M30740051 to 2^63 is 10.95% complete. Time: Unknown
[Oct 13 13:49] Factoring M30740051 to 2^63 is -1.#J% complete. Time: 
3611713.703 sec.
[Oct 13 13:59] Factoring M30740051 to 2^63 is 87.07% complete. Time: 
630.573 sec.
[Oct 13 14:10] Factoring M30740051 to 2^63 is 87.14% complete. Time: 
641.433 sec.
[Oct 13 14:20] Factoring M30740051 to 2^63 is -1.#J% complete. Time: 
633.152 sec.
[Oct 13 14:31] Factoring M30740051 to 2^63 is 87.27% complete. Time: 
628.722 sec.
[Oct 13 14:41] Factoring M30740051 to 2^63 is 87.33% complete. Time: 
641.846 sec.
[Oct 13 14:52] Factoring M30740051 to 2^63 is 87.40% complete. Time: 
634.827 sec.
[Oct 13 15:03] Factoring M30740051 to 2^63 is 87.47% complete. Time: 
631.016 sec.
ERROR: Incorrect factor found.
Waiting five minutes before restarting.
[Oct 13 15:18] Factoring M30740051 to 2^63 is 87.53% complete. Time: 
910.507 sec.
[Oct 13 15:28] Factoring M30740051 to 2^63 is 87.60% complete. Time: 
631.078 sec.
[Oct 13 15:39] Factoring M30740051 to 2^63 is 99.99% complete. Time: 
645.657 sec.
[Oct 13 15:50] Factoring M30740051 to 2^63 is 87.73% complete. Time: 
650.022 sec.
[Oct 13 16:00] Factoring M30740051 to 2^63 is 99.99% complete. Time: 
635.967 sec.
[Oct 13 16:11) Factoring M30740051 to 2^63 is 87.86% complete. Time: 
636.825 sec.


Does anyone have an explanation for this strange behaviour?

Peter

-- 
_________________________________
Peter Owen
Liverpool UK
mailto:[EMAIL PROTECTED]
_______________________________________________
Prime mailing list
[email protected]
http://hogranch.com/mailman/listinfo/prime


_______________________________________________
Prime mailing list
[email protected]
http://hogranch.com/mailman/listinfo/prime

Reply via email to