IDimager

Stephen wrote: ↑

18 Oct 17 4:51

WIll this work properly if files are first copied from the memory card to another drive and then imported into PSu from that new location?

For PSU the source file is whatever you point it to. For those files the archive flag is set after copying with PSU's Import Module.

PSU uses the archive flag of your files to determine the initial marked state. After copying a file to your system then PSU alters the archive flag of the original file on your memory card. Could it be that you made the memory card read only or any other possible reason why the archive flag of a fil...

Psu calls the external app, passing the file to it.

How that app handles a passed on file is up to that app and not something that PSU controls.
Make sure you report to them that a passed on file is not handle the way you expect it to.

In general the rule is: if you know what you're doing then certainly use it. You should be safe using vacuum, reindex or backup using pgadmin.

You can disable metadata writing by keeping the metadata in the catalog only.

Some of the categories are used by PSU and can't be deleted. You can Rename them though. Still, even after a rename they still serve the purpose they are designed for.

I think you're mainly waiting for the file system. You may want to disable auto-sync to file and sync manually when convenient. If you're reading from files then you'll have to bit the bullet once to get everything read into the catalog database.

This message does indicate a malformed database file. Make sure to compact your database regularly, typically once a week. At this point that will probably also give you the malformed message. If your backups are also malformed then Restore a backup that is not malformed or start a new database and ...

You should be able to copy the 2 catalog files to the new machine. Of course your hard drive is different and so PSU will consider the images in the old catalog to be offline. To point to the folder on the new computer, open FOLDERS, right click on the top node, select “map to the correct physical f...

Can you also provide the screenshot that Stephen asked for?

Also, you keep using the word "Flag", but what is a "flag"?

When using PSU's backup and compact then users will be affected by that as the database will need to be locked. Compacting on the PostgreSQL or SQLServer version is not that relevant. You could do without. For backups, use the PostgreSQL or SQLServer backup facilities for real-time backups.

Stephen wrote: ↑

29 Sep 17 12:12

Perhaps you could supply a screenshot to illustrate what you are trying to do?

And a screenshot of your Sync-Write and Sync-Read settings

This is a PSU message. The Free Text Service is one of the services inside PSU. It makes sure that you can search for “stuff”. Not sure why you’d get such an error from it.

I just tried it here...the XML returned by G+ is "Insert is no longer supported"...which PSU tries to handle but which obviously is no valid XML, hence the error message that you get. Looks like Google killed their service and made it read-only now.... You could ask them about it. Consider switching...

Ah, sorry for that...long live auto correct.
I mean "lowest level" (the folder containing images)