Dasylab 13 - Module not found error (display1, DISPL1.DLL?)

[zac_schramm]

Hi All,

I had a super strange error today that my Y/t charts all get a module not found error.  This software has worked for many years without issue (and we still prefer version 13 due to memory handling, though we have bought the new versions).

If I look through the modules I can see that half the display modules are not loaded.  I did not change anything since yesterday when I used this.  

When it is loading I notice display 1 module is not listed here and there are no errors.

However the file is there in the pool directory

I tried to uninstall and reinstall and got the same result.  I am so surprised and not sure what to do here.

Thank you, Zac

[zac_schramm]

I just tested this on my laptop and it is exactly as I thought, DISPL1.DLL shows as being loaded and everything works.  No idea where to go from here.

[zac_schramm]

I enabled some debugging in the .ini file and now see this error.

[2025-09-10 19:45:16] FPWRITE.DLL not found.
[2025-09-10 19:45:16] DISPL1.DLL Cannot be loaded.

[MvanStraaten]

Hi Zac,

a few weeks back I had the same problem. I also couldn't get the displ1.dll to load. In the end I installed the newest DASYLab version and it works for now. 

Annoyingly, I have this issue now again on another system. For me this happend both times on a system that was previously running Windows 10 and was updated to 11. It runs fine in the beginning and then after a week or two the .dll doesn't load anymore.

Kind Regards Michael

[zac_schramm]

Thank you Michael.  Unfortunately DL13 works much better for displaying a lot of data than the newer versions which I get memory errors with.

At least we understand the problem a little better now, I will update all here if I make anymore progress.

[stephan.gerhards]

Hello

We noticed this problem with Dasylab 13 with some other customers too.

Upon closer examination of the problem, we saw that Microsoft removed some older 32-bit DLLs with the latest Windows 11 update, which were previously still included for compatibility reasons. In your case, the DLL “ctl3d32.dll” is used internaly by the Dasylab DLL “displ1.dll.” If ‘ctl3d32’ is not (or no longer) available, Dasylab cannot use the DLL “displ1” and some display instruments implemented in this DLL are no longer available.

A simpler, quicker way to solve this problem is to copy the DLL “ctl3d32.dll” from another system. So far, we have not seen any further negative effects, but nevertheless, this tip is at your own risk.
I therefore strongly recommend switching to newer Dasylab versions. They do not have this problem.

Best regards

Stephan

[zac_schramm]

Hi Stephan,

Thank you for updating us here.

I found a tool GitHub - wasson-ece/CTL3D32-Hunter: A Windows restoration tool for recovering the CTL3D32.DLL file r...

Someone made this since the update also broke another Agilent software.   It supports silent deployment as well which is nice.

Agree with newer versions of dasylab, as I mentioned the issue is just being able to plot a lot more data at once with version 13 as compared to 2016 and newer.