You are not logged in.
Due to a large amount of fake accounts registrations for advertising purpose (spam), this forum does not accept new registrations any longer.
You can still browse existing threads to find the help you are looking for. If you do not find it and have questions, please use this contact form.
====================================
En raison d'un nombre important d'enregistrements de faux comptes utilisateurs à des fins de spam (publicité non sollicitée), il n'est désormais plus possible de s'enregistrer sur les forums de support technique.
Vous pouvez toujours parcourir les sujets existants pour trouver ce que vous recherchez. Si vous ne trouvez pas l'information et avez des questions, veuillez utiliser ce formulaire de contact.
When this happens are there any logs stored anywhere so I can figure out what happened?
Also, another question, which I think I may know the answer to. When Fab's skips over data is it because the source disk is damaged (bad sectors etc)? Can't really think of any other reason why data would be listed but then produce an error when trying to transfer
Thanks,
Offline
When this happens are there any logs stored anywhere so I can figure out what happened?
This could happen when a file's size changed between the time it has been listed for copy (its size was added to the total files size amount) and the time it has been copied. That can explain why there can be some glitches like that. This is not monitored anywhere since there is no error in the process.
Also, another question, which I think I may know the answer to. When Fab's skips over data is it because the source disk is damaged (bad sectors etc)? Can't really think of any other reason why data would be listed but then produce an error when trying to transfer
That is a reason. It can also skip files if they are in use while the program tries to copy them.
Fab
Offline
[ Generated in 0.053 seconds, 8 queries executed - Memory usage: 1.41 MiB (Peak: 1.58 MiB) ]