<html><head></head><body><div>For UUID's in windows, have a look at:<br><br><a href="https://www.howtohaven.com/system/change-disk-signature.shtml">https://www.howtohaven.com/system/change-disk-signature.shtml</a></div><div><br></div><div><br></div><div><span></span></div><div><br></div><div>On Sat, 2021-08-07 at 11:08 +0100, Michael McEllin wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Thanks for the advice - I guess cloning the disk may be the root of the issue. However, defining the collections as network shares did the trick. So I will probably leave well alone until I have another reason for reformatting disk.<br></div><div><br></div><div>Mark this one “customer satisfied” with very prompt and relevant guidance.<br></div><div><br></div><div>Michael <br></div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On 6 Aug 2021, at 22:20, Maik Qualmann <<a href="mailto:metzpinguin@gmail.com">metzpinguin@gmail.com</a>> wrote:<br></div><div><br></div><div>I don't know exactly where the error is without a DebugView log file from <br></div><div>digiKam.<br></div><div><br></div><div>Two things:<br></div><div><br></div><div>Virtual folders are be used under Windows to move the image folder from C: to <br></div><div>another drive. digiKam does not support virtual folders, you always have to <br></div><div>specify the physical path.<br></div><div><br></div><div>It can happen that the drive UUID of the drives C: and D: are the same, then <br></div><div>digiKam cannot distinguish the drives. Either format a drive, it then receives <br></div><div>a new UUID or change the collection to a network collection in digiKam <br></div><div>settings, then only the path is used for identification. <br></div><div><br></div><div>Maik<br></div><div><br></div><div>Am Freitag, 6. August 2021, 12:37:53 CEST schrieb Michael McEllin:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>I recently installed version 7.3.0 of Digikam as the first installation of<br></div><div>Digikam on my computer. (In fact, I had just reloaded the operation system<br></div><div>so it was a “clean” computer.)<br></div><div><br></div><div>Installation was apparently trouble free and I could manipulate photographs<br></div><div>as expected, until I tried to add a new collection: I wanted to view images<br></div><div>in C:/users/Public/Pictures as a new collection but I get an error message:<br></div><div>“It was not possible to add a collection for the following paths:<br></div><div>C:/users/Public/Pictures “. In fact I cannot add any collection of images<br></div><div>stored on C:, always getting the same error message. In fact, in the<br></div><div>Collection configuration tool, the initial collection, which I had expected<br></div><div>to appear as C:/users/michael/Pictures was in fact described as<br></div><div>D:/users/michael/Pictures.<br></div><div><br></div><div>On further investigation, I find that although my Digikam database files are<br></div><div>created, as I specified, in C:/users/michael/Pictures, the Albums that are<br></div><div>actually loaded during the initial configuration are stored on another disk<br></div><div>D:/users/michael/Pictures. I have no problem in adding other collections<br></div><div>stored on D: .<br></div><div><br></div><div>At this point I need to point out that when reloading my operating system I<br></div><div>had retained a complete clone of the old OS and user files on a separate<br></div><div>hard disk, on which the bootable partition now appears to Windows as D:. In<br></div><div>the Windows Disk Management utility, the disk containing the old clone (D:<br></div><div>etc) is designated as Disk 0, while the disk with the new version of the OS<br></div><div>(C: etc) is designated as Disk 1. (Disk 1 is also a Raid pair - though it<br></div><div>appears to windows in every respect as a single hard disk.) Is it possible<br></div><div>that Digikam collection configuration is miss-translating from drive<br></div><div>letters with the assumption that Disk 0 will always be C: ?<br></div><div><br></div><div>Am I right in believing that this may be a bug rather than a “feature”?<br></div></blockquote><div><br></div><div><br></div><div><br></div><div><br></div></blockquote><div><br></div></blockquote></body></html>