Talk:QuickPar

From Wikipedia, the free encyclopedia

"QuickPar is rather buggy. The app fails to repair the files that have been damaged. Usually several runs need to be performed to get it right. Tech Support will always blame the users hardware even if you are running a mission critical workstation that passes all known stress test and the machine remains in use 24/7.

The best and only hope appears to be using the command line tool instead."

Using it since years. Never expierenced any problems. Don't blame them.

[edit] BUGS

It's great that quickpar works good for you but others are having some trouble with it and the command line tool seems to be the best option. This information is crucial to people who are having trouble getting a large file to repair and are getting frustrated.

The bug I run into most is the one that par tells me the repair failed and the rars did not verify. This is a false negative because I can open the rars and extract the file and it will match the source md5. I have repeated this test numerous times and it occurs most of the time.

[edit] Rumours?

It would be helpful if bugreports -like the above- would be a bit more scientific. E.g. mentioning version number etc. How long ago is this? What are the steps to reproduce? Be more specific.

[edit] Reliability

Supposed issues with relibaility and bugs have no source sited. Problems with QuickPar failing to repair a volume have always come down to bad hardware (specifically RAM) in my personal experience.

Also claims about tech support are superfluous since QuickPar has no official tech support. As the article notes, no one "takes responsibility" (whatever that means) because QuickPar offers no warranty of any kind. Ryan Hobrock 18:42, 30 April 2006 (UTC)