Auto-Unrar stops

[superJ]

out of interest try this.. once a unrar gets locked. try go into altbinz/setup/misc/misc#2 and alter any of the priorities then press "ok"
see if it pops up "thread handle is invalid (6)"

This I can confirm! It's the same with me.

But I found the sucker.
Because I got it after a clean start to unrar smothly and selectet then one after another option in the  Setup Menu. And between every step I unrared something. It worked fine until I selected: Setup > NZB > "Autoimport NZB files from folder" (in my case C\AAA). Then the unrar stopped again. I don't know why, but this is for shure, the strange behaviour with the stopping of the Unrarprozess is only there if I select the "Autoimport NZB from folder"

The Problem is: I love the Autoimport function. So, Rdl, if you could fix this (or tell me what I could do) - it would be verry apreciated.

[Rdl]

out of interest try this.. once a unrar gets locked. try go into altbinz/setup/misc/misc#2 and alter any of the priorities then press "ok"
see if it pops up "thread handle is invalid (6)"

This I can confirm! It's the same with me.

But I found the sucker.
Because I got it after a clean start to unrar smothly and selectet then one after another option in the  Setup Menu. And between every step I unrared something. It worked fine until I selected: Setup > NZB > "Autoimport NZB files from folder" (in my case C\AAA). Then the unrar stopped again. I don't know why, but this is for shure, the strange behaviour with the stopping of the Unrarprozess is only there if I select the "Autoimport NZB from folder"

The Problem is: I love the Autoimport function. So, Rdl, if you could fix this (or tell me what I could do) - it would be verry apreciated.

Heh, that makes sense. Do you have in autoimport folder rar file without any nzb inside?

[superJ]

I don't know, if I understand your question right... The Folder in which I download my nzb's and autoimport from is C\AAA\
I have "Delete NZB File after importing" checked - so, yes, usualy there is no NZB File in this folder (only if just downloadet and not yet importet).

[Rdl]

Possibile solution in 0.27.0 Please test and respond if the problem is solved (I cannot reproduce the problem)

[SirTristen]

I would unrar without scanning for virusus anyhow..no problem with me

[superJ]

Possibile solution in 0.27.0 Please test and respond if the problem is solved (I cannot reproduce the problem)

No. With 0.27.0 the same stopping of the unrarprozess apears. :-(

Any other Idea?

[Rdl]

Could you, temporary,  turn off autoimporting and see if the problem is still there.

[superJ]

Could you, temporary,  turn off autoimporting and see if the problem is still there.

Like I said above, if I do this, the Problem does not apear.

But I played again a little bit around and I can circle in the Problem now a whole lot more: Ususaly I have, like I said above, autoimported my nzb from my usual Download-Folder (C\AAA\). To be not misunderstood: THIS IS NOT my alt.binz Download Folder, but the Folder where I store everything my Browser Downloads. So my NZBs. And all the other stuff, like updates of Programs ect. If I turn autoimport from this folder on - the Problem apperars. If I turn it off - it does not appear.

BUT - AND THAT'S THE NEWS! - if I change my autoimport Folder for the NZBs (I took the ususal ...\alt binz\nzb\), turn autoimport on, put some nzb in this folder and unrar something out of alt.binz - no problem aPpears. It autoimports the nzb and unrar flawless at the same time.

That leads me to the conclusion, that the bug must have something to do with the autoimport out of an Folder where not only nzbs are stored. What is strage, because I had never this Problem before - until I updated from 0.25.0 to 0.26.9 (and I always autoimported bevor from the same folder, where all the other stuff is stored).

I hope this helps to fix this bug. My workaround will be to look up, how I can teach my firefox to download only nzbs to an extra folder. But it would be very cool If you get this fixed.

[superJ]

Any News on this Topic?

[Rdl]

Any News on this Topic?

It's hard to fix something you can't reproduce COuld you come to #alt.binz@EFnet so you could try few test versions. It would go faster that way.

[superJ]

Any News on this Topic?

It's hard to fix something you can't reproduce COuld you come to #alt.binz@EFnet so you could try few test versions. It would go faster that way.

Shure. But I have to konfess, that I realy don't know anything about mirc. What do I have to do, to come to #alt.binz@EFnet ? And how do I find the Test-Versions there?

[Rdl]

Any News on this Topic?

It's hard to fix something you can't reproduce COuld you come to #alt.binz@EFnet so you could try few test versions. It would go faster that way.

Shure. But I have to konfess, that I realy don't know anything about mirc. What do I have to do, to come to #alt.binz@EFnet ? And how do I find the Test-Versions there?

You have to install an irc program (try mIRC), connect to any efnet server and "/join #alt.binz" When you're in the channel, contact me and I'll prepare test versions for you to try.

[squidgy]

Just to say I have the exact same problem since moving to 0.27. I also use autoimport and have specified the default NZB folder as a subfolder of the autoimport folder. I've now switched off autoimport to see if it resolves the problem.

[MajesticJG]

I have the same problem in 0.28.1 and haven't been able to solve it yet.

I'm hoping for something new to try!