It doesn’t. But it’s often the case that PrePoMax files are placed in location protected by Windows (like system drive) and various issues arise because of that.
This thread discusses the same errors and provides some potential fixes: Gmsh error in v2.2.0
Thanks, yes the gmsh issue is resolved now but still the jobs fail to run. Here some potential solver issues are raised for Win11 pro, this is what may happen?: Extrude meshing question - #26 by Trevor
What if you try using solver other than Pardiso (which is currently the default matrix solver in PrePoMax) ? Only Pardiso needs those special libraries.
Thanks, tried that and when running from cmd, as described here
I’m getting this error message of mkl_rt.2.dll was not found for ccx_dynamic:
when using ccx_static instead, it appears to be running but gives this error:
*Error in linstatic : the PARDISO library is not linked
This is the file: sandwichPARDISO.inp - Google Drive
same is true when i change the solver in Prepomax to Pastix before exporting as inp
I believe I solved this now. It appears that additional dll are missing, at least for an Intel processor system. I followed the steps described here :
and it solved all issues and the jobs are running now in all Prepomax 2.2.x versions (earlier where running fine)
I added all required drivers, including the meshing ones mentioned above, in the link below. Hopefully it will help someone else one day: missing dlls - Google Drive
Instruction: Simply copy all dll to the folder ‘lib’
Are all files in the link necessary to run the CalculiX? I could add them to my releases, but I would only add them if they are really required.
Since two of them are larger, I could provide them separately on the webpage. But since not a lot of users have this problem, I am wondering why. Intel, in combination with a new Windows version, should be a more common occurrence. My laptop is of the same combination and I had no problems.
It seems to be rather rare issue so maybe it’s enough if users will be sent to this thread for a possible solution. We can add it to the Tips and Tricks section too.
Agree with Anys that dll’s from unspecified sources should be treated carefully. It is at own risk, but without trying it from other users earlier would never have found out…
Agree with FEAnalyst that the dll would not need to be added to the release if it’s such a rare occurrence (it works on my i5 laptop but issues are only on my (virgin) i9 machine). You could add trouble shoot instructions how to install these yourself using the official installation file?:
Install and copy the named drivers from C:\Program Files (x86)\Intel to your prepomax “lib” folder. This does not include the gmsh dlls of course which I copied from Trevor’s post.
Matej, I will try to remove the dll’s one by one and see how long it still runs stable but merely followed the instructions in the post linked above and not sure how they came to their conclusions…