<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I recently installed version 7.3.0 of Digikam as the first installation of Digikam on my computer. (In fact, I had just reloaded the operation system so it was a “clean” computer.)<div class=""><br class=""></div><div class="">Installation was apparently trouble free and I could manipulate photographs as expected, <b class="">until</b> I tried to add a new collection:</div><div class=""><ul class="MailOutline"><li class="">I wanted to view images in <i class="">C:/users/Public/Pictures </i><span style="font-style: normal;" class="">as a new collection but</span> I get an error message: “<i class="">It was not possible to add a collection for the following paths: C:/users/Public/Pictures</i> “. In fact I cannot add <i class="">any</i> collection of images stored on C:, always getting the same error message.</li><li class="">In fact, in the Collection configuration tool, the initial collection, which I had expected to appear as <i class="">C:/users/michael/Pictures </i><span style="font-style: normal;" class="">was in fact described as <b class="">D</b></span><i class="">:/users/michael/Pictures. </i></li></ul><div class=""><br class=""></div></div><div class="">On further investigation, I find that although my Digikam database files are created, as I specified, in <i class="">C:/users/michael/Pictures</i>, the Albums that are actually loaded during the initial configuration are stored on <i class="">another</i> disk <i class="">D:/users/michael/Pictures</i>. I have no problem in adding other collections stored on D: . </div><div class=""><br class=""></div><div class="">At this point I need to point out that when reloading my operating system I had retained a complete clone of the old OS and user files on a separate hard disk, on which the bootable partition now appears to Windows as D:.</div><div class=""><ul class="MailOutline"><li class="">In the Windows Disk Management utility, the disk containing the old clone (D: etc) is designated as <b class="">Disk 0</b>, while the disk with the new version of the OS (C: etc) is designated as <b class="">Disk 1</b>. (Disk 1 is also a Raid pair - though it appears to windows in every respect as a single hard disk.)</li></ul><div class="">Is it possible that Digikam collection configuration is miss-translating from drive letters with the assumption that Disk 0 will always be C: ?</div><div class=""><br class=""></div><div class="">Am I right in believing that this may be a bug rather than a “feature”?</div><div class=""><br class=""></div></div><div class=""><br class=""></div></body></html>