wrong file extension name, can't open image

Hello,

When I created an image of a hard drive to a network share I created it with the wrong file extension name by accident. I'm not able to open the image file because it says it's either not a valid image or it's corrupted. Even if I append the correct file extension I can't open it. I've also tried renaming to the proper file extension with no luck. Is there any way around this? Surely naming the file extension would NOT be optional if it could prevent the image from being able to be opened.


Regards,
Elvar

 

Hello Elvar,

Not long ago someone had problems due to invalid characters in the first part of the filenames (he had used dots for the date) but after he renamed the files they were accepted. That would mean the file name is not recorded inside the file itself and it may be changed, even if the image has been split into several files (as it has been in the case I'm talking of).

Did you happen to use some complicated file name besides the wrong extension? Try changing it to something simple if you did.

 

I named the file pc01_full-2006.12.08.bkf instead of .tib by accident. I had just ran an ntbackup right before and used it's file extension instead of .tib. The image completed fine but I can't open it. I've tried renaming to .tib and even .bkf.tib and neither has worked so far.


Any further suggestions?

 

Remove the periods in the 2006.12.08 part of the filename.

 

The most recent posting from seekforever is a good one. He is very knowledgeable about this product. You might go a step further by eliminating the hyphen. I would suggest trying a rename to 1208.tib and see if that works.

 

Re: wrong file extension name, can't open image - Solved

You'll have to please excuse me, some serious user error was in effect. I was trying to load the initial first image which I canceled and was not complete. The good image was split up amongst many files and not one of them was named .tib but rather all missing the .tib extension. Because of this, I kept trying to load the incomplete image. I finally realized the mistake and loaded the correct image specifying "show all file types". Sorry for the confusion.


Thanks,
Elvar