Forum Discussion
So assuming there are 20 computers (each computer has a few Quartus versions installed) sharing on one network drive, however some computers have different specification. Let say we divide into two different computer groups, A and B, more powerful A ( with issue) and a less powerful (with no issue) computer B.
When Computer A1 compiling a Quartus project on the network drive, the Quartus software locally installed in the Computer A1 get corrupted. Then, the Computer B1 is able to compile the same project (compiled before by A1) in the network drive without any issue. Then another Computer A2 compile the same project (compiled before by A1) will get corrupted as well after maybe 5 or 7 compile, in the network drive.
The Quartus corruption only happen in computer A1 and A2, causing them unable to compile project locally, while the Quartus in A3, A4 and so on, is still usable and able to compile the project locally.
My guess is the network drive is used to share the project files to the students after each class.
Correct me if my understanding wrong at this point.
My suggestion for now is to restrict the students permission to compile the project in the network drive and ask them to copy and compile the project in their local disk. Try to set up permissions on the network drive so that the students only have read access but not write or execute access. This allows them to copy the project files to their local drive while preventing them from modifying the original files on the network drive.
Could you try to install a Quartus Standard or Pro version, setup an evaluation license and see if the issue persists? (to check if different Quartus version has an impact)
If possible, try to use a different network drive.
I am trying to duplicate the issue from my side but no success yet. Most likely the setup is different.
Processor Intel(R) Core(TM) Ultra 7 165U 1.70 GHz
Installed RAM 32.0 GB (31.4 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 11 Enterprise
Version 23H2
OS build 22631.5335
Regards,
Richard Tan
Hi Richard,
thanks for your reply. Due to other important tasks I have to do, I won't get around to replying until Tuesday next week, May 27.
Best regards
Stephan