Is there any tricks on creating an account on PrimeNet V5? I keep getting a "[COLOR="Red"]Please review the Terms and Conditions and check the acceptance check box[/COLOR]." message and the password boxes are marked with a red star. I've tried different multiple passwords without success.

harlee: Check for javascript. Also check that the min number of characters are present in the password.

[QUOTE=harlee;119195]Is there any tricks on creating an account on PrimeNet V5? I keep getting a "[COLOR="Red"]Please review the Terms and Conditions and check the acceptance check box[/COLOR]." message[/QUOTE]

Bug fixed. Please try again.

[QUOTE=Prime95;119201]Bug fixed. Please try again.[/QUOTE]

Prime95 - Thanks, I was able to create an account.

[QUOTE=James Heinrich;119116]When I start Prime95 the ECM thread usually gets to the check-how-much-RAM-it-can-claim stage first, and allocates anywhere from 250-750MB for itself. If I have high RAM settings (say 2GB for Prime95) there's plenty left over for the P-1 thread to do something useful with, and it does. However, once the ECM thread finishes its stage2, the P-1 thread restarts with new settings and grabs all available RAM for itself and then the ECM thread sits idle .[/QUOTE]

Does prime.txt have this line in it?

DelayStage2ThreadCount=2

[QUOTE=Prime95;119203]Does prime.txt have this line in it?
DelayStage2ThreadCount=2[/QUOTE]No, doesn't have that at all (of any value).
Should it?

[QUOTE=James Heinrich;119205]No, doesn't have that at all (of any value).
Should it?[/QUOTE]

Try it. By default, only half of the worker threads are allowed to use extra memory. You were getting both workers using extra memory only because the ECM job wasn't using all of the available extra memory.

This default was chosen because if you were doing all ECM, then each worker would essentially alternate using the maximum memory.

Your situation reveals that some alternative options and/or defaults may be desirable. I need to think on this some more.

[QUOTE=James Heinrich;119081]The server assigned me a couple LL tests yesterday. One of them's done already (well, sortof):The other's still doing P-1, and I hope it finds a factor too, since otherwise I won't be done LL until 09-Apr-2007 :yawn:[/QUOTE]P-1 is finished ("assuming no factors below 2^66 and 2 primality tests saved if a factor found"), and now it's doing TF to 2^67... :surprised
Shouldn't it do TF [i]first[/i], then proceed to P-1? At least, that's what it used to do in v24.x -- is this new behavior intentional?

[QUOTE=Prime95;119211]This default was chosen because if you were doing all ECM, then each worker would essentially alternate using the maximum memory. Your situation reveals that some alternative options and/or defaults may be desirable. I need to think on this some more.[/QUOTE]When doing a single worktype (whether ECM or P-1 where stage1 and stage2 take similar amounts of time and one thread can continue onto another stage1 if no RAM is available for stage2, then the current default is sensible. Where it breaks is if a thread gets to the point where it cannot do any more work until it has some RAM available. This could be remedied in several ways, including (but not limited to):
* if idle thread is detected, (temporarily) allow (all?) threads to share RAM
* if idle thread is detected, allow it to do some work on another thread's queued-up worktodo that doesn't need a lot of RAM. (I previously proposed having a single pool of worktodo that is dynamically assigned to available worker threads, rather than hardcoding the assignments to specific threads; that would work nicely here.)

[QUOTE=James Heinrich;119217]Shouldn't it do TF [i]first[/i], then proceed to P-1? At least, that's what it used to do in v24.x -- is this new behavior intentional?[/QUOTE]

This is intentional. GIMPS will now do P-1 before the last two factoring levels. This should increase GIMPS throughput by a miniscule amount.

[quote=hoopmanjh;118752]I don't know if this is a program issue or a user issue . . . I got through phase 1 successfully in 25.5, but now I can't run phase 2 -- both worker threads keep saying "Other worker threads are using lots of memory now" and then try to restart with new memory settings. If I limit myself to 1 thread, then it works just fine, but as soon as I go back to 2, everything stops again. I'm running an E6600 Core2 Duo (2.4GHz) with 2GB of RAM; what would be realistic daytime and nighttime memory settings?
Thanks!
Joe[/quote]
And another update: Once one of the threads moved to primality testing, the system was able to run both threads simultaneously again. Unfortunately, I don't think I have the .txt files any more that were being requested.