Suggestions for future enhancements

[Reboot It]

George:

Would it be possible to add something in Prime.ini that would make Prime95 stop processing an LL test (first time or double-check) on the current exponent when the process got to the specified percentage?

For example, if it said something like:

[code:1]StopTestPercent=99[/code:1]

the program would write a save file, leave the entry in the WorkToDo.ini file but continue to process the next exponent from the list of work.

[Axel Fox]

Hmmm, what would be the point of that ?

[nomadicus]

Might be a way to organize machines not connected to the internet and avoid manual checkins. Then sneakernet the data to one a machine that completes the last % and uses primenet to report in. ?

[apocalypse]

One small change I would request is for the Status dialog to display the estimated completion time of the last element in the worktodo.ini file on the last line, if there are more entries than the dialog currently reports.

Not of much use to most people, but it would help the LMH'ers who run thousands of TF tests at a time.

[dsouza123]

Another small change, the Status to show the starting bit size for TF just like the worktodo.ini M23123456,57 or enable showing it with a line in Prime.ini or Local.ini.

StatusShowBitStart=1

[dsouza123]

Another small change for the results.txt file to show the starting bit depth for TF. Or enable it with a line in Prime.ini or Local.ini

ResultShowBitStart=1

[Reboot It]

Originally Posted by nomadicus

Might be a way to organize machines not connected to the internet and avoid manual checkins. Then sneakernet the data to one a machine that completes the last % and uses primenet to report in. ?

Spot on! That's exactly what I had in mind.

[nomadicus]

Originally Posted by Reboot It

Spot on! That's exactly what I had in mind.

Great (well, mine is questionable :)) minds think alike. I've been thinking about asking for this feature for some time . . . just don't critical mass in the number of my computers.
Great suggestion!!!

[hyh1048576]

I think the expected completion date should be more precise. ;)

For example, my is usually 10 days earlier than the date I clear the exponents.(My current exponent was assigned to me on July 21st, the expected completion date was Sept. 1st at that time, but now it says Sept. 10th ;) ). We should realise that Prime95 is not always take 100% CPU :( )

[smh]

Originally Posted by Reboot It

Spot on! That's exactly what I had in mind.

But why stop shortly before the exponent is completed? The results are stored on the local pc until they are submitted to primenet. Just stop the client on that pc, move the whole directory to another pc, start the client and submit to primnet. Let it get new exponents, stop the client and move it back to the original pc.

BTW, there is an option in undoc.txt to create a save file every XXXXX iterations.

[Reboot It]

The results are stored on the local pc until they are submitted to primenet.

If there is no internet access it makes it difficult. Also, personally, I have never enjoyed moving prime.spl files around either, as I can't see what's in them to check what's going on!

Just stop the client on that pc, move the whole directory to another pc, start the client and submit to primnet. Let it get new exponents, stop the client and move it back to the original pc.

Compare the number of operations there with "copy the save file, delete the WorkToDo.ini line that relates to it and stop/start the client". You only have to visit a PC once. These things can save a lot of time in some settings (such as remote machines).

BTW, there is an option in undoc.txt to create a save file every XXXXX iterations.

Thanks for the reminder (as I hadn't thought of that in connection with this). But to be able to stop just before completion (99%, 99.8% or whatever) would mean loads of these save files to have a file close to that point.