Louis and Angel, There are two possibilities that I can think of... 1. depending on whether the trndll.dll is compiled in debug mode or release mode, it goes looking in external dlls in either the ..\Trnsys17\UserLib\DebugDLLs\ or the ..\Trnsys17\UserLib\ReleaseDLLs\ directory. It could be that on one machine, the TRNDll is compiled in one mode whereas it is compiled in the other mode on the students' machines. If you run the simulation on each machine and look at the *.log and *.lst files that are produced, you should find a "Notice" telling you where the TRNDll was looking for external DLLs. It is best if the TRNDll and external DLLs are all compiled in release mode. 2. even when the trndll and external dlls are compiled in release mode, they sometimes require access to some other DLLs that are only present on computers that have a compiler installed on them. These are the so-called Microsoft redistributable libraries. They are free and everything may work fine if you install them on the students' machines. http://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-visual-fortran-composer-xe-for-windows Best, David On 5/16/2013 05:09, Angel Carrera
wrote:
-- *************************** David BRADLEY Principal Thermal Energy Systems Specialists, LLC 22 North Carroll Street - suite 370 Madison, WI 53703 USA P:+1.608.274.2577 F:+1.608.278.1475 d.bradley@tess-inc.com http://www.tess-inc.com http://www.trnsys.com |