When big files are corrupted it take a lot of time to repair it, quickpar re-construct the repared file with the old one...If quickpar allow to select where you want to put the repaired file (on an other hard drive for exemple) it can speed up the task.
Bye!
Offline
This would be a great feature. "All" that is necessary is for Quickpar to create the new, repaired file(s) in a temporary folder, and then to copy the files from the temporary folder to the correct destination when the repair is complete - just before it does the final verification process.
A user would be able to customise the temporary folder, so that it is either on a RAMdrive or a second physical harddrive: in either case that would greatly speed up the repairing process and avoid a lot of wear and tear on the harddrive.
This approach could also provide half of the solution for users wanting to repair files off DVD-ROMs. The app would 'notice' that it is unable to copy the files from the temporary folder back to the source location and could either leave them intact in the temporary folder, or prompt for another destination.
Offline
I suspect it might actually be slower to move the files around like that (Windows would have to cache data in both locations).
If you're having speed issues:
- Check whether QuickPar is using 100% of your CPU time, because if it is, then there's nothing you can do to make it faster. Other then buying a faster CPU...
- If you're not seeing 100% CPU, maybe you need to defrag the drive that you're using to perform the repair on. Or you have other programs accessing the hard drive at the same time (which tends to kill performance with PATA and older SATA drives).
Offline
Bumping this topic.
This would be very helpful when repariing a rather large file (like HDTV movies topping 20GB) because if you can READ the files from one location and repair them to another (as in another physical drive) that would tremendously speed up the process.
I've been eagerly anticipating this feature as well. GREAT work so far - hopefully this will make it even better!
Offline
CPU is not at 100% at all the problem is an IO problem, not a CPU limitation.
Try on you computer with 2 hard drive :
- copy a file of 8 Go on the same disk
- copy the same file on other disk
The copy on the other disk is really twice faster because there is no head swapping.
Why do you think that you need 2 cache data?
Offline