Jump to content

Get the LV version of a VI file without opening it in LV?


Recommended Posts

I would like to determine which version of LabVIEW a given VI was saved in, but not by opening it in LabVIEW. I just want to look at the raw hex of the file on disk to determine it. Does anyone know the key(s) to accomplishing this?

I messed around a little by saving an empty VI file in LV85, then backsaving it to LV821. The files are the same length, and are virtually identical (I think) except for some data at the end of the file (roughly the last 0x01E4 bytes). The whole thing looks vaguely like an old MacOS-style resource file (which I think should not be surprising), but nothing jumped out at me.

And while we're on the subject, any recommendations for a good graphical diff utility for binary files? I've never come across one.

Link to comment

QUOTE(Jim Kring @ Oct 5 2007, 01:09 PM)

Gah. I always look in the properties, but I never think to check the methods... :oops: Thanks!QUOTE(Michael_Aivaliotis @ Oct 5 2007, 01:42 PM)

Ah Jim, you spoiled the fun. I wanted to see how far Justin was going to get with his reverse engineering...

Yeah, hoo-boy, wouldn't that've been fun! :headbang:

Maybe you could've egged me on to do a whole library for the Code Repository, and then once I submitted it you could post the method node in the comments thread. That would have been AWESOME. Whee!!! :P

Link to comment
  • 2 weeks later...
  • 1 year later...

So, I have several test stations that have somewhere between LV7.0 and LV8.2.1. While I like to work from my desk, I have 8.6 here and needed a way to take a package and finish development on the test station. LV doesn't seem to have an option to make Save as Previous Version the default save method. So I wrote this up to down-rev everything to make the move.

Open to suggestions for improvements or better ways to do this.

Kip K

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.