Restart PL5 and add another keyword ‘B2’.Copy database (I would now use the ‘Create backup’ option).Add a keyword ‘B1’, ensure that is in PL5.The database housekeeping certainly needs attention, particularly if it is actually used as the sole repository if it is used for some or all keywords.
![restart photo mechanic trial mac restart photo mechanic trial mac](https://www.softwaretestinghelp.com/wp-content/qa/uploads/2021/01/How-to-Disable-Avast-Antivirus_.png)
One potential difference is that I have never used the backup and restore options (until I used the restore option today!) but I cannot see why that should change things!!?
![restart photo mechanic trial mac restart photo mechanic trial mac](https://home.camerabits.com/wp-content/uploads/2020/11/Plus_chart600.png)
So between us, and I suspect a lot of other users, we have “found” most(!?) of the issues with the installation process, although I am still puzzled why your installation did not default to your PL4 location. The installation defaulted to the PL4 location and appropriated the database as I stated in the post. John7 as I stated in my post above this did not happen to me in quite the same way. The issue of incompatible DOPs is just that and photo processing needs to be carefully managed while there is more than one version of PL or DxO installed! In PL5 restore the original PL4 database from the backup created by PL5 when first installed and run, at which point PL5 will transcribe the data from one database to another! Don’t panic when it appears to be hung (like I did), the bigger the database the more work it has too do! Running PL4 will object to the PL5 database that it finds and will revert to a new PL4 database.Īt this point it should be possible to restore the PL4 database using the restore option (selecting the PL5 created backup, which should be in the same directory) I then switched PL5 to use its own directory but I am not sure what I copied to the new directory at that time but there is a recovery database in that folder!? PL5 warns, creates a backup copy in that location and creates a new PL5 database. PL5 locates its database in the same location as PL4 on installation by default (I know of no option to change this default action). So I think that the situation goes like this
#RESTART PHOTO MECHANIC TRIAL MAC UPGRADE#
PL5 installation should have an option to select a new location for the database and an option to import an existing database into that location, performing the upgrade as required. Notwithstanding the fact that the situation can be recovered it should not be necessary. I then re-read platypus post and restored PhotoLab_1520-1.db in PL5 and selected restart and it “hung” sorry in the time that I was “fiddling” with this post the “hung” PL5 continued to work and I finally had the PL4 contents in a PL5 database! This does not auger well for those that use PhotoLabs as the custodian of their valuable keyword data! I then used the PhotoLab_1520-1.db (copied as PhotoLab.db) in the PL5 directory and PL5 started correctly but simply made the warning and threw away that database and created a new one!! However, looking at the PL5 directory it was clear that the PL5 database was too small so I repeated the exercise by copying the newly re-purposed PL4 database as the PhotoLab.db database in the PL5 directory and hung PL5 on startup (or so I thought)! I just copied one of the databases (PhotoLab_1520-2.db) in the PL4 folder back as the main (PL4) database and it seems to have restored things as they were for PL4 (albeit I was not concerned about the loss at this time).
![restart photo mechanic trial mac restart photo mechanic trial mac](https://cdn.fstoppers.com/media/2021/01/13/pmp_upload.jpg)
![restart photo mechanic trial mac restart photo mechanic trial mac](https://nektony.com/wp-content/uploads/2019/09/mac-touchpad-not-working.png)
The PL5 installation caused the same problems identified by AdrianW PL5 took over the PL4 database and upgraded it (allegedly) and when I ran PL4 (still my “production” version) I ran into the same database incompatibility problem. PL databases reside on the E drive in an appropriately labelled directory. I had the same problem when I installed the PL5 Trial on my main (Win 10) machine! I keep the “catalogs” created by the various bits of photo editing either on the F: drive (HDD) or the E: drive (Sata SSD). Database what database (or should that be which database)!?