WIN XP SP2 problem

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

Moderators: helmut, XnTriq, xnview

Post Reply
Guest

WIN XP SP2 problem

Post by Guest »

With XnView 1.70.4 set as default image application and when
double-clicking an image file in Windows Explorer ...

- using Win98SE on my old machine XnView started
like it should, and displayed the image OK;

- using WIN XP Pro SP1 on my new machine brought up
the Windows Image and FAX viewer which displayed
the file. There was an edit button which brought up
XnView and the image but I didn't find a way to bypass the
Windows Image & FAX viewer;

- using WIN XP Pro with SP2 newly installed on my new
machine brings up XnView which displays the image;
however, on the top there is an alert box saying (wrongly)
"Windows cannot find 'path\filename'. Make sure you typred
the name correctly and then try again'.

(I don't have any problem bringing up a 3rd party text editor
(Crimson Editor) for .txt files.)

Is there a fix? Thank you, Steven Gibbs.
Lostclown
Posts: 99
Joined: Thu Jul 22, 2004 12:21 am
Location: Iceland

Post by Lostclown »

I think this is related to the fact that the default action for images in XP is "preview", but not "open".
Try to rightclick an image from Windows Explorer and select open to verify this. Then your would either have to make open the default action or associate XnView with the preview action.

I believe there are others on this forum that can help you with this, as this has most likely come up before,

Regards, Lostclown
Guest

Post by Guest »

Thank you for the tip. I found the problem was with PNG images, JPG images opened OK (I didn't try other kinds). I edited the PNG file association dialog to exactly match the JPG dialog and now PNG comes up OK without the unwanted alert box.

Regards, Steven Gibbs.
User avatar
xnview
Author of XnView
Posts: 46362
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: WIN XP SP2 problem

Post by xnview »

Anonymous wrote:Is there a fix? Thank you, Steven Gibbs.
I've fixed the problem in 1.74
Pierre.
Post Reply