dir.mnu dependency conflict

[Kevin_H.]

When you save the VI and the project and ANY and EVERY file it asks you to save, close ALL of labview and reopen the project/VI files do you get the same warnings? I believe you shouldn't. That's simply the change of dependency path system in labview automatically fixing some path names that were incorrect. It's actually a good thing, otherwise you'd have to go manually find all your files. Also, it's just a warning, so it shouldn't effect anything running successfully.

[JLBehr]

Yes,

I quit all LabVIEW apps.

I then re-start LabVIEW,Select the project from recent projects, and fail.....

-Jason

[Kevin_H.]

And you did save? Those warnings shouldn't persist if you save EVERYTHING (even the files that aren't yours).

If they do you may have something wrong with your LabVIEW install and it might be worth a repair.

[JLBehr]

Hi Kevin,

Yes I saved.

And I did save everything....

I just repeated the same procedure on my system to be deployed (PXI with LabVIEW having just been installed)

same exact problem, so that would eliminate a LV install issue.

Same drivers:

LabVIEW 2009 Pro, Ver 9.0f3

NI-VISA Ver 5.0.3

Point to clerify:

when I installed the instrument drivers I take the .zip file and "expand it here" into the inst.lib folder.

Is there some other way?

Thank's

-Jason

[Kevin_H.]

OHHHH I see the problem (and why it won't go away). VIs are loaded into memory and maintained in a memory space associated with their name. Both of those drivers have a set of files with identical names (normally the naming convention is to put productname_viname to avoid this). You're going to need to rename (making sure to maintain the links) one of the sets of conflicting files or it won't be able to load both groups into memory.

[JLBehr]

Hi Kevin,

I disagree.

This Keithley DMM and HP supply have a large user base, and LabVIEW also has a huge following.

I can't believe it's normal to get this many error messages  with common equipment.

Have you attempted to recreate this error, and what were your results?

If I have .vi files with the same name, I would agree. I disagree that this is true for the .mnu files. Only the .mnu files are being reported as conflicting. NOT the .vi files

As I look in the user.lib/templates, everything has a dir.mnu.

And for the loaded question, as BOTH of these drivers are NI Certified and NI Supported (see the links you provided above) would it be normal to expect NI to fix them?

Have a great Weekend!

-Jason

P.S. If you want to work on this in real time, I provided you my contact info by private message a few days ago.

[Kevin_H.]

I executed the steps you suggested and received warnings, but never .mnu warnings. My warnings also went away after saving. To clarify my steps were exactly as follows.

1) Create new project

2) Create new VI

3) Load Initialize.vi from one of the drivers (tried in both orders)

4) Click through warnings

5) Save

6) Repeated 3-5 with other driver

7) Save Project

😎 Click Close on one of the VIs front panels

9) Save the driver VIs that have been modified for my version of labview and location problems

10) Repeat 8, 9 for second VI

11) Close Project

12) Save lvlib files for version and location changes

13) Reopen with no warnings

I did notice there was a bug fix in LV 2009 SP1 that says

188425

—

.mnu files with same name conflict even if they have different namespaces.

and that you appear to be using standard LV 2009. Is it possible for you to upgrade to SP1?

Source: http://zone.ni.com/devzone/cda/tut/p/id/10829

[JLBehr]

RESOLVED!

Upgrade to SP1,  and then apply patch SP1-f1.

-Jason

[Kevin_H.]

Excellent!