Page 1 of 1
Question about Suppress read errors
Posted: Tue Aug 30, 2005 6:19 am
by orcatron
I have a rather basic question about read errors. Say I want to set up a slide show of a folder full of .jpg files. If, in the Options panel, I turn off the "Supress read errors" box, none of the .jpg files I have will open. The slide show just repeatedly shows an error window stating "Format of the file <C:\sample\.001.jpg> could not be determined". This is an example, with the file name and path varying for each file. If I turn on the "Suppress read errors", the slideshow works just fine.
Other file viewers and browsers have scattershot reactions to the jpg files I have; some of them just show them all without comment, others won't display them at all, and some (like XnView) will display them but will comment about errors if you set options certain ways.
I think XnView is handling this issue just fine. It's just that I want to know what errors these are. Also, I'd like to know if there is a simple way to just batch fix these errors without significantly changing the picture, which might be an issue with a bunch of pictures with varying levels of compression.
Re: Question about Suppress read errors
Posted: Tue Aug 30, 2005 7:04 am
by xnview
orcatron wrote:I have a rather basic question about read errors. Say I want to set up a slide show of a folder full of .jpg files. If, in the Options panel, I turn off the "Supress read errors" box, none of the .jpg files I have will open. The slide show just repeatedly shows an error window stating "Format of the file <C:\sample\.001.jpg> could not be determined". This is an example, with the file name and path varying for each file. If I turn on the "Suppress read errors", the slideshow works just fine.
Other file viewers and browsers have scattershot reactions to the jpg files I have; some of them just show them all without comment, others won't display them at all, and some (like XnView) will display them but will comment about errors if you set options certain ways.
I think XnView is handling this issue just fine. It's just that I want to know what errors these are. Also, I'd like to know if there is a simple way to just batch fix these errors without significantly changing the picture, which might be an issue with a bunch of pictures with varying levels of compression.
Could you send me a sample?
Posted: Tue Aug 30, 2005 5:44 pm
by Guest
After having puzzling problems reproducing the issue with the pics outside of the folder they were in, I began fooling around and trying many things, and finally discovered what the real issue is.
In Windows, I tried to Select All in the folder to copy them to another folder, and it told me there are as many invisible files in the folder as there were pictures. So I went to Folder Options and turned on see invisible files, and discovered that all of the files (example, 001.jpg) have an invisible duplicate with a period in front of the name (example, .001.jpg). These invisible duplicates are all 82 bytes in size. XnView is not able to open these files, and returns the error I quoted above in my first post.
I am assuming these are separate thumbnails created by one of the several picture viewers/organizers I have been trying out recently. When I attempt to do a slideshow with XnView on this folder, it sees these invisible files before it sees the normal files, and returns errors on those invisible files before it gets to the real files (which XnView can open just fine, even in slideshow).
Unfortunately I haven't been able to figure out which program created these separate thumbnail files. None of the programs I have now seem to be doing it, so I guess it's just an issue of going through and deleting all those invisible files.
Posted: Wed Aug 31, 2005 5:40 am
by orcatron
Final bit of info: I looked at one of those 82 byte files with notepad and noticed the text "JPEGogle". This reminded me that I had copied these folders from a MacOS 9.x volume, and so those little invisible files are resource forks.
So I used Agent Ransack to find all the files in those folders that started with a period, deleted them and the problem is solved.