I have been a faithful Ghost user going back at least 10 years starting with the DOS versions. Almost 2 years ago I began using Ghost 14 for backups and have not had a problem. My C drive was about to fail so I made two separate backups with the "Ignore Bad Sectors" and "Verify recovery point after creation" options selected. After doing this I shipped off my C drive for a replacement. In the meantime I was using a laptop and decided to browse my backups of the C drive. I was able to do this successfully on both independent backups.
While I was in the recovery environment (booted from the recovery CD) on another occasion, I came accross a partition editor utility on the Norton disk. Im not exactly sure how I did it but I deleted or changed the Master Boot Record (MBR) of the recovery drive containing my two backups via that utility. My only option at that point was to use a third party program to recover my missing .v2i files. The program recovered my backups successfully and I saved them to another drive as the backup drive with the missing MBR had to be reformatted to create a new MBR. It has since been reformated.
However, now I am unable to browse or load the two recovered .v2i backups that worked fine before. I keep getting the error message, "Error ED800012: The internal structure of the image file (Last File Frame) is invalid, damaged or unsupported. Error ED800012: The internal structure of the image file (CRC Check or Frame Header) is invalid, damaged or unsupported. I tried mounting the individual .v2i backup images to see if I could pull individual files off instead of reloading the whole image file, but all that does is crash the recovery CD image browser with an "UNKNOWN ERROR" message.
This whole situation is quite unfortunate as I have lost almost 15 years worth of data. I have read that there is no known way to browse, handle or repair seemingly damaged .v2i files. It would be nice if Norton would create a utility to allow users to access ANY recoverable data. Until that day comes, I will store these two backups and the associated .sv2i file (34GB total) possibly forever. I am quite disapointed to have possibly lost so much because no one has thought of a way to repair or browse seemingly damaged .v2i files up to now. Please help or let me know who I can contact to develop this utility.
Thanks for your time.