[Digikam-users] Problem with new hard disk containing existing images
sleeplessregulus at hetnet.nl
Sun Oct 9 17:50:17 BST 2011
Hi Stuart T,
If your new harddisk has the same name as the old one (let´s say
¨photo¨, one is mounted as ¨photo¨ and the other as ¨photo_¨, you can
see that in /media if that is your mountpoint. So maybe digikam did the
right thing, it depends on which one is mounted first. If only the new
drive has been mounted, digikam starts saying that it found the
collection but that the disk id has changed, and it can and will read
your new drive.
Op 09-10-11 18:09, Stuart T Rogers schreef:
> I am currently using Digikam 1.9 and today I installed a new hard disk
> for all my photos. I copied everything over outside of Digikam and
> then remounted the new hard disk in the same place as the old one was
> which contained the collections. The database was copied to the new
> hard disk as well. Just for the time being I also mounted the old hard
> disk at a new mount point so I could copy over anything I'd forgotten.
> On starting Digikam it promptly used the old hard disk at the new
> mount point without being told. I dont understand why since the new
> disk is mounted where the old one was. I use a complete hard disk for
> photos by the way which is an ntfs partition as it is shared with a
> dual boot XP install.
> Surely Digikam should have gone to the new hard disk in the original
> mount point!
More information about the Digikam-users