What was pulled out again? The prime cofactor of the algebraic factor (2^6979-1)/(2^997-1), a.k.a. Phi[SUB]7[/SUB](2^997)? It's there.

Still getting a C41715 here both from yafu-x64's "factor" command and also by running the ecm command also with yafu-x64.

This time having the output to the screen (or monitor) instead of a file.

Took a bit of time to get the

=============================================
ecm: 0/1 curves on C41715, B1=11K, B2=gmp-ecm default

visible.

[QUOTE=storflyt32;385591]Still getting a C41715 here both from yafu-x64's "factor" command and also by running the ecm command also with yafu-x64.

This time having the output to the screen (or monitor) instead of a file.

Took a bit of time to get the

=============================================
ecm: 0/1 curves on C41715, B1=11K, B2=gmp-ecm default

visible.[/QUOTE]

I assume you are still going on about [URL="http://www.mersenneforum.org/showthread.php?t=19772"]this[/URL]. Just because you can print it does not make it so.

I am sorry that yafu does not work on every conceivable input, but the fact remains that it was not designed to work on numbers like this. Why would you insist that yafu is right when every other piece of software that *was* designed for numbers like this disagree with it?

Do not know where to post this.

[url]http://factordb.com/index.php?id=1100000000785525326[/url]

Lying at the bottom of my checkfacts.txt file, the number fits into the factorize line in the Factor Database.

Just clicking the Factorize button, it first became "U" for unknown.

Clicking the button again and I was told it was a PRP3759.

This time it apparently was not because of me.

Whose responsibility is to update what and where and if a given number turns out to be a quite large one,
who should be credited with the find or discovery?

[QUOTE=storflyt32;404695]Do not know where to post this.

[URL]http://factordb.com/index.php?id=1100000000785525326[/URL]

Lying at the bottom of my checkfacts.txt file, the number fits into the factorize line in the Factor Database.

Just clicking the Factorize button, it first became "U" for unknown.

Clicking the button again and I was told it was a PRP3759.

This time it apparently was not because of me.

Whose responsibility is to update what and where and if a given number turns out to be a quite large one,
who should be credited with the find or discovery?[/QUOTE]
The factordb server probably ran a PRP check.
On the status page, one core of the 2600k is dedicated to do this:
"Checking the smallest number with status unknown <20000 digits"

:whistle:

[url]http://factordb.com/index.php?id=1100000000792308300[/url]

The remaining C103 is a very difficult one.

Running it using ecm only could possibly work, but would probably take a very long time, depending on the number of curves which are being selected.

Most likely the 9704 curves being used by the Yafu software is not enough for this number.

Therefore a larger number of curves are needed, increasing the number it takes to complete.

You don't have an hour to factor this yourself?

[QUOTE=jasonp;405927]You don't have an hour to factor this yourself?[/QUOTE]Actually, a little more than an hour, but then I couldn't run my full 6 cores becuase of the ambient temp....

I notice the factorization of the remaining C103.

Thank you very much for doing that.

Appreciated.

Here is another interesting one. I have recently stumbled onto this C81 ([URL="http://factordb.com/index.php?id=1100000000792511003"]link[/URL]). This will be a difficult one to crack. In fact, it will likely take longer than the age of the universe to factor. I have already started trial factoring with my pocket calculator, and will let you all know of any results.