On Sunday 30 January 2005 01:26, Walt Mankowski wrote: > I finished double-checking exponent 13386931 earlier today. When I > checked prime.log just now, I saw the following message: > > [Sat Jan 29 14:12:31 2005 - ver 23.9] > Sending result to server for exponent 13386931 > ERROR 3: Exponent not assigned to this computer. > Sending text message to server: > UID: waltman/ito, M13386931 is not prime. Res64: E450101FAF5AB7D1. WZ2: > 43B2A23A,309435,00000000 > > The exponent is gone from worktodo.ini. It is, however, still listed > on my primenet_report page, which says it still has 0.9 days to go. > > Anyone know what might have happened?
This sort of thing does happen; there are two reasons which seem to be more or less common: 1) You "inherited" this assignment from someone else who stopped work for long enough to convince the server that they had abandoned work. However they carried on, finished before you did and checked the result in. 2) PrimeNet lost track of the exponent. This may happen sometimes when the database is updated manually. (1) is much more likely as PrimeNet database problems will likely result in the assignment being removed from your PrimeNet report page. > I'd hate to think I just wasted > the last 2 months of work. A few triplechecks (or early doublechecks) do no harm. In fact there are a considerable number of exponents which are being deliberately triplechecked (outside PrimeNet) - the point being that it's better if someone else runs the doublecheck. Your work is not wasted provided it's reported. If your PrimeNet status page does not show the assignment as completed, extract the line with the final residue from results.txt & mail it to George Woltman ([EMAIL PROTECTED]) Regards Brian Beesley _______________________________________________ Prime mailing list [email protected] http://hogranch.com/mailman/listinfo/prime
