LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

driver dl1540

Solved!
Go to solution
Solution
Accepted by topic author FonzB

Okay, so the problem is that, unlike other drivers, this particular driver does not install Borland support files. This is why the program file couldn't be attached -- because it was looking for a lib file in the bc folder, and it didn't exist there.

 

You can't really copy .lib files between the two folders, since the .lib files corresponding to each mode have different formats. CVI will not be able to load the msc .lib file when the compatibility mode is set to Borland, even if you copy the .lib file manually to the bc folder.

 

By the way, the Borland compatibility mode in CVI is obsolete and has been discontinued in newer versions of CVI, starting in 2009. Is there a particular reason why you must use the Borland compatibility mode?

 

Luis

0 Kudos
Message 21 of 22
(589 Views)

Ok, this means I have to set the compatibility mode to Visual C/C++ for this program.

When I leave the compiler in this mode I think I'll have to recompile and rebuild all my other programs.

 

There is no particular reason why I use the Borland compatibility mode. It was already so, and I didn't have problems with it until now, so I didn't think of changing it.

 

Thank you for helping me solving this problem.

 

Best regards

FonzB

0 Kudos
Message 22 of 22
(587 Views)