"Lewandowski, James R." <[EMAIL PROTECTED]> wrote: >for the second time an XP machine crashed while saving a subvi of a library >and corrupted the whole library. >At one point I believed that a "llb" file was only a list to point to >other subvi's but it really seems that is not the case. I was working >on a new subvi that was saved into the llb when the corruption occured. >I only lost the work I had done today, and am currently waiting on our >support people to restore the file from a backup of a couple months ago. >Any ideas how to get at this work?
Well, depending on when the problem occurred during the save, there may be a little chance to retrieve some of the work. If LabVIEW however can't browse into the LLB anymore it has to be considered total loss. NI might be able to retrieve some of the information but this is a laborous job and they have a lot of other things to do than putting their developers up with such a task. Considering the loss of "only" one day of work anything else but trying to retrieve the data file for file by trying to open them each in LabVIEW will simply cost you more than trying to recreate it. I do think your computer may have some serious problem either hardware or software related (bad RAM, HD or corrupt LabVIEW or Windows installation). The way LabVIEW saves LLBs should almost completely prevent such things as it creates a temporary copy of the LLB in your temp folder modifies everything in there and when no error occured, the temporary file will be moved to replace the original file. A few suggestions: During development don't use LLBs. They are a complete nodo if you ever want to use source code control, have little use nowadays with all OSes allowing for at least 32 character filenames (MacOS only) or usually 255. They are a remainder of the times when LabVIEW had to run on Windows 3.1 with its nice 8+3 character filename limitation. Without that they would have never been invented. Individual file loading is sometimes and saving generally faster than using LLBs depending on the LLB size. And the little compression you gain in an LLB compared to individual files is no reason with GB HD space being bought by the single dollars nowadays. Creating subdirectories inside your project is much better, less error prone, and allows you to manage and supervise the source code of your application in the standard OS file browsers if you need to. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
