Hello All, George Gatling wrote: >I am happily working my way through my current project when I suddenly >realize about half of my application is in C:\Documents and Settings\...\Temp\ > >I have no idea how long I have been editing files in a garbage temp >folder, >not to mention which ones are linked to the temp files vs the real files. >GRRR!! Has anyone seen this behavior before? How does an entire app get >copied to temp AND then why does LabVIEW link half to temp and half to real?
Greg McKaskle wrote: > I stinks when this happens, and I'm afraid I can't tell you why it > definitely found VIs in your temp path. Rolf Kalbermatter wrote > What has happened here is that your target drive was full at > some point. LabVIEW saves its files into the temp directory > before moving them to the real target to prevent corruption > of at least the original file due to memory, system or disk > space problems. > > If the target drive is full LabVIEW aborts the save operation > but the files saved to the temp directory stay and if you > later save the application again, the current temp copies can > get the actual linked ones. I have observed this event on several occasions in LabVIEW 7.0 on Windows XP, and as far as I can remember, it hasn't happened on other system configurations. What happens to me is as follows: I press <CTRL>+S to save a VI that is open. LabVIEW pops open an error message about not having permission to save the file. The name of the VI changes to some strange temporary name. I press <CTRL>+S again and the VI is saved to the temporary location with the new name. I am not sure why the file error occurred (I have lots of disk space, which rules out Rolf's scenario). However, maybe the file was locked somehow. Regards, -Jim
