"Guysu" <(E-Mail Removed)> wrote in news:1110297985.204400.149980
@g14g2000cwa.googlegroups.com:
> Then if you want to keep your information you could disable the update
> schedule for the files (options, index update tab) and update your
> index manually.
Hi Guysu,
Thanks for your reply.
Your method works but it prevents the index from being updated (you have
to do it manually). If I forget to do it, Copernic will take a long time
(CPU + IO) for updating the index. Moreover, as a lazy computer's user,
what I want to do is not caring about Copernic when I do not need to.
In facts, it is possible to make the difference between a removed drive
and a removed file.
In the "removed file" case, the file is removed from the disk but the
drive still exists in the system.
In the "removed drive" case, the drive does not exist in the system and
it makes the difference. I think removing all the removed drive's files
from the index is not really a good issue for Copernic since it has to
rebuild it again each time the drive is reconnected.
That is why I was asking if someone knew exactly what Copernic was doing
in such a case.
|