07-17-2012 01:38 PM
Classic noob case of not doing autobackups for some small project. Usually I work straight from Dropbox, but the last two weeks I was on a new machine and just didn't make obviously (now) small effort to set it up. Anyway, I've seen a few posts from last year where a couple of individuals magically fixed the header/footer of the VI in a hex editor. I've tried browsing it, and doing random stuff (replacing first few bits from a new file, etc.). I'm just hoping for a bit of that same magic before starting the rebuild.
Specifically loading the VI gives:
"LabVIEW: File is not a resource file. The file 'ManualControl.vi' could not be loaded."
Developed in Labview 2011 64-bit. I'm with a university, but I don't think there is free support from NI available anymore for us academics. Thanks for your time.
Solved! Go to Solution.
07-17-2012 05:43 PM
I was in similar situation few days ago, almost lost my 3 months worth of work. Only thing that saved me was my laptop that was closed at home and did not synch up to the currupted version yet. Had to go home, disable wifi and retrieve the earlier version. I would also like to know if there is a way to retrieve these vi.
07-17-2012 05:48 PM
If you're using Dropbox you can go back to old editions of a file. See https://www.dropbox.com/help/11/en. I don't know how this service is free 🙂
07-17-2012 05:54 PM
Source control, source control, source control.. Subversion is free and very easy to use.
07-18-2012 12:07 PM
Unfortunately, as this link shows, there is no official way to recover a corrupted VI. As other users have mentioned, we recommend backing up your VIs frequently so if a problem like this occurs you don’t lose all of your work. Sorry we can’t help you out.
04-01-2013 05:31 PM
Yeah, well it's pretty annoying. I was working on a small utility, hadn't saved it since opening it today, and both the source file and the autosave is corrupt. That may be unfortunate, but it is also UNRELIABLE.
04-01-2013 05:45 PM - edited 04-01-2013 05:47 PM
@Spaz wrote:
Yeah, well it's pretty annoying. I was working on a small utility, hadn't saved it since opening it today, and both the source file and the autosave is corrupt. That may be unfortunate, but it is also UNRELIABLE.
I've had it where autosave corrupted the VI and had to go back to the original file, erasing a few hours of work. In that case, version control would not have helped because I am not in the habit of commiting my changes every few minutes. (What i sweird is that I save often, and it made me go back to the original that was a few saves ago.)
04-01-2013 06:06 PM - edited 04-01-2013 06:07 PM
Early Christmas present.
Edit: Just saw that the commenter was not the OP. Oh well, very late Christmas present.
04-02-2013 01:44 PM
The newest version that I have is 2010. I still use 7.1 the most. (RE: http://forums.ni.com/t5/LabVIEW/Why-I-prefer-using-LV-7-1-Sort-of-like-why-I-keep-using-XP/m-p/11124...)
Althiough I got around my problem, I would be very interested in seeing any other approaches if that's the subject of your VI. Seems small... a screen shot of the BD would suffice.
04-02-2013 01:52 PM - edited 04-02-2013 01:54 PM
I just posted a fixed version of the original VI, without checking the date of course. I have a little utility which tries a few things to fix or otherwise retrieve data from corrupted VIs and LLBs and this one happened to have fixable damage.
Too bad I was asleep at the switch when the original post happened.
Edit: Just got the solution and Kudos from the OP. Excellent. I like it when my spelunking into the depths of LV has beneficial side effects. Better late than never it seems.