recovering source file after crash (Urgent!)

[Intel_C_Intel]

Hi,

While happily working on a project my system (NT4.0) crashed - blue
screen of death. After restart and reopening my fortran project, the
source code (main.for) could not be opened, because now it is binary.

Aargh! 2 days of work lost? I hope not!

Anyone an idea on how to retrieve the original source?

(Why does developer studio create a binary file? I should think
that just crashing the computer shouldn't loose my source, well
perhaps if it happens during a save...)

Thanks!

Henk Witte

[Steven_L_Intel1]

Can you open the source file in NOTEPAD? If so, I suspect that the issue is that the registry was corrupted, so that the association of the Fortran file types as source files was lost. Reinstall CVF will probably fix this. (This is the response I sent you to your support request.)

Steve

[Intel_C_Intel]

I can open it in notepad, but the content is nothing, in wordpad only
unreadable chars (squares). I can open the file in Dev, but get a
kind of hex-layout with all zeros.

I can open other worskspaces/fortran source codes ok by the way, just
this one is corrupted.

Henk

[Steven_L_Intel1]

Ok - you have bigger problems. The file is corrupted on disk - there's nothing Visual Fortran can do about this (nor did it cause the problem). Do you have Norton Utilites for NT? You may be able to use Norton Disk Doctor to recover unlinked disk block chains with some of your source, but if the disk just overwrote the data, it's gone.

Steve

[Intel_C_Intel]

Steve,

I guess I'll have to recreate the file. Perhaps I can find some parts
on the disk. In any case, I suppose the work can be recreated
relatively quickly. Still, only the re-testing of the results will take a
day or so.

Will teach me (again) to make more frequent copies!

Henk

[Jugoslav_Dujic]

Well, I see BSODs daily when compiling with CVF or VC++, with various levels of damage. That's probably hardware problem or some software/hardware interaction. I see crashes like yours frequently (though I use Source Safe even for my own projects so the damage is less); most often, only the beginning of the file is screwed. In cases like yours, scandisk frequently happened -- Win2k scandisk
(or was it chkdsk?) creates a directory called FOUND.XXX in drive's root where I sometimes find my source in a file of obscure name. Hope NT works that way also.

Jugoslav

[Steven_L_Intel1]

System crashes when compiling are often caused by bad RAM or disk (due to high virtual memory usage). Sometimes a bad video driver can also cause such problems.

Steve