[QUOTE=LaurV;294313]Ok, to make you happy, I will take 4000 expos to 68 :P:P[/QUOTE]I see 47 exponents cleared in the last few days.:fusion:
Also, now the 332M range has passed 57.6% of all exponents factored.:smile:

[QUOTE=Uncwilly;294570]I see 47 exponents cleared in the last few days.:fusion:
[/QUOTE]
They are all mine. They should be 59 by now (the last 2 or 3 may not be reported). I queued all [U]unreserved[/U] exponents which were below 70 bits in the range 332M-334M to 70 bits, on 6 copies of mfaktc on 3 gtx580. They are (were, before starting) 6130*6=36780 exponents, most of them from 66 to 70, few of them done to 69 already. I did not reserve them on PrimeNet, as the reservation process is pain in the ass for this amount (I explained before in [URL="http://www.mersenneforum.org/showthread.php?t=16664"]this[/URL] topic). Poaching should not be an issue, one expo takes about a minute (6 minutes, but considering that I have 6 windows), so no big lost if I duplicate something. Whole work would take about 55 days and I might get bored and switch to something else, anyhow I don't know ho long I will have the cards, and I will be in Songkran holiday soon, but I am sure the job will be welcomed as long as it will last... :smile:

Yes, but what if you poach somebody else who has reserved it from PrimeNet but not completed it? (Yes, they won't lose much work, but still.)

[QUOTE=Dubslow;294606]Yes, but what if you poach somebody else who has reserved it from PrimeNet but not completed it? (Yes, they won't lose much work, but still.)[/QUOTE]
I queued the [B][U]unreserved[/U][/B] exponents, please read again my post. There is a checkbox on gimps page which says "show only unreserved exponents". In fact, there was NO RESERVED exponent matching other criterion (factored under 70. I did both queues, they produced exactly the same list, I did both queues for higher bitlevel, they produced different lists). People who do reservation in this range work higher (73-79 bits). And anyhow, all of 100M TF-ers read this thread, that is why I posted. If some of you consider that I am selfish and want to grab all small (easy to find) factors on my plate, then I am happy to split the 36k exponents with you. :yucky:

...my bad :blush:

[QUOTE=Uncwilly;294570]Also, now the 332M range has passed 57.6% of all exponents factored.:smile:[/QUOTE]Now at 57.67% and climbing.
Could I suggest that you start at 332500561 and take them to 69?
Most everything from there to 332999999 is less than 70.

Also, if you want to run some longer exponents, I am not currently working anything above 74. 74 -> 76 should not be too long for an instance of mfactx.

[QUOTE=Uncwilly;294944]Now at 57.67% and climbing.
Could I suggest that you start at 332500561 and take them to 69?
Most everything from there to 332999999 is less than 70.

Also, if you want to run some longer exponents, I am not currently working anything above 74. 74 -> 76 should not be too long for an instance of mfactx.[/QUOTE]
I work in all 332-334M range, so it will come to your range anyhow. However i took your suggestion and modified in all files ",70\r\n" into ",69\r\n", using "replace all" function. I don't know what will be mfaktc reaction when it will find "Factor=N/A,xxxxxxxxx,69,69" (some lines will be like that now) but let's see... Anyhow, works to me, (remember Rick Hunter?), now the work to do is half and the ETA less then a month...

[QUOTE=LaurV;294951]I don't know what will be mfaktc reaction when it will find "Factor=N/A,xxxxxxxxx,69,69"[/QUOTE]It will complain about an invalid assignment and skip the line and keep going doing worktodo until it finds a valid assignment to work on. Eventually mfaktc will run out of work, and worktodo.txt will contain all the assignment lines it didn't recognize or consider valid (it just skips "bad" lines, doesn't erase them).

[QUOTE=LaurV;294951]I work in all 332-334M range, so it will come to your range anyhow. However i took your suggestion and modified in all files ",70\r\n" into ",69\r\n", using "replace all" function. I don't know what will be mfaktc reaction when it will find "Factor=N/A,xxxxxxxxx,69,69" (some lines will be like that now) but let's see... Anyhow, works to me, (remember Rick Hunter?), now the work to do is half and the ETA less then a month...[/QUOTE]Or you could just do another replace of ",69,69" -> ",69,70"

[QUOTE=Uncwilly;294944]Could I suggest that you start at 332500561 and take them to 69?[/QUOTE]

[QUOTE=LaurV;294951]I work in all 332-334M range, so it will come to your range anyhow. However i took your suggestion and modified in all files ",70\r\n" into ",69\r\n", using "replace all" function. [/QUOTE]Oops.:blush:
I meant to say, "start at 332500561 and take them to 69 [U](at least), in a single pass[/U]."
If you are already taking them to 70, that is fine. 332500561 is just the start of the low-hanging section.

I just updated my local copy of the rang out to 332999999 and see the progress. Oops:redface:

If you are taking them to 70, that is cool.:smile:

Someone found a 102 bit factor (6157103818187609775710294086831
) for 332219539 (which previously had been factored to 79 bits.)

So, this hurts our 'effort' number (by ~1,000,000), but helps with the value of the numbers factored out.