This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
In all reality, performance is the same; personally, I would just keep it set as "quick removal" so that you don't think it's done, yank it out, and then get corrupted files.
In all reality, performance is the same; personally, I would just keep it set as "quick removal" so that you don't think it's done, yank it out, and then get corrupted files.
I concur, write caching just gives the illusion of better performance. All it does is write the data to volatile memory before it writes it to disk.
What this means:
The copy window that you see will disappear a lot faster, but it's not done yet... It still has to write it to disk, which is the *actual* action you want to take, and still takes the normal amount of time (Or possibly even longer)
For example, if it normally takes 30 seconds to copy a file, with that option enabled, it may appear to only take 10 seconds... So you're free to copy another file. But it still has 20 seconds left before it finishes the copy, so if you unplug the device before the full 30 seconds, that file is now corrupt.
With Windows 7, you can copy multiple files to the same destination (Which you couldn't before, I think it may have been included in Vista as well) so I would just get them copying, leave the "Quick Removal" option on, and unplug it when it's finished... That way you can be sure it's done.