B4: Crash when opening print dialog
Moderators: XnTriq, helmut, xnview
Closer to a path to reproduce:
The good news is it's linked to the printer.
On my desktop at home (XP-SP2/Epson RX500 whatever on or off) I can reproduce 99% (see bellow). If I change the default printer to Windows FAX, I can't. Just switching from one printer to the other, open Xnview select a picture, print button and crash /or see the dialog.
On my personal laptop (XP-SP2, HP 710 not connected) I can't trigger the crash.
Apparently it has nothing to do with repository (I agree with Helmut's remark: Desktop isn't virtual). I tried in All users...\documents\temp. also in C:\Support. No noticable influence.
Nothing to do with either the size of image, the Qty of image, the mixup with video clips, image having metadata or not. Same reaction. Now I use the folder with the 4 samples provided with XP.
How to:
- Set the "bad printer" as default,
- start Xnview and select a folder (samples),
- close Xnview, restart it after a few seconds,
- select pictures and print button,
To see the print dialog after a crash:
After restarting Xnview select another folder, select on or more picture and click the slideshow button. Close the slide dialog, select pictures again and print button. Sometime, just changing the folder you can print.
Additional remark: On my desktop, if I start XnView from a new unzipped, the current view is always the XnView' folder from where it started (Xnview 1.84 is installed on that and use the .ini file). On my laptop, a new package shows the last folder browsed during my last trial (Xnview 1.84 never been installed on this PC). From where does it retrieve the path !?
Hope this helps, regards,
Daniel
The good news is it's linked to the printer.
On my desktop at home (XP-SP2/Epson RX500 whatever on or off) I can reproduce 99% (see bellow). If I change the default printer to Windows FAX, I can't. Just switching from one printer to the other, open Xnview select a picture, print button and crash /or see the dialog.
On my personal laptop (XP-SP2, HP 710 not connected) I can't trigger the crash.
Apparently it has nothing to do with repository (I agree with Helmut's remark: Desktop isn't virtual). I tried in All users...\documents\temp. also in C:\Support. No noticable influence.
Nothing to do with either the size of image, the Qty of image, the mixup with video clips, image having metadata or not. Same reaction. Now I use the folder with the 4 samples provided with XP.
How to:
- Set the "bad printer" as default,
- start Xnview and select a folder (samples),
- close Xnview, restart it after a few seconds,
- select pictures and print button,
To see the print dialog after a crash:
After restarting Xnview select another folder, select on or more picture and click the slideshow button. Close the slide dialog, select pictures again and print button. Sometime, just changing the folder you can print.
Additional remark: On my desktop, if I start XnView from a new unzipped, the current view is always the XnView' folder from where it started (Xnview 1.84 is installed on that and use the .ini file). On my laptop, a new package shows the last folder browsed during my last trial (Xnview 1.84 never been installed on this PC). From where does it retrieve the path !?
Hope this helps, regards,
Daniel
And do you have problem with 1.82.4?B.Douille wrote:Closer to a path to reproduce:
The good news is it's linked to the printer.
On my desktop at home (XP-SP2/Epson RX500 whatever on or off) I can reproduce 99% (see bellow). If I change the default printer to Windows FAX, I can't. Just switching from one printer to the other, open Xnview select a picture, print button and crash /or see the dialog.
On my personal laptop (XP-SP2, HP 710 not connected) I can't trigger the crash.
Could you try to search xnview.ini on your disk?Additional remark: On my desktop, if I start XnView from a new unzipped, the current view is always the XnView' folder from where it started (Xnview 1.84 is installed on that and use the .ini file). On my laptop, a new package shows the last folder browsed during my last trial (Xnview 1.84 never been installed on this PC). From where does it retrieve the path !?
Pierre.
Never seen with this version.xnview wrote:And do you have problem with 1.82.4?B.Douille wrote:Closer to a path to reproduce:
The good news is it's linked to the printer.
On my desktop at home (XP-SP2/Epson RX500 whatever on or off) I can reproduce 99% (see bellow). If I change the default printer to Windows FAX, I can't. Just switching from one printer to the other, open Xnview select a picture, print button and crash /or see the dialog.
On my personal laptop (XP-SP2, HP 710 not connected) I can't trigger the crash.
There is a big difference when I uses these PCs, which is the user level: On the desktop I always work as a standard user whereas on the laptop I uses administrator account. I tried to use admin account on the desktop too and I was unable to trigger the crash so the problem is probably linked to access rights.
I've got 10th due to alpha and beta packages still on my desktop But it's linked to user level. With a standard account Xnview do not start in the previous folder.xnview wrote:Could you try to search xnview.ini on your disk?B.Douille wrote: Additional remark: On my desktop, if I start XnView from a new unzipped, the current view is always the XnView' folder from where it started (Xnview 1.84 is installed on that and use the .ini file). On my laptop, a new package shows the last folder browsed during my last trial (Xnview 1.84 never been installed on this PC). From where does it retrieve the path !?
I think we should forget this remark for the time being and concentrate on the crash itself.
All shared printers are available for users?B.Douille wrote:There is a big difference when I uses these PCs, which is the user level: On the desktop I always work as a standard user whereas on the laptop I uses administrator account. I tried to use admin account on the desktop too and I was unable to trigger the crash so the problem is probably linked to access rights.
Send me a email, i'll send you a debug version...
Pierre.