|
|
Post by thewalker on Feb 14, 2022 20:43:08 GMT
Due to the size constraints of my C drive, I was able to move my image files from C to J drive successfully, PSE 2018 functioned perfectly, all was fine. Decided to upgrade to PSE 2022, the install itself went well, installation asked to convert catalog which I responded with YES, this resulted in catalog image referencing C drive, this is not correct, all images are stored on J drive.   |
|
|
|
Post by michelb on Feb 14, 2022 21:29:51 GMT
Two correct ways to move image files folders to another drive: - in the organizer, by drag and drop of the master folder in 'tree mode' to the new drive. - by a full backup and restore on the new drive. (Not likely, your catalog folder would have been restored on J) .
Which one did you use?
Is your PSE2018 still installed and functioning well with the pictures in J ? The PSE1018 catalog is still on C, renamed with a 1 suffix.
If you uninstalled it, did you make a full backup of the catalog before installing PSE2022 ?
Did you try to 'reconnect' missing files? For instance the '2007 12 05' folder by guiding the reconnection to the same folder on J ?
|
|
|
|
Post by thewalker on Feb 14, 2022 22:54:09 GMT
Hi Michel,
With respect to the first two question, no to both, all I did was install pse2022 and said yes to "convert existing catalog".
PSE2018 is still installed but referencing Huk Photos.
I have a current catalog backup of PSE2018.
|
|
|
|
Post by michelb on Feb 15, 2022 7:12:48 GMT
Hi Michel, With respect to the first two question, no to both, all I did was install pse2022 and said yes to "convert existing catalog". PSE2018 is still installed but referencing Huk Photos. I have a current catalog backup of PSE2018. How did you 'move' the files from C to J before attempting the conversion ? If you have used another method involving using an external tool than the organizer (the explorer, a backup or sync utility, a cloning utility...) please describe in more details. What is interesting for troubleshooting is to understand what can explain that the conversion process does not identify your drives correctly.
|
|
|
|
Post by michelb on Feb 15, 2022 10:36:54 GMT
There is no move of files in the conversion process to a new version. There is an identification process of the drive by Windows. How does Windows identify the drive?
This is not shown in any of the usual Windows tools such as the Explorer or the disk manager. You have to start a 'command prompt' to open a command line Window like in the old DOS time...
Right click on the Windows 'start' button, bottom left, and select the 'command prompt' line (invite de commande in French) In the Command prompt Window, type the command 'Vol C:' or 'Vol J:' to get the internal serial number of the drive referenced by Windows. The result is displayed in hexadecimal format.
In the internal organization of the catalog database, the location of every file is given by two chunks: the drive identification (the above hexadecimal value translated in decimal' plus the full path (the folders and subfolders hierarchy). In the conversion process, the organizer reads the drive identification and concludes that it corresponds to the C: drive. Why 
One reason may be that for Windows there is a confusion between C and J. If they have the same identifier, the organizer is lost. And that can be the result of a cloning of an old conventional drive to a new small SSD drive which copies the identifier. So, it's important to know what has been done to the drive before the conversion attempt.
|
|
|
|
Post by thewalker on Feb 17, 2022 21:39:21 GMT
I had a look around the hard drives and could not really point a finger at the issue but the ProgramData/Adobe/Elemants Organizer/Catalogs had many obsolete catalogs, might have have referenced one of these when asked to convert existing catalog, deleted those not relevant.
Rebuilt the catalog, tedious, but worked. All appears OK
As always, thank you for your response.
|
|
