IrfanView 64-bit v 4.4.2.0, Windows 7.
I hesitated to report this, until I saw problems in this thread that look familiar.
The error message says:
(File path and name): Can't read file header! Unkown file format, empty/damaged file or file not found!
Some JPG images do not open in IrfanView even though they open in: Paint, Windows Photo Viewer, Image Lounge, Canvas 11, etc. The JPG does open in IrfanView if moved or copied to the desktop. So this looks like a Windows issue, but why only IrfanView has a problem?
All the “problem” JPGs were copied from a Classic Mac computer via a MacOSX computer. Mac users may know that every file copied in this way arrives into Windows accompanied by a sort of “ghost” file (the classic Mac resource fork, split off). The ghost has the same name, with a “._” prefix. I copied around 6,000 JPG files in about 230 nested folders, then removed all the “._” files using TreeSize file search. Most of these JPGs are legacy scans from film camera days, so have no EXIF data. Those with EXIF were not edited in Mac OS and seem to open OK. An example is attached, chosen from a "bad" folder (but not moved or copied).
It seems that the folders get “poisoned” by some memory of the ghost images. But why only IrfanView sees a problem? All the same, IrfanView is a better viewer than any other Windows 7 viewer I have tried.
I hesitated to report this, until I saw problems in this thread that look familiar.
The error message says:
(File path and name): Can't read file header! Unkown file format, empty/damaged file or file not found!
Some JPG images do not open in IrfanView even though they open in: Paint, Windows Photo Viewer, Image Lounge, Canvas 11, etc. The JPG does open in IrfanView if moved or copied to the desktop. So this looks like a Windows issue, but why only IrfanView has a problem?
All the “problem” JPGs were copied from a Classic Mac computer via a MacOSX computer. Mac users may know that every file copied in this way arrives into Windows accompanied by a sort of “ghost” file (the classic Mac resource fork, split off). The ghost has the same name, with a “._” prefix. I copied around 6,000 JPG files in about 230 nested folders, then removed all the “._” files using TreeSize file search. Most of these JPGs are legacy scans from film camera days, so have no EXIF data. Those with EXIF were not edited in Mac OS and seem to open OK. An example is attached, chosen from a "bad" folder (but not moved or copied).
It seems that the folders get “poisoned” by some memory of the ghost images. But why only IrfanView sees a problem? All the same, IrfanView is a better viewer than any other Windows 7 viewer I have tried.
Attached Files
Comment