Corrupted file handling

Ask for help and post your question on how to use XnView Classic.

Moderators: XnTriq, xnview

Post Reply
lawndart
Posts: 51
Joined: Sun Sep 19, 2004 4:03 pm

Corrupted file handling

Post by lawndart » Wed Feb 09, 2005 11:22 am

Edit: Please skip this post and read post below instead.

I downloaded a jpg that would not appear in preview window.
Right click plus menu select open results in Warning dialogue saying:
'corrupted file' (I only tried this because of problem, I normally use
keyboard shortcuts and full-screen for everything when possible).


Hitting enter from browser launches 'corrupt' jpg in another program
(web browser -IE) associated with jpg instead of Xnview as expected.
So, this problem jpg file is handled 2 different ways under Xnview.
I don't think it should be passed on to any other program to launch.

If Xnview is associated with jpg and problem file is selected from browser,
then warning box is displayed and then an unwanted 2nd instance of Xnview
browser remains.

When Xnview is un-associated with jpg after this, then launching problem
jpg no longer gets passed on to IE as before but will get passed onto whatever
program is newly associated with jpg files.

Problem jpg is skipped when it is among a directory of files being viewed
in viewer-full-screen mode.
Last edited by lawndart on Tue Feb 15, 2005 12:47 pm, edited 1 time in total.

User avatar
helmut
Posts: 8153
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Re: Corrupted file handling

Post by helmut » Mon Feb 14, 2005 9:51 pm

lawndart wrote:...
Problem jpg is skipped when it is among a directory of files being viewed
in viewer-full-screen mode.
A bit hard to follow your long description and to reproduce your problem. I assume that you have activated the setting "Use shell context to open picture" in "Tools > Options > Browser". After activating this setting, I can see a difference in behaviour.

In the XnView browser, at least one image (thumbnail) is selected:
a - when selecting "Open" in the context menu, XnView will show the image in XnView.
b - whereas when hitting "Enter", a second instance of XnView will open and show the image.

So yes, I can confirm that there is a difference. But I'm not sure whether this is a bug or feature: I think the intention is that people still can view their images in XnView even if they have activated the setting "Use shell context to open picture".

lawndart
Posts: 51
Joined: Sun Sep 19, 2004 4:03 pm

Post by lawndart » Tue Feb 15, 2005 12:12 pm

Yes, my first post was too confusing. Allow me to
rephrase.

Without 'use shell context to open picture' checked, shell context
is still used to open corrupt jpgs when <enter> is pressed in browser mode.
(I assume this applies to any corrupt file. This might be a way for problem
files to cause mischief, considering the many patches issued to IE/WinOS).

Selecting problem jpg with right click open, or menu>tools>open shows
"corrupted file" warning box. Since reinstall of Win2k, I'm no longer
seeing a second instance of browser appearing after this warning box (which
was a problem before).

lawndart
Posts: 51
Joined: Sun Sep 19, 2004 4:03 pm

Post by lawndart » Tue Feb 15, 2005 3:21 pm

Similar to 'corrupt file jpg' problem above, a non-jpg file renamed to jpg
produces similar results:

1. Turn off 'use shell context to open picture'
2. Turn off scan headers in folders.
3. Rename text file to text.jpg
4. Look for text.jpg in browser mode.
5. Right click open displays: 'Format cannot be determined' warning box.
6. Click in browser or enter in browser always opens file using shell
context.

User avatar
helmut
Posts: 8153
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Post by helmut » Tue Feb 15, 2005 8:57 pm

lawndart wrote:Similar to 'corrupt file jpg' problem above, a non-jpg file renamed to jpg
produces similar results:

1. Turn off 'use shell context to open picture'
2. Turn off scan headers in folders.
3. Rename text file to text.jpg
4. Look for text.jpg in browser mode.
5. Right click open displays: 'Format cannot be determined' warning box.
6. Click in browser or enter in browser always opens file using shell
context.
Thank you for your very clear desription, I could easily verify your problem. I have no real good explanation for this behaviour and can't tell whether this is an intended feature or a bug. Perhaps Pierre knows.

Post Reply