RAR > PAR > RAR first

[glazed]

I will support this feature request.

I have a 40Mbit line on Giganews and rarely have to repair files.

My download server is a Synology NAS (CPU not the fastest). This results in the fact that a 4GB movie takes at least twice as long to parity check as it does to download.

So ... these scenerios would be perfect for me.

1) no errors: UNRAR
2) errors: UNRAR (fail) -> PAR2 repair -> UNRAR (succeed)

Couldn't this be implemented in a post processing script?

[glazed]

What do you think - should I go for the trunk - or Alpha5?

And on a scale from 1 to 10 - how stable is it? :-)