LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to convert Labview 2.2.1 (Mac) vi's to labview 7.0 (PC)?

I have tested it on the following Macs:
 
Mac Mini(OSX and OS9)
G4(OSX and OS9)
3 different PowerPCs from the 7000 series(OS8 only)
1 other unit that I don't remember the model for(OS9 only)
 
I recently tried the conversion cd in my PC, and it is starting to give me problems there too. I had originally spent a week one day working with our university's Mac specialist. We couldnt get it working after trying several versions of Mac OS. We finally decided that there must be something wrong with the resource forks. When I open the files on any of the Macs I get a dialog box asking me what program I want to use to open the file. I thought about choosing Acrobat Reader, but decided that I didnt believe in programs opening other programs.
 
Some of the NI people I talked to said that the CDs just don't work on Macs. When I saw that you had used it, my curiosity was peaked.
 
Interestingly enough, when I talked to the people at NI last week, the chap I spoke to said that I didnt even think anyone on his floor had a Mac. This was funny to me, since Labview had originally started out on Macs.
 
I did try try running the program directly from the CD, and also by copying the program to the HD and trying it there. The only reason why I want to try the files from your CD is because that would rule out my resource fork theory pretty quickly, considering that you have a CD that definitly works, and mine only works with Windows machines. If you have any other ideas, I would love to try them out. I have plenty of Macs at my disposal, which I will have to do if I can't get this working. Thanks again for your help.
 
Jordan
0 Kudos
Message 21 of 23
(710 Views)
I am not suprised that this thread is still alive!

We bought a bunch of licenses for LV 1.5, the 'killer app', along with a bunch of Macs quite a while ago. I *still* have the same 'funny' feeling that Jordanyorg expressed regarding the complete abandonment of the Mac platform. A few years ago, the 'excuse' from one of the NI visitors on campus was Apple's lack of support for PXI architecture (never mind they were on the forefront of introducing this bus).

Regarding the switch from 2.x to 7.x, I vaguely recall that the critical point was for LV 3.5, where all VI's would be "dual-platform". The warnings NI issued then were to convert all 1.x and 2.x to 3.5 prior to going to 4.x.

In 4.x, I recall the warning that the many "compatibility VI's" between 1.x and 2.x going into 3.5 would be dropped. However, I have found that many of these "compatibility VI's" still functioned in 4.x. As for upgrading beyond 4.x, there was no compelling reason to do so until "undo" was implemented in LV7, I think it was. I do not need Visa on top of GPIB, thank you very much!

So now we have two labs; one is all Mac with 4.x and one is all PC with 7.x. I have not taken the plunge to batch-compile the entire custom Mac library into LV7, partly due to the bizarre way in which LV7 handles paths on XP (which I'm still learning how to cope with when I change even the name of a single sub-vi!!!).

It's University vs Industry, IMHO! I was delighted to see all the help offered to the person who started this thread. Although computers have a 2-3 year lifetime, we who rely on LV have a much longer career than that!
0 Kudos
Message 22 of 23
(691 Views)
Well, I found an old conversion CD in the lab and plugged it in. low and behold it worked wonderful. So now I have my solution. Hopefully this isnt a problem with all of the newer CDs. Or if it is, Ni can always revert to an old iso of the CD.
 
Thanks for all your help.
 
Jordan
0 Kudos
Message 23 of 23
(661 Views)