mersenneforum.org Prime95: INI_FILE settings limited to 80 characters
 Register FAQ Search Today's Posts Mark Forums Read

 2021-03-10, 18:53 #1 sp00n   Dec 2020 7 Posts Prime95: INI_FILE settings limited to 80 characters This is taken from the source file for version 30.3b6. In the common.c file the various INI settings are defined as e.g. Code: IniGetString (INI_FILE, "local.ini", LOCALINI_FILE, 80, LOCALINI_FILE); IniGetString (INI_FILE, "worktodo.ini", WORKTODO_FILE, 80, WORKTODO_FILE); IniGetString (INI_FILE, "results.txt", RESFILE, 80, RESFILE); which limits the value to 80 characters. I was trying to write the log file to a different directory than where the binary file and the prime.txt/local.txt are, and if you're using a longer file name (e.g. by adding the date and time) or a longer directory name, these 80 characters can be exceeded, which in turn cuts off the name of the file that is generated in the provided directory. Example: Directory of the prime95.exe: D:\Benchmarking\Prime95\30.3b6\binaries\ Directory of results.txt file: D:\Benchmarking\Prime95\30.3b6\logs\ Name of results.txt: Prime95_results_2020-12-31_23_59_59_FFT_248-8192.txt Expected file name: D:\Benchmarking\Prime95\30.3b6\logs\Prime95_results_2020-12-31_23_59_59_FFT_248-8192.txt Actual file name (cut off after 80 characters): D:\Benchmarking\Prime95\30.3b6\logs\Prime95_results_2020-12-31_23_59_59_FFT_248 Is there any particular reason why there's a limit to 80 characters and not to ~260 characters like Windows supports? I seem to have been able to work around this by setting the WorkingDir= directive to one level above the directory where the .exe is located then setting prime.ini=, local.ini= and results.txt= as a relative path from that directory. It appears to be working, but it seems unnecessarily complicated. These are the resulting entries in the prime.txt, of course, they're only examples. (I also find it a bit weird that you can set the file name for the prime.ini/txt in that exact prime.txt.) Code: WorkingDir=D:\Benchmarking\Prime95\30.3b6 prime.ini=binaries\prime.txt local.ini=binaries\local.txt results.txt=logs\Prime95_results_2020-12-31_23_59_59_FFT_248-8192.txt So I'd suggest to change the 80 character limit to something higher in a future release so that these kind of workarounds aren't required anymore. (Also, for more than just stress testing, you'd probably have to modify the other settings as documented in undoc.txt to the relative path as well.) Last fiddled with by sp00n on 2021-03-10 at 18:53
 2021-03-10, 21:55 #2 ixfd64 Bemusing Prompter     "Danny" Dec 2002 California 19·127 Posts The 80-character limit is a relic of a bygone era when most computer screens could not display more than 80 columns. I agree it's no longer relevant in this day and age. Last fiddled with by ixfd64 on 2021-03-11 at 01:50
 2021-03-10, 22:58 #3 Prime95 P90 years forever!     Aug 2002 Yeehaw, FL 167268 Posts Prime95 is a relic, There are 8.3 limits in some of the code. I'll boost the limits you mentioned in 30.5.
2021-03-11, 01:46   #4
kriesel

"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

16AB16 Posts

Quote:
 Originally Posted by Prime95 Prime95 is a relic, There are 8.3 limits in some of the code. I'll boost the limits you mentioned in 30.5.
It would be great if the obfuscated-exponent filename consequences of that residual 8.3-ness went away.
Quick, what exponent does file pA852841.residues relate to? pA851779.proof?

2021-03-11, 15:25   #5
LaurV
Romulan Interpreter

"name field"
Jun 2011
Thailand

263B16 Posts

Quote:
 Originally Posted by kriesel Quick, what exponent does file pA852841.residues relate to? pA851779.proof?
Plus one for that! Well spotted! May George be healthy and have free time in the future, so he fix all those relics...

Last fiddled with by LaurV on 2021-03-11 at 15:26

 2021-03-11, 16:08 #6 kriesel     "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 16AB16 Posts Also p8U82187 and related .bu* (dated today and yesterday, produced by prime95 v30.4b9 LL DC of M55882187) There are p(clear 9 digit exponent) files produced in the same folder during the same time frame, from other work types from other workers on that instance. pA853833.* from PRP-CF of M10853833 (and more examples like the above) Last fiddled with by kriesel on 2021-03-11 at 16:09
2021-03-11, 16:30   #7
chalsall
If I May

"Chris Halsall"
Sep 2002

7·1,423 Posts

Quote:
 Originally Posted by LaurV Plus one for that! Well spotted! May George be healthy and have free time in the future, so he fix all those relics...
+1!

Thanks, George!

2021-03-11, 16:53   #8
sp00n

Dec 2020

7 Posts

Quote:
 Originally Posted by Prime95 Prime95 is a relic, There are 8.3 limits in some of the code. I'll boost the limits you mentioned in 30.5.
Great, thanks.

2021-03-12, 04:45   #9
LaurV
Romulan Interpreter

"name field"
Jun 2011
Thailand

9,787 Posts

Quote:
 Originally Posted by kriesel Also p8U82187 of M55882187 pA853833.* from PRP-CF of M10853833 (and more examples like the above)
To be fair, we know (and always knew) how to decode those, there is some explanation in those .txt files sent with P95, which no one reads them ever. But it would be indeed wonderful if George fix the checkpoint names and temp file names, to something more clear and palatable, considering the new invention called "long file names".
We wouldn't mind zero-filled names to 9 positions, so we can sort them properly in the folder when there are different numbers of digits (edit: like for example M098765432_blah_blah.bkp, to be sorted before M123456789_blah_blah.bkp, and not M98765432_blah_blah.bkp).

Last fiddled with by LaurV on 2021-03-12 at 04:51

 2021-03-12, 17:25 #10 kriesel     "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 132538 Posts The readme.txt file list section seems to indicate they'll have alpha first char, numeric ASCII for exponent. But the 7 N's don't fit even current DC exponents. Code: cNNNNNNN,cNNNNNNN.buN Intermediate files produced during certification runs. pNNNNNNN,pNNNNNNN.buN Intermediate files produced by prime95.exe to resume computation where it left off. pNNNNNNN.residues Large intermediate file produced during PRP test for constructing a PRP proof. pNNNNNNN.proof PRP proof file. eNNNNNNN,eNNNNNNN.buN Intermediate files produced during ECM factoring. fNNNNNNN,fNNNNNNN.buN Intermediate files produced during trial factoring. mNNNNNNN,mNNNNNNN.buN Intermediate files produced during P-1 factoring. I didn't see an explanation for the leading or embedded alpha characters. Nothing relevant to that found searching readme, whatsnew, or undoc, for "file" or "8.3". Where's it to be found? Last fiddled with by kriesel on 2021-03-12 at 17:26
2021-03-12, 20:45   #11
Prime95
P90 years forever!

Aug 2002
Yeehaw, FL

1DD616 Posts

Quote:
 Originally Posted by kriesel Where's it to be found?
The usual answer: dig into C code.

 Similar Threads Thread Thread Starter Forum Replies Last Post Bommer1 Software 3 2019-11-25 13:05 evanh Software 3 2017-12-04 15:18 rharmz Software 1 2014-05-20 07:36 fox_mccloud_123 Information & Answers 6 2013-05-07 21:12 jasonp Factoring 8 2006-08-05 21:06

All times are UTC. The time now is 02:05.

Mon Oct 25 02:05:25 UTC 2021 up 93 days, 20:34, 0 users, load averages: 0.92, 0.89, 1.00