Problems with large rar files in 0.28.4 and 0.28.5

[oblodo2]

I seem to have a problem with nzb files containing large rar files. (250 to 400 MB for each rar  total file size 6-8 GB) I run XP Pro SP3 have a Quadcore CPU and 4GB RAM. It seems that the process stops during par2 checking after the file has finished decoding. The nzb wil not be unrared and the following nzbs will then NOT be checked or unrared either. I have to manually unrar and delete the files from queue. After i restart and delete the "red" files, it runs fine for a few downloads. ( it works fine for all standard files, but I have downloaded a few 100 Criterion releases that have had HUGE (400MB) rar files and that is a problem...) Could it be that the program is not capable of using all cores of the CPU? On my older P4 3.2GHz decoding and unraring is twice as fast as on my Quadcore 2.4 GHz... 
It is not a huge problem, more of an inconvenience, but I am a huge fan of Alt.Binz so I hope you guys can help

[oblodo2]

Just to say that I have had the new par2.exe all the time, and I know it is supposed to utilize all cores...

My problem is only with decoding of huge files. It seems that since alt.binz is stuck at decoding, the repair and unrar can not start.

I tried NewsLeecher on one of the NZB files, and I had no problem at all getting the 7GB. I retried with alt.binz, and it stopped on decoding about 40% in to the download. All files got downloaded, I just had to manually unrar.

So I do think the problem is in alt.binz

I will continue to use Alt.Binz, but hope you sort it out.

[Rdl]

Just to say that I have had the new par2.exe all the time, and I know it is supposed to utilize all cores...

My problem is only with decoding of huge files. It seems that since alt.binz is stuck at decoding, the repair and unrar can not start.

I tried NewsLeecher on one of the NZB files, and I had no problem at all getting the 7GB. I retried with alt.binz, and it stopped on decoding about 40% in to the download. All files got downloaded, I just had to manually unrar.

So I do think the problem is in alt.binz

I will continue to use Alt.Binz, but hope you sort it out.

Be more specific. If the problem is in decoding you shouldn't be able to even manually decode??