Interesting Behaviour

[SkyIDE]

My BCB V6 project got currupted on its own by itself. I have no idea how. I just launched it, F9 and I got bombarded with linker errors. Fortunately I had made a fresh backup copy of the source the previous day and this one works fine.

What puzzles me is, it just stopped working. The linker gave me all these warnings cannot open somefile.dfm quite a few of them. The back up copy works fine but the one on the hard disk did not. I didn't make any modifications in project properies...

Does anyone have any ideas what might have happened?

I looked at the #include paths and they were still the same.

[tchikien]

.dfm files are the form files that store all controls/components you placed on the form at design time. If your .dfm files corrupted you get errors.

[SkyIDE]

Interesting, ahh well...moving along....

I back up the project sometimes a few times a day. After every considirable amount of code work, backing up is a must and now it paid off   Let this be an example to other people -- expect the unexpected and always back up your work.

[f0dder]

1) chkdks /f on all your partitions, just for good measures.
2) subversion for finer level of control than plain backups.

[mouser]

another thing is to compare the backup and hd files and see whats changed.

[SkyIDE]

I wish I could but now but it's too late It's all gone. After that, I believe Belenix's (OpenSolaris) "Install on Hard Disk" utility currupted my "partition table" or something else on my NTFS partitions so I got all these error messages such as \NTLDR missing, \Windows\System32\Winload.exe (this second one is on Vista) even though they were there. I didn't even touch these partitions when I used their fdisk utility but looks like "it" touched them anyway...hehe

I spent about two hours late at night fiddling with rescue CDs and pre-installed environments, replacing bootmgr, msdos.sys, ntdetect etc etc to no avail until I realised their partitioning tool most likely stuffed either my partition table or the NTFS file systems as there was no logical explanation why Windows wouldn't boot. I deleted the Solaris partitions and restored XP on the primary active partition from an image and I put Vista on the second and the Solaris one got replaced with Linux So the corrupted project file is all gone, beyond recovery

So all that was a rough ride hehe