Quartus problems caused by Windows display language the non English

[efe1864]

Hi, the Quartus Prime (light or full) versions are not working properly Win 11 OS home addition which is selected Turkish as "windows display language". Home addition is not allowed to chage language into English unless upgrading to pro version. Briefly Analysis&Synthesis phase can not be passes throw to next while using system display set languge non English. I have tested problematic project on a computer works Win11 English, it hascompiled perfectly. I have seen the similar problem(s) in community and some suggestions are consist of deleting megafunction folder, deleting several files of the project etc. But it not helps. 1st of all the resolver should focus on the problem by providing similar condition; win 11 home edition -preffered- Turkish Windows display lang. Thanks

[TingJiangT_Intel]

Hi there, which version of Quartus are you using? Some old versions aren't compatible with Win11.

[efe1864]

[efe1864]

Hi @TingJiangT_Intel any findings to solve?

[TingJiangT_Intel]

Hi there, I'm communicating with experts, if any updates will let you know.

[TingJiangT_Intel]

Hi there, what error message did you get?

[efe1864]

Hello,

 Please see the transcript of the tool and please find attached .txt saved by the quartus.

We can not make development caused by this issue.

Thank you

[TingJiangT_Intel]

Got it, thanks for sharing. BTW does this same error happen when compiling on the command line (quartus_sh --complile....)

[TingJiangT_Intel]

If the error still exists with cmd line, please share us your testcase shows the error for further investigation. Thanks

[efe1864]

Hello,

a) It is very good that you got the problem. But i do not have any idea what is the problem, if you share more info i'll do my best to understand it.

b) If you lead me that how to run tool via command line i can help you. Cmd line can be an option but i think it should not be unique method. For that reason i did not examine the user manuals of cmd usage ever.

c) I have shared the error message as visual and also .txt file. What do you need more to check, please inform me.

c1) You are not volunteer to re produce problem in your side but i strongly suggest to do it, other wise by you guidance performance we'll moved to another fpga solution in year the 2025. Intel can solve this problem with proper patch, i trust you.

Best regards.

[efe1864 · Accepted solution]

No solutioın yet, we accept the solution(?) to closed the case, we'll move to AnotherMadeDevice