[QUOTE=James Heinrich;586413]I tried it, it crashed the same way as the original.[/QUOTE]

[QUOTE=BudgieJane;586425]Version 2.01 works OK on my Win-7 machine.[/QUOTE]

[QUOTE=WraithX;586429]I am missing the same dll files as Budgie and James, but yafu 2.06 works fine on my Windows 7 Pro x64 computer.
[/QUOTE]

I don't know how we have entered dll hell and I don't know how to get out of it, especially given that I have been unable to reproduce the problem on any windows system I have access to (win10 enterprise, win10 home, on a variety of cpus).

I have gone through the effort over the last few months to make sure my windows build system was fully updated to the latest SDK and toolset for MSVC 19. I don't recall if that was done prior to the early releases such as 2.01, which is perhaps why that one works for BudgieJane. I suspect that Brian is correct and a full rebuild with an earlier SDK could be a solution. But that doesn't explain why some people with Win7 systems are able to use 2.06., so there must be a solution from a user perspective too. Just don't know what it is yet.

I think I'm a particularly oddball case in that I'm using both an old OS and a (very) old CPU (no AVX2 for example).
I don't know where to get a copy of v2.01 (that apparently work for other Win7 users), if someone wants to send me a copy I can confirm if it runs on my system or not.

[URL="http://github.com/bbuhrow/yafu/blob/d6cf245f72a7aadf68dea89ef5ff18396418c378/yafu-x64.exe"]Here[/URL] you go! :smile:

[QUOTE=James Heinrich;586481]I think I'm a particularly oddball case in that I'm using both an old OS and a (very) old CPU (no AVX2 for example).
I don't know where to get a copy of v2.01 (that apparently work for other Win7 users), if someone wants to send me a copy I can confirm if it runs on my system or not.[/QUOTE]

That would certainly mean that my build would fail with an illegal instruction exception since I build MPIR with AVX2 assembler support.

[QUOTE=James Heinrich;586481]I don't know where to get a copy of v2.01 (that apparently work for other Win7 users), if someone wants to send me a copy I can confirm if it runs on my system or not.[/QUOTE][QUOTE=kruoli;586482][URL="http://github.com/bbuhrow/yafu/blob/d6cf245f72a7aadf68dea89ef5ff18396418c378/yafu-x64.exe"]Here[/URL] you go! :smile:[/QUOTE]Thanks! But it crashes the same way all the others do.

Is YAFU command line only? If so, maybe it can be built with msys?

[QUOTE=rogue;586503]Is YAFU command line only? If so, maybe it can be built with msys?[/QUOTE]

Yes it does, but while it seems to work for me, people have reported problems/crashes there as well.

Given the availability nowadays of WSL2 and a much better visual studio implementation as of v2.06, I am actually in the process of abandoning the mingw64/msys2 build option and code from yafu. All these different options are getting to be too much for me to maintain.

[QUOTE=BudgieJane;586438]I got a system error: The program can't start because nvcuda.dll is missing from your computer. Try reinstalling the program to fix this problem.[/QUOTE]

I think I want to run away and hide. I found the reason why nvcuda.dll is missing from my computer: it's because my Win-7 computer does not have a NVIDIA graphics card. Extract from the specification:
Graphics Card: INTEL® HD GRAPHICS MEDIA ACCELERATOR 4600

So that explains why Brian's verson won't run.

[QUOTE=James Heinrich;586481]I think I'm a particularly oddball case in that I'm using both an old OS and a (very) old CPU (no AVX2 for example).
I don't know where to get a copy of v2.01 (that apparently work for other Win7 users), if someone wants to send me a copy I can confirm if it runs on my system or not.[/QUOTE]

Here's a copy of what I'm using.

[QUOTE=BudgieJane;586517]my Win-7 computer does not have a NVIDIA graphics card[/QUOTE]My computer doesn't have an NVIDIA card in it either (AMD RX480 now). But it used to in the past so it's got some copies of nvcuda.dll from 2015 still lurking in there.

[QUOTE=bsquared;586475]I don't know how we have entered dll hell and I don't know how to get out of it, especially given that I have been unable to reproduce the problem on any windows system I have access to (win10 enterprise, win10 home, on a variety of cpus).

I have gone through the effort over the last few months to make sure my windows build system was fully updated to the latest SDK and toolset for MSVC 19. I don't recall if that was done prior to the early releases such as 2.01, which is perhaps why that one works for BudgieJane. I suspect that Brian is correct and a full rebuild with an earlier SDK could be a solution. But that doesn't explain why some people with Win7 systems are able to use 2.06., so there must be a solution from a user perspective too. Just don't know what it is yet.[/QUOTE]

I have come to a decision. All this new stuff will not run on my Win-7 machines, so I am giving up with those and I am going to use only my new Win-10-Pro machine. If I must run something on these old machines, I shall go back to version 1.34, which I was running until recently.

There is aboslutely NO WAY that I will expect anybody to prepare versions of their software that will run on 7-year-old machines that do not have the latest SDK and toolset together with the required hardware.

I would like to thank Ben for all his work so far, and would like to say thank-you in advance for future developments.