Photo Supreme

I just ran an import of a few hundred images, and two of them failed to import with the following error:

Copy failed for E:\DCIM\100EOS7D\0S5A7935.JPG with error Failed on copy Cannot create folder P:\Photo Supreme\2021\2021-05\2021-05-21\
Cannot create folder P:\Photo Supreme\2021\2021-05\2021-05 ...

This issue still seems to exist in V6. If I select "EOS_DIGITAL" for import, not only do the movies get left behind, some of the images don't import (see screen shots - e.g. 8Q7A7134.CR2). If I select the drive for my CF card, everything works like I would expect. Is this a bug or a feature? It ...

Hey all -

Sorry for the long hiatus. Work keeps intruding on life!

Here's where I am with the main issues on this thread. I think that I had two overlapping problems. The first, which was seen in the OP, was that my HDD-based database was struggling to keep up when I made lots of changes (import a ...

I deleted all versions of PSu from my machine and the registry keys. I then downloaded a new version of PSu 6. I told it to create a new database on a local Postgres server running on my windows machine (not the one I use normally for PSu). Then I told it to create another new database. Then I tried ...

I just created a new catalog. And then tried to exit PSu. Instead, I got an exception.


"Field not found"???? That should not be possible and if that field is missing in your database then yes, very strange things will happen and in that case I'm not surprised that you get crashes all the time ...

You can create a PostgreSQL backup as described in the Maintenance manual.


Restoring is also explained in the Maintenance manual.


OK, but if my database is corrupted, how I using pg backup and restore going to help? I was trying to use the PSu backup and restore. Are you telling me that ...

OK. So how does restore work at all? I have a backup from before all of this started happening. It's 50MB, so I think it is a real backup. But then when I create a new catalog and select restore, it just immediately pops up a window saying that restore is finished and that PSu will restart. Which it ...

First make sure you have a backup.

PSU keeps a "last resort" backup in the metadata, called the ICS (IDimager Core Schema). By default PSU is configured to write the ICS.

If you want to rebuild a catalog from the ICS then make sure that after creating a new catalog that you enable ICS reading ...

Well, back to verifying folders, and another poof crash. This one came with an exception report. Although unfortunately this looks like an after-effect of the crash rather than the cause. Looks like maybe heap corruption?

I just created a new catalog. And then tried to exit PSu. Instead, I got an exception.


So I killed PSu, restarted, opened the new, empty catalog, created another new one. And the same thing happened.

I have been super busy at work, so haven't gotten back here yet. I know about creating a backup of the catalog. But if I write everything out to the image files and then reimport them all to a new catalog, will all the information be preserved?

If I make sure everything is written out to the files, is there any other data or setting I need to save somewhere to make sure I don't lose anything?

Nothing in the logs at default logging levels.

Well, I just started a scan on the rest of the folders (2011 - 2021) and just came back and it has crashed. Do you run with Postgres on a separate machine? Is it possible the database connection is timing out and killing the process?

Finally was able to get back to this. First time I verified the 2004 folder, I got a poof crash when it was scanning for changes. The next time it scanned through the whole folder and presented me with the import options, and then started importing and died somewhere during that process. So I ...