I would still suggest, however, that this line of output with the ETA should be included even at verbosity level 0, there's already a fair amount of output from NFS sieving so the extra line with ETA every now and then wouldn't really make things much longer (but contain useful-to-user information). And at v=1 there's now a lot more information on the screen that you need to hunt through the output to find the ETA line before it scroll off screen.
Also, perhaps date-stamping the ETA line would be helpful: for example I know the ETA is 3h15m according to the output on my screen, but was that printed just now, or an hour ago? Copying this ETA line to factor.log (where everything is datestamped) would also be helpful, that currently logs [c]nfs: commencing lattice sieving with X threads[/c] but nothing else.

[QUOTE=James Heinrich;609900]I would still suggest, however, that this line of output with the ETA should be included even at verbosity level 0, there's already a fair amount of output from NFS sieving so the extra line with ETA every now and then wouldn't really make things much longer (but contain useful-to-user information). And at v=1 there's now a lot more information on the screen that you need to hunt through the output to find the ETA line before it scroll off screen.
Also, perhaps date-stamping the ETA line would be helpful: for example I know the ETA is 3h15m according to the output on my screen, but was that printed just now, or an hour ago? Copying this ETA line to factor.log (where everything is datestamped) would also be helpful, that currently logs [c]nfs: commencing lattice sieving with X threads[/c] but nothing else.[/QUOTE]

Good feedback, thank you. I can make that happen.

Why does yafu 2.08 binary from github say that it was built with Microsoft Visual Studio 1922?
Is there code from before year2k problem?

Can anyone create an app_info.xml file for boinc yafu project to run yafu 2.0 instead of 1.34?

[QUOTE=bsquared;609450]I've fixed this now. Still need to update the windows executable on github.[/QUOTE]Any chance you, or someone, could build a new Windows executable with all the latest changes and fixes?
[c]factor.json[/c] output would be particularly useful to me ([url=https://www.mersenneforum.org/showthread.php?p=605289#post605289]added in May 2022[/url]), along with whatever tweaks and fixes have been made since the last build (6 months ago).

YAFU docfile.txt says: [QUOTE]<name> = light: pretest to t-level 2/7 the size of
the input before starting qs/nfs[/QUOTE]but it seems it's rather 2/9 the size.

I'm on vacation for a couple weeks. When I get back I'll get a couple more fixes done and update the windows version.

I use this perl script to contribute to factordb, but sometimes yafu gets stuck factoring the same number indefinitely.

[QUOTE=kotenok2000;610529]I use this perl script to contribute to factordb, but sometimes yafu gets stuck factoring the same number indefinitely.[/QUOTE]

When I notice this happening I abort yafu (ctrl-c), then restart it on the same number with -R -noecm and this works for me in that every time I have done it I have got a factorization very quickly. It implies that there is something awry between finishing the ecm stage and starting the NFS stage for the numbers that this happens to (but I know not what, and I could be completely wrong).

I restarted it manually with the same command line and it correctly factored it.

I tried to get batchfile processing working with YAFU 2.08 and it's not playing nice for me. Running YAFU interactively or passing it a single number (e.g. [c]yafu-x64 "factor(12345)"[/c]) works fine, but when I specify to use a text file for input it gives a very ambiguous error that it can't open "something":[quote][c]U:\factordb>yafu-x64.exe -batchfile random_composites.txt[/c]
no variable indicator (@): interpreting batchfile lines as input expressions

YAFU Version 2.08
Built with Microsoft Visual Studio [b]1922[/b]
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz
Detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991
Parsed yafu.ini from U:\factordb

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
======= [email]bbuhrow@gmail.com[/email] =======
======= Type help at any time, or quit to quit =======
===============================================================

[color=red]>> fopen error: Invalid argument
couldn't open for reading[/color][/quote]The error message is trying to say what file it is trying to open but the filename is apparently empty at that point (which of course explains why it can't open it). But it's not really clear what file it's trying to open. Tried with base filename, different filenames, relative paths, full paths, different drives, but I can't get it working in v2.08

Perhaps a little overall code tweaking could make the error messages more useful, instead of saying "fopen <filename> failed", it could say "(log|factor|batch|whatever) fopen <filename> failed". Extra points if you can show what the configured filename was before it resolved down to emptystring.

edit: Maybe my problem is (like [i]kotenok2000[/i] pointed out) that the version I'm using was built using a 100-year-old version of MSVS. :wink: