LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

creating an EXE in 6.1 previously saved in 6i

I developed an LLB in LabVIEW 6i and I opened and saved the top level of that LLb in 6.1, when I tried creating an EXE from 6.1, an error came up;

'Generic file I/O error occured VI library 'internal.llb' could not be saved!!
LabVIEW save error code 48: Could not move temporary file to destination'

when I press on ok, a dialogue box appears asking me to select a directory where I want to save the run time menu internal.llb, when I select one of the folders in C:\temp, it saves the llb but then pops up with another message saying 'Error 7 occured at librarian get info.vi-file could not be found
LabVIEW file not found or NI-488 non-existent board'

I know (or atleast assume)that this error was caused by me saving the
llb I created in 6i in to 6.1 and then trying to create an EXE from 6.1, the LLb has more than 200 vi's in it as well. Does anyone no a way around this?
Edge!
0 Kudos
Message 1 of 5
(2,851 Views)
You could always make a copy of the libray, do a mass compile on it and then use the converted version to build your app.

Mike...

PS: I love your guitar work. Say "hi" to Bono and the rest of the guys for me...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 5
(2,851 Views)
I would add that I would first use the library manager to convert the LLB to a directory of individual VIs. Get rid of any VIs,.lsbs that were in vi.lib so that you are using the newer 6.1 functions.
0 Kudos
Message 3 of 5
(2,851 Views)
excellent point...

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 4 of 5
(2,851 Views)
Dennis and Mike, great answers. Following on their ideas; Edge, you could open the top level VI in LabVIEW 6.1 and then save with options, saving it as a new development distribution to a new location. This would provide you with a new llb with all the VIs in LabVIEW 6.1 and would address the issues Dennis mentioned.

Evan Collier
Applications Engineer
National Instruments
0 Kudos
Message 5 of 5
(2,851 Views)