Am I doing it wrong?
 

Okay, I was bored and was poking around and I found this on my factors found with TF:
It says I found the factor with P-1, when I actually did it with TF
[code]
[SIZE=2]kracker[/SIZE][SIZE=2] Manual testing [/SIZE][SIZE=2]31321219 [/SIZE][SIZE=2]F-PM1 [/SIZE][SIZE=2]2012-07-01 20:15 [/SIZE][SIZE=2]0.0 [/SIZE][SIZE=2]325236569986535729617[/SIZE][SIZE=2] 1.3727[/SIZE]
[/code]...The others are fine.
[code]
[SIZE=2]kracker[/SIZE][SIZE=2] Manual testing [/SIZE][SIZE=2]3125237 [/SIZE][SIZE=2]NF[/SIZE][SIZE=2] 2012-07-01 18:39[/SIZE][SIZE=2]0.0[/SIZE][SIZE=2] no factor for M31252379 from 2^68 to 2^69 [mfakto 0.11-Win barrett15_75_2][/SIZE][SIZE=2] 1.9129[/SIZE]
[/code]Maybe I'm doing something wrong or this is normal? Thanks :smile:

31,321,219 is not very close to 3,125,237...is it possible the first WAS actually P-1?

Edit: You might consider upgrading to mfaktc 0.17 or 0.18 as well...

No, this is a long- and well- known problem with PrimeNet's results parser. It completely ignores what program reported the factor and guesses the work type based solely on the size of the factor: anything beyond the default P95 TF, which is everything that GPU272 does, is presumed to be P-1.

James is working on fixing it.

[QUOTE=c10ck3r;303822]
Edit: You might consider upgrading to mfaktc 0.17 or 0.18 as well...[/QUOTE]

I run mfakto, not mfaktc :smile:
[QUOTE=Dubslow;303823]No, this is a long- and well- known problem with PrimeNet's results parser. It completely ignores what program reported the factor and guesses the work type based solely on the size of the factor: anything beyond the default P95 TF, which is everything that GPU272 does, is presumed to be P-1.

James is working on fixing it.[/QUOTE]

Ah ok, Thanks!:smile: