Reading official upgrade list I've found a very useful (my opinion) upgrade on DE.

Quote:

- Add saving bad files separately and automaticaly

I made so a little experiment with a disk with one damaged head. So after cloning try to save files .....off course many on them are corrupted.MRT have created a new folder "!Bad Flies" (.....I guess they mean "Files" ) but still empty.

So question is: .....have I misunderstood the meaning of "BAD FILES"? ....

I have saved files not copletely readed (contain some empty sectors,....also some contain bad sectors (red and black).No one of them was moved to BAD FILES folder.

Reading official upgrade list I've found a very useful (my opinion) upgrade on DE.

Quote:

- Add saving bad files separately and automaticaly

I made so a little experiment with a disk with one damaged head. So after cloning try to save files .....off course many on them are corrupted.MRT have created a new folder "!Bad Flies" (.....I guess they mean "Files" ) but still empty.

So question is: .....have I misunderstood the meaning of "BAD FILES"? ....

I have saved files not copletely readed (contain some empty sectors,....also some contain bad sectors (red and black).No one of them was moved to BAD FILES folder.

Is a bug o my fault? Someone have experienced same situation?

Hi, we have received your information.We can't get your meaning by your description, it is not clear.Please add our technical support Skype: service@mrtlab.com , he will check for you.

The best I could tell, they were files with bad sectors. Perhaps, if you have a head off, those sectors aren't being tagged as bad. Maybe you need to change the map of white, unread sectors to red and see if that makes a difference.

Basically, they should be considering all files bad and only consider them good if all the file's sectors are read. If they are doing it differently where they are only considering a file as damaged if it has read errors, it will result in a lot of false positives and consider files good if their sectors weren't read because a head was disabled. Sadly, I suspect that this is the case and it will likely take as long for them to fix it as it is taking for them to exclude the full task name from the front of directory path when saving files out to a destination drive.

The best I could tell, they were files with bad sectors. Perhaps, if you have a head off, those sectors aren't being tagged as bad. Maybe you need to change the map of white, unread sectors to red and see if that makes a difference.

Head is not set off, just unable to read (so produce all black and red sectors).Mi test files are different types: some are all black, some mixed green, red, black and white, some others have errors but not completely readed.

I'm sure some option make the difference ...........it seem no have any setting.

Anyway despite my experiments not any bad file will filtered.Waiting MRT support for clarification

Basically, they should be considering all files bad and only consider them good if all the file's sectors are read. If they are doing it differently where they are only considering a file as damaged if it has read errors, it will result in a lot of false positives and consider files good if their sectors weren't read because a head was disabled. Sadly, I suspect that this is the case and it will likely take as long for them to fix it as it is taking for them to exclude the full task name from the front of directory path when saving files out to a destination drive.

Well, Do You Not Think They Should Involve Some Of Us for beta testing their software i bet some of us are far better then their Chinese clients

Who is online

Users browsing this forum: Google [Bot] and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum