View Single Post
Old 2020-06-15, 18:59   #5
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

23×421 Posts
Default

Quote:
Originally Posted by bsquared View Post
In my mind, the .ini file should be used to set *permanent* parameters. Things that you always need (for example the ecm path, ggnfs binary folder, and ecm pretesting preferences). Anything in the .ini file can be overridden on the command line. For me, threads is something I frequently change, depending on what I'm trying to do or what networked system I'm currently running on, so I always set that from the command line. Just my preference: customize the .ini as you see fit. The new .ini is simply meant to document the possible options.
I just remembered something else to bring up, but will have to wait for another tune session to show an example. I get a repetitive skewed error message with the new .ini file. All seems to run fine afterward, though. This was with and without removing the existing tune data. I suppose it might have to do with the threads edit. I'll post an example later, unless it never shows again.
EdH is offline   Reply With Quote