As DO doesn't show CRC or other errors when extracting RAR is there a way to handle RAR with DO (open in lister etc.), but use WinRAR automatically on extraction (copy in lister or drag'n'drop,...)?
If there's a CRC error while extracting a RAR then Opus should report it, and does in my own testing.
Why do you think it doesn't, and what are the steps to reproduce it?
On multipart-archives with corrupt parts DO cancels (and deletes) the corrupt file and leaves a standard message. But WinRAR shows - and that is the important thing - which part is corrupt and sometimes it's necessary to keep also the corrupt file(s).
You said Opus didn't show CRC errors, but if there is a CRC error Opus will show an error message telling you the file is corrupt. Showing a slightly different error message to what you want is quite a different thing to not showing an error message at all.
I don't think there is any good way to get what you want, but I don't understand why it's needed either.
If a file within an archive is corrupt, Opus will tell you, so there is no danger that you'll extract corrupt data without knowing. If you need to investigate exactly which part of a multi-part archive is corrupt, or you want to extract and keep the corrupt file, you might need to switch to WinRAR, but that is a rare thing, isn't it?
What are you doing where that happens often enough that it matters? Where are all these corrupt multi-part archives coming from (that aren't checked/repaired beforehand using .PAR2 or .SFV files)?
I had some crashes/CRC-errors because of faulty RAM (reported last week, if you remember), so some archives are corrupt. The only thing I want is showing the corrupt part name, which isn't included in DO's error message.
So there's a bunch of multi-part RARs, some parts might be corrupt, and you need to work out which parts are corrupt in order to re-download those parts?
I would find all the archives and then right-click them and get WinRAR to test them all in a big batch. That should get you a list of corrupt parts that need re-downloading.
Testing:
- takes nearly same time as extracting larger archives and
- its a step more getting an information that can be given while extraction process (and if succeeded no waste of time).
It would be helpful in general, not just because of the RAM failure.
But question was how to configure DO using WRar on extraction, but not when opening in lister. If possible.