[QUOTE=gd_barnes;189260]"misunderestimated"

Hum, interesting. You need to be more specific. Does that mean that you underestimated by more than you expected to underestimate or by less than you expected to underestimate by?

Personally, I usually under underestimate but on occassion, I will over underestimate.


:missingteeth:[/QUOTE]
Hmm, I will procrastinate thinking about that tomorrow.
In fact I will probably only think about it every-other, alternate, second, leap year.

[quote=Lennart;189270]Sorry :smile: Could be that it was i prime there :smile:

Lennart[/quote]
Thanks, I'll get them processed right away.

[quote=Flatlander;189286]Hmm, I will procrastinate thinking about that tomorrow.
In fact I will probably only think about it every-other, alternate, second, leap year.[/quote]

:missingteeth::missingteeth::missingteeth:

217-222 is complete. (Definitely an undermisunderestimation. I think.)

Taking 240K-250K. :smile:

We are well past optimum sieve depth at P=21T for the entire n=250K-400K range. I've now posted the entire sieve file. Feel free to take whatever range you can complete in ~2 weeks.

240K-250K complete, no primes. Results attached.

Reserving 250K-252K.

250K-252K done, no primes. Reserving 252K-254K.

252K-254K done, no primes. Reserving 254K-256K.

254K-256K complete, no primes. Reserving 256K-258K.

256K-258K complete, no primes. Reserving 258K-260K.

258K-260K complete, no primes. Reserving 260K-262K.

260K-262K complete, no primes. Reserving 262K-264K.

Also reserving 264K-274K.

Finally! A prime! After almost 2 months of searching on my dualcore, I pop a 10K range onto my quad and pull out a prime within the first 1K:

[URL="http://primes.utm.edu/primes/page.php?id=92527"]51255*6^264988+1[/URL] is prime!

Additionally, this accomplishes a personal goal for me: I haven't found a top-5000 prime in a [I]really[/I] long time (almost a year now--last one was submitted May 19, 2009), and have been trying for a while now to break that stretch. :smile:

BTW: since my 262K-264K range on my dualcore is below this prime, I'll leave k=51255 in that range. As far as 264K-274K goes, PRPnet automatically removed the k as soon as the prime was found.

Gary, could you update the posted file as soon as you get the chance?