[QUOTE=preda;624125]
- when mprime runs out of work (empties worktodo.txt), it sets UsePrimenet=0 and NoMoreWork=0 (which wore set to UsePrimenet=1 and NoMoreWork=1 initially). This looks like a bug.
- it would be great if prime.txt would never be written by mprime. The user writes prime.txt, mprime *only* reads it.

If for some reason some options in prime.txt need to be written by the software, thouse are the ones that should be extracted from prime.txt to a separate file, such that prime.txt becomes read-only.[/QUOTE]

The best way to do this is "DaysOfWork=0"

NoMoreWork=1 really means "Quit GIMPS after current assignments complete"

[QUOTE=Prime95;626012]NoMoreWork=1 really means "Quit GIMPS after current assignments complete"[/QUOTE]

In 30.11, NoMoreWork will be renamed QuitGIMPS.
The mprime menus will allow setting "Days of work to queue up" to zero. The Windows dialog box already allowed this.

What about:
MaxExponents=0

that seems to work ok as well.

[QUOTE=ATH;626014]What about:
MaxExponents=0

that seems to work ok as well.[/QUOTE]

I suppose that would work as well.

So you will just merge two files into one? And all content of one file copy to another. No more no less? :)

[QUOTE=pepi37;626017]So you will just merge two files into one? And all content of one file copy to another. No more no less? :)[/QUOTE]

When you first run 30.11, the two files will be merged into one and local.txt deleted.
A few options are renamed for clarity. Some options are moved to sections like [Internals] or [PrimeNet], also for clarity.

Again, all automatic.

[QUOTE=Prime95;626019]When you first run 30.11, the two files will be merged into one and local.txt deleted.
A few options are renamed for clarity. Some options are moved to sections like [Internals] or [PrimeNet], also for clarity.

Again, all automatic.[/QUOTE]

Only downside I see here is that it's a one-way trip; downgrades won't know what to do with the combined file. I don't plan on downgrading, but it's worth considering if there's some reason that someone might be inclined to try.

Bugs motivating version revert are one foreseeable reason. User preference is another.
So:

copy prime.txt was.prime.txt
copy local.txt was.local.txt
merge files

There seems to be something I didn't get here: what are you trying to accomplish using DaysOfWork=0 or MaxExponents=0 ? What is the intended behavior when exhausting worktodo? I think it should just be a normal stop (and automatic restart if new work is received through Primenet).

This might not be the right place to ask, but is there an option to not receive work from the server, but still submit results automatically? I ask because my current setup racks up several (unwanted) assignments when the work I queue gets low, but I have found in the past that setting days of work to queue lower sometimes removes work that I add manually.

[QUOTE=Denial140;626066]This might not be the right place to ask, but is there an option to not receive work from the server, but still submit results automatically? I ask because my current setup racks up several (unwanted) assignments when the work I queue gets low, but I have found in the past that setting days of work to queue lower sometimes removes work that I add manually.[/QUOTE]

Set DaysOfWork=0 and UnreserveDays=999999, both in prime.txt.

The first tells the client to not fetch more work from PrimeNet. The second prevents it from unreserving assignments. Sometimes the computer will be busy doing something else when mprime/Prime95 calculates the system throughput which causes it to unreserve exponents.