Probably an OSI Layer 8 failure..?

[icecat]

Hey,
found this great program and made it my usenet leecher no.1
Some features made me very lucky when I found them.
The first thing I went lucky about was of course the par2 checking option.
In my view it is for checking the complete files and repair them, if it is essential and possible.
The second great feature I found was the auto unrar to a different folder ability.
Great thing too.
Just let me say in short: If I activate each of these and give them the right foldernames and path, the complete file will be leeched but nothing else matters.. It remains in the first folder (download) and won't be checked or repaired or unrared.
The logfile says nothing at all.. No entry relating to this. Just the last leeched article and no more..

The last one I remarked was the following phenomen:
Everytime I put a .nzb into the folder, where the app automatically scans in, it will be recognized, put down in the queue and instead of removed (yes, it is checked on) a "cross" --> x is added to the filename..
So it remains in the folder and the next time the app scans for nzbs, it recognizes the "new" file with the "x" and put them down again in the queue..

Am I completely dumb or just not able to work with it?

It is a great app and I'm really _not_ acting the fool..

best wishes,

icecat

[Rdl]

Hey,
found this great program and made it my usenet leecher no.1
Some features made me very lucky when I found them.
The first thing I went lucky about was of course the par2 checking option.
In my view it is for checking the complete files and repair them, if it is essential and possible.
The second great feature I found was the auto unrar to a different folder ability.
Great thing too.
Just let me say in short: If I activate each of these and give them the right foldernames and path, the complete file will be leeched but nothing else matters.. It remains in the first folder (download) and won't be checked or repaired or unrared.
The logfile says nothing at all.. No entry relating to this. Just the last leeched article and no more..

You're doing something wrong. Are you sure you enabled par2 checking&repairing&unraring. Did you restart program after that? Maybe filepath+filename is hiting 255 char limit? If enabled small par2 file should be downloaded first. Does it shows in Par2 tab? If yes, after each file downloaded & decoded & checked it should show in par2 tab (be sure to 'uncover files' by expanding loaded small par2 file) After the whole par2 set is complete it will be unrared if enabled. If this helps you-great. In every case I'll post in help section explanation with pictures of whole downloading-checking-downloading missing blocks-repair-unrar process.

The last one I remarked was the following phenomen:
Everytime I put a .nzb into the folder, where the app automatically scans in, it will be recognized, put down in the queue and instead of removed (yes, it is checked on) a "cross" --> x is added to the filename..
So it remains in the folder and the next time the app scans for nzbs, it recognizes the "new" file with the "x" and put them down again in the queue..

This one is a bug. It's already fixed and will be available when new version is released. As a quickfix enable IMPORTED prefix under Setup/NZB (option requires program restart)

[Rdl]

See this topic for detailed explanation of par2/unrar function

[icecat]

Well, it definitely was a layer8 failure..
I'm very sorry for the misleading.
However thank you for your great help.
I ticked the

• import par2 files as paused so he fetched everything but not the files needed for check.

Now I get everything extraced and it works fine. Just a little question:

The rar and par files remain in the folder?
Yes, cleanup is ticked..

Best regards,

Icecat

[Rdl]

What is OSI layer 8 ?

I'm 99% sure it's again somehow again your fault. Did you restart program after ticking 'Cleanup after par2 repair' and ' Delete archives after successful unraring'. I pressume you don't download par2 recovery blocks by default?