How to stop bak files being created

[veritylmiles]

Hi,

I am having problems tagging images - when I select an image, Xnview creates a .bak file so that I am not able to tag the orignial image.

I have looked at previous questions about this on the forum but can't find a solution that works for me.

I have a lot of data - I am tagging about 500,000 images. Weirdly it worked fine for the first 300,000 and the problem has just started. I haven't changed any of the settings and have checked there are not errors on the hard drive. The images are not write protected.

Any help would be greatly appreciated, thanks!

[XnTriq]

Are the files in question write-protected/read-only, veritylmiles?

Related options:

• Tools → Settings… → General → File operations
  • Make backup for lossless flip/rotation
  • Make backup for lossless crop
  • Make backup for other lossless operations

Related topics:

• Creation of .bak and .xmp files during tagging.
• bak Files ???
• A strange file that creates .bak when categorized
• Stop Creation of .bak Files ???

[veritylmiles]

Hi,

Thanks for your reply.

None of the files are write-protected or read only.

I have unticked all of those options (Make backup for lossless flip/rotation, Make backup for lossless crop, Make backup for other lossless operations) but the problem still occurs.

What happens is I select a number of photos, tag them using the categories, then as soon as I click on to another image a .bak file is created for each of the images I just tagged. This bak file sits at the bottom of the folder so it takes me to the end of the folder and I loose my place.

Would love to find an answer to this!

Many thanks

[XnTriq]

I've not been able to reproduce this issue myself, but other users have. Maybe Pierre knows what's going on.

[BuckSkin]

Would love to find an answer to this!

Know that you are not alone in this and it is extremely annoying; I wish I could offer a solution, but I have not been able to find one myself.

My suggestion to the creators is to make a version that does not create .bak files at all.

It is most annoying to me when I am adding embedded comments and IPTC; if I am not very careful, I will be adding my information to the bak files and not the actual files.

I have been fighting this for a long time and have not found a solution yet.

If the bak files serve a useful purpose, I have not been able to find it, but they sure are an extreme annoyance.

If it is any help in your situation, you can change the format from .bak to .jpg and the bak file becomes a plain old jpeg.

[xnview]

what do you have in Settings>General>File operations & Settings>Metadata?
By tagging, you select a file and select a category in the categories panel?

[Bob_in_MA]

I have this same issue with vers. 1.3.1.

If I have more than one jpeg thumbnail selected, add categories for them (or edit previously checked categories), then click on one of the selected thumbnails , the .bak file is created. If I click on a file not among the thumbnails selected, no .bak file is created.

If I uncheck "Export Catalog's Category to XMp and IPTC", it does not create the .bak file. However, I would prefer to keep this feature on.

Is there a fix?

[xnview]

what do you have in 'Settings>General>File operations'

[Bob_in_MA]

Pierre,

I had already unchecked all the "Make backup...." boxes, but that had no effect.

[xnview]

i can't reproduce

- Settings>Metadata : 'export catalog category' is on, 'update sidecar' is off,
- select 2 jpeg files
- select 1 category
- click on first selected file => no .bak

[Bob_in_MA]

I have those same settings. It does not seem to ALWAYS happen, just most of the time.

Here is one more clue:
If under 'export catalog category' , 'Create XMP data' is unchecked, no .bak file is created, even if 'Create IPTC data' IS checked.

[Bob_in_MA]

I switched back to version 1.3 and that seems to work fine.

[xnview]

I switched back to version 1.3 and that seems to work fine.

could you send me your .ini

[Bob_in_MA]

Pierre,

I sent it earlier today....

[xnview]

Thanks to your detailed description I can reproduce the problem.