New Contributor
New ContributorHello @RichardTanSY_Altera ,
thank you for taking this issue seriously.
@StephanBorucki is currently not able to access his Intel account, but I will try to answer all of your questions.
1) We have always been using the GUI to start the compilation. Is using the command line worth a try?
2) Rebooting the computer has absolutely no effect once the error has occurred.
3) "Can you try quartus --reset_desktop to see if it helps?"
We will give it a try.
4) "In the C:\Users\<user>\ directory there is a quartus2.qreg file, delete it and see if it helps."
We will try that as well.
5) "How much free disk space is on the machine that crash?"
This varies from machine to machine, but at least 250 GB and in some cases > 1 TB.
6) "Could setting the Quartus installation files to read-only be a potential workaround?"
I assume, you are referring to the program files folder, correct?
7) Start Analysis & Synthesis from the GUI, Fitter from the command line.
We can also try that.
Once the error in question (293007) has occurred, it will always occur on that machine no matter what project we are trying to compile and no matter where that project is stored. Therefore it seems like the entire Quartus installation on that particular machine gets corrupted on the first occurrence.
From this point onward nothing seems to be able to revert the issue - not even uninstalling and reinstalling Quartus. The only way that we have found so far that fully restores Quartus on an affected computer is the previously described procedure using CCleaner.
9) "What is the license setup?"
We usually work with Lite Edition 19.1 and 24.1, so no license is required. When we installed Standard Edition 24.1 for testing purposes we used the 30 day trial, so also no license needed.
10) "Project > Clean Project..." and "manually delete all quartus-generated subdirectories"
This makes no difference either; the error persists.
11) Deugging the fitter with VS
We will look into this once we find some spare time.
For now this is all the information I can provide.
We will make sure to try out your suggestions, which we will probably not get around to before the end of next week.
Kind regards,
Nils
