fond of a factor? Urn yourself to become remains

[Uncwilly]

Originally Posted by Uncwilly

A nice run of the mill 79 bit factor: 1025757166134493292294953
But, it was found when I poached (not sorry) a stalled P-1 that was in the lowest 25 exponents for FTC.
103547179

Just got me another like it: 312854885986074648542201
78 bits
The old P-1 assignment had been sitting on this low Cat 0 assignment since April 18. Hadn't checked in since then. P-1 is the wild west. No expiry after 30 days, no expiry after not starting in 7 days. (This was in the bottom 25 again).

[Jwb52z]

P-1 found a factor in stage #1, B1=736000.
UID: Jwb52z/Clay, M104224103 has a factor: 457222887848673747662129713 (P-1, B1=736000)

88.563 bits.

[Viliam Furik]

Yay, I found my first top-500 factor. Not even on the list yet, but soon. Albeit only at 495th place.

M2315107 has a 118.475-bit (36-digit) factor: 461896913357939229136479311870224273 (P-1,B1=5000000,B2=505000000)

461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * 3,978,523 * 458,257,259) * 2315107

Also a relatively tight fit in the bounds.

[James Heinrich]

Originally Posted by Viliam Furik

Yay, I found my first top-500 factor

[Viliam Furik]

Originally Posted by Viliam Furik

Yay, I found my first top-500 factor. Not even on the list yet, but soon. Albeit only at 495th place.

M2315107 has a 118.475-bit (36-digit) factor: 461896913357939229136479311870224273 (P-1,B1=5000000,B2=505000000)

461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * 3,978,523 * 458,257,259) * 2315107

Also a relatively tight fit in the bounds.

And the last fun fact to add is that it almost went unnoticed. I have run out of my worktodo, and that triggered the setting in the prime.txt that turned off the PrimeNet usage, so the factor, being found after these events, has not been reported immediately. If I didn't notice that nothing was being reported, I wouldn't have found it, and it would have been buried in the results files until deletion.

Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply .

[firejuggler]

On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'

[Viliam Furik]

Originally Posted by firejuggler

On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'

I believe this would mean I'd have to manually upload every once in a while, and when I would upload, it would, in the process of contacting the PrimeNet, get some assignments back, which I don't want. Or not?

[kruoli]

Originally Posted by Viliam Furik

Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done?

What about manually setting DaysOfWork=0? That way, you'll never get automatic work and the results still will be reported normally.

[Uncwilly]

Originally Posted by Viliam Furik

Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply .

NoMoreWork=1 in prime.txt

[sweety439]

Originally Posted by Jwb52z

P-1 found a factor in stage #2, B1=740000, B2=20264000.
UID: Jwb52z/Clay, M103695649 has a factor: 2004109083829816426995592903 (P-1, B1=740000, B2=20264000).

90.695 bits.

When I add the P-1 method with B1=740000, B2=20264000 for this prime in factordb, it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"

[Viliam Furik]

Originally Posted by Uncwilly

NoMoreWork=1 in prime.txt

That is the setting I am using, but it turns off the PrimeNet connection when out of work. It prints out "Successfully quit GIMPS" in the Comm thread.