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

[rioch]

I finally got the conversion kit. However, I have no experience with labview version 2.2.1.
The files I want to convert do not even have .vi or .llb extensions. Actually, there are no
extension with these files.
Could experienced ones give some advice? Thank you very much.

[chilly_charly]

---

rioch wrote: The files I want to convert do not even have .vi or .llb extensions. Actually, there are no extension with these files.

---

That's normal with MacOS files. Before MacOS X, the file type (and creator) was stored in a dedicated file location (ressource). Forget that and modify simply the vi names by adding the proper extension.

CC

[rioch]

Thank you for your information. I tried to rename the files and open them.
I got message "the file ***.vi is not a VI, select another?"
BTW, I have transferred the files from mac to pc and try to open them with
labview conversion kit in windows.
Is this possible?

[rolfk]

chilly charly wrote:

> That's normal with MacOS files. Before MacOS X, the file type (and creator)
> was stored in a dedicated file location (ressource). Forget that and modify
> simply the vi names by adding the proper extension.

LabVIEW itself doesn't care about file endings. From the File->Open menu
you can select a file with any ending (set the File Type selector in the
dialog to Any Type (*.*) to be able to see other files than the ones
with the proper endings). LabVIEW then tries to verify the file as a
LabVIEW resource file and if successful, it will open it independant of
the ending it may have.

Of course to be able to point and click on a file in the Windows shell
you will have to have proper endings as the Windows shell can only
recognize file types based on endings.

Rolf Kalbermatter

[rolfk]

rioch wrote:

> Thank you for your information. I tried to rename the files and open them.<br>
> I got message "the file ***.vi is not a VI, select another?"<br>BTW, I have
> transferred the files from mac to pc and try to open them with labview conversion
> kit in windows. <br>Is this possible?

No. The LabVIEW files for version 2.2.1 and earlier where Macintosh
files only and actually had most of their interesting part stored in the
resource fork of the file. This resource fork is simply lost when you
move the file to a non MacOS system, since they do not support forked
files as Mac OS used them. So most of what the VI consists of is lost
after copying the file to a non MacOS formated media.

You will actually need at least a conversion kit installation on a Mac
OS system and since you would need the conversion kit comparing to I
think LabVIEW 5 to be able to read 2.x files, I'm afraid it will only
install on a Classic MacOS system.

Rolf Kalbermatter

[Jordanyorg]

---

@rolfk wrote:
@rioch wrote:

You will actually need at least a conversion kit installation on a Mac
OS system and since you would need the conversion kit comparing to I
think LabVIEW 5 to be able to read 2.x files, I'm afraid it will only
install on a Classic MacOS system.

Rolf Kalbermatter

---

What do you mean by Classic MacOS? I got the kit and tried it on some pretty old PowerPCs running OS 8, as well as a few G4s running OSX (and OS9 in the background)and it could not even recognize the files as being executable. The Windows side of the CD works fine. If NI could provide a downloadable kit then I'm sure I could get it up in seconds. Can anyone provide a stuffed or zipped version of the Mac Conversion kit?

Thanks,

Jordan

[johnsold]

Jordan,

I am not familiar with the conversion kit, but I have LV 4, 5.1, 6.0, 7.0, 7.1, and 8.0 installed on this computer (Mac G5, OS X 10.4.6 and Classic OS 9.2.2). Classic is what Apple calls running OS 8 or 9 under OS X. If you can post one of your troublesome VIs, I will try to open it on one of the old systems. If it is a valid 2.2.1 VI, I can convert it for you. If it has a lot of old DAQ VIs, those will need to be replaced with DAQmx equivalents; the conversion will not be without some effort.

Lynn

[Jordanyorg]

It's a lot of files, and I would hate to inflict them on you. I had a porttion of them changed by NI, and it took them a while. Ideally I would like to have a Mac compressed version of the kit. That way, if I run into this issue again I will be able to fix it on the spot. Like I said before, the only issue is that no Mac I've used so far(OS8, OS9, OSX) recognizes the Mac versions of the programs as executable files.

[johnsold]

I have not used the kit, because I have all the old versions of LV available (including 1.2 and 2.2.1). I thought it might help if I looked at a few of the VIs to verify that they are, in fact, old VIs.

Lynn

[Donald]

---

@Jordanyorg wrote:

... Ideally I would like to have a Mac compressed version of the kit. That way, if I run into this issue again I will be able to fix it on the spot. Like I said before, the only issue is that no Mac I've used so far(OS8, OS9, OSX) recognizes the Mac versions of the programs as executable files.

---

Jordan,

Do you have a working version of LV2.2.1 to verify that your files are still executable VIs?  If not, Lynn's offer is a good one.

I used the kit successfully several times on several Mac's (PowerMacs 7200 and 8600 with OS8, G4 with OS9) to convert old files.  The only time I encountered a problem similar to what you're describing was with a couple files on a old disk which had been corrupted.

I don't think a compressed version of the kit is available for download.