Corrupted file recovery & repair (urgent please!)

Hi,
Does anyone know of a why to try to salvage a file that has been damaged during a power failure. That is, a surge in electricity probably damaged the file, even though the machine did not reboot, the lights flickered on and off, and the computer locked down and needed reboot to be able to log on again. The file in question now cannot be opened.
Does anyone know how to possibly fix this? Any tool?
This is very urgent, if you can help.
Thanks, on behalf of me and a friend in need.
Mrk

 

What file type are we talking about?

 

Hi,
An .llb file - associated with LabVIEW (containing lots of .vi files).
Mrk

 

Mrk,

I don't know about LabView, but some programs make backup files when you save over the same filename. So there would be two files with the same name - one with a .bak (or other) extension. Some programs may even have an autobackup feature that saves it every few minutes. Perhaps you could search your drives which contains the data and the program for just the file name with no extension and see what turns up. Maybe you can find an older version of the file as well.

It's a long shot, but if the data is unreplaceable, maybe you could contact tech support for LabView, explain the situation and see if they could look at the corrupted file. Maybe just the file header is corrupt and they could fix it.

 

Since you said that the PC got "locked"...
if there aren't any bak/.sav/whatever files got saved,
chances are pretty much everything 's gone.
There is a very slight possibility that some (certainly not all) of the data,
managed finally to get written from memory in the hard disk's clusters,
but they 're just not visible (maybe 'pagefile" would help?not 100% sure).
Even then,you would have to get your PC in a data recovery company,
explain them exactly what happened and expect to pay a lot of money,
with not always having the results you would want.

 

Hi,
The thing is the library got damaged. So of the VIs - call them dlls / functions if you want - have become damaged. All files are there - but not all working. There are backups of course - but older version of the application (it's something this guy and I wrote together). In the meanwhile, we started reconstructing the last version ...
The library was open when the electricity failed. The computer stayed on, but something got messed up. We didn't notice until we tried to log in and could not. Reboot - and then the mess started. Tried loading the library and some of the files could not be loaded. It's quite a complex application - calls to more than 140 functions ...
We contacted National Instruments, but it takes time ... So we're writing it again. It's called deja vu work.
Mrk