CopperLan

One thing I noticed. In the console, at the top it reports: "Find CLP error: 2"

Ha? interesting... it means that the VNM is not able to load its the extension libraries...

Do you see the folder "C:\Program Files\CopperLan\CPVNM\CLP" ? does it contain *.clp files?

Ha? interesting... it means that the VNM is not able to load its the extension libraries...

Do you see the folder "C:\Program Files\CopperLan\CPVNM\CLP" ? does it contain *.clp files?

Nã, no CLP folder.

Just reinstalled and still... no CLP folder

???? That's amazing! How is it possible???

Maybe some file system issue around the program files\copperlan folder?

After CopperLan uninstall, do you still have a C:\Program Files\CopperLan\ folder? if so, can you try to rename it, then delete it before re-installing CopperLan ? this is to ensure that the CopperLan folder has no custom owner or security property that could prevent installation of the CLP files.

Sorry Philip for having mislead you. The folder is there, I looked in the Copperlan folder instead of the CPVNM one.

I just reinstalled it just in case but the issue is still the same: "Find CLP error: 2"

This is one of those ones, hã!

Hi Phil.

Just to check, I installed Copperlan in a laptop with windows 7 where I really didn't need it and the problem is exatly the same.

Really??? That's crazy...

So, finally you see the *.clp files in the C:\Program Files\CopperLan\CPVNM\CLP subfolder, right?

Can you try to copy the *.clp files next to the cpvnm.exe in the C:\Program Files\CopperLan\CPVNM folder and then chack if you still have this "Find CLP error: 2" when you start the VNM in console mode?

Just give a moment and I will check it. I just need to have remote access to the machine.

Meanwhile I made one experiment with my office windows 10 pc. Installing the 1.4 the ethernet device still doesn't appear BUT if i install the 1.3 version it will appear and I can see the the first "picture" of the local cp config. Unfortunately I can't click anywhere in the configuration menu just because the manager closes.

Reverting back to 1.4 and it gets the usual error.

So, there is something to work here, right?

As I know you're the only one with this problem... and I can't figure out what is going on...

So... yes, there is something to fix, but I need you to make some experimentation in order to find the cause of the problem...