In Bridge 18.104.22.168 I have many NEF file that when I try to open them I get the following message, "Could not complete your request because an unexpected end-of-file was encountered." Are there any work-arounds that I can try to open these files?
Have you tried to open them in ViewNX or CaptureNX? They might be corrupted.
Can you tell us from what camera they have come, what version of Camera Raw you are using, and how you got them from the memory card to the hard disk?
They copy to my hard disk and I work with them through Bridge/Photoshop. I don't understand why it matters what camera, they are Nikon NEF files, which is, if I understand it correctly, NIKON's version of RAW.
The Nikon NEF extension obscures the fact that all raw formats are different for every Nikon camera. So, no, it's not that simple.
The method of transfer has caused problems recently, with Nikon Transfer modifying raw files, making them unreadable by Adobe.
The best policy is to transfer files using a card reader an either the operating system itself, or Adobe Photo Downloader.
Meanwhile, I'm trying to check that your software supports your camera model. Btw, you can update to Camera Raw 6.7, but no further with CS5. This is always worth trying, as long as your camera is supported.
Okay. So it's long supported. It sounds like file corruption. The question is How. Do you still have images on the card? Raw files contain small previews, so that might be what you can see. You might still see the preview, even if the file is broken.
You still haven't said how you copied the files to the disk. Was it manually using drag and drop, or did you use software? This might narrow it down a bit.
You might be looking at a card, reader, cable, software, or operating problem.
In Bridge 22.214.171.124 I have many NEF file that when I try to open them I get the following message,
So you mean that also your old files are corrupted, some can be opened and some not but all still have the .NEF in the filename and their is no renaming used that for example have an other dot added to the filename.
Just trying to understand a bit more, leave the Windows and Nikon tech part to Yammer P and Curt.
And don't you have a back up of the files? If not then start to develop a good back up startegy. If you use photodownloader you can also check this option while getting your files from the card reader. When the card reader is corrupted this will not help you but also always check randomly if the previews build in HQ in Bridge before formatting the CF card again (always in camera with camera software!). If previews build correctly then its not likely the files are corrupted on ingestion.
These file are from when I lived in Italy in 2005-7, so, no I don't still have them on a card. As a matter of fact I no longer use Nikon due to too many problems. (don't have a hissy fit nikon users) I always download my files to a folder in my main hard-disk and to a secondary folder on my tower. I also periodically back these up to a remote hard drive. that taken care of. I have many files that work just fine but far too many that will not open. I am looking for a work-around way to open the file, In Nikon viewNX I can open the "preview" of the NEF file just fine but when I try to open it in Photoshop CS5 I get the file end message. Is there a work around?
Is there a work around?
Don't know of any other then use the back up files to retrieve raw data or extract the jpeg previews from the NEF files. Be aware this is not the same file size as a Raw file but if you don't need it for large size print or publishing it will get you somewhere I believe.
As a Canon user I have no experience with Nikon nor did I need to extract jpeg previews but according to Google their are dedicated software options for this workflow.
Try this John Nack blog message for a start:
Although they also talk about the option for this in Bridge CS4 I can't find it in CS6 nor have I heard of it before.
And if your back up has the correct files it might also be wise to check all content on the problem disk and when sure to have back up or it can be deleted check the disk for errors. maybe even reformat and start again or use a new disk.