[100/200/300/400] File Manager for Networked Media Tank v 1.1.1 Beta - Released 25/1/2010

[Cherek]

Hi vaidyasr,

I wondered if it's possible some components of filemanager could conflict with NZBget?
The reason I ask this is because (when everything was still fine) I downloaded a DVD and NZBGet wouldn't unpak (using Oversight's unpak). I download everything directly to my ext. usb HDD.
In NZBGet's left upper frame on the main page, the free space is shown. ( It should now be about 250GB.)
Because of the unpak problem (a common chown refusal thingy) I thought I'd unrar the DVD using Filemanager. I didn't know I should leave my PC on during the process so after I turned it back on, from standby, I saw an error message from filemanager (stupidly enough I didn't copy it somewhere).
After some reading on the forum concerning unrarring, I read that an unrar process through an external location (I read it was a terminal so I derived it to be so for all external apps) needs the process starter to remain connected.

After I started up the NMT (A100) today I thought I'd give NZBget another try, since preciously a power off restart would fix the chown problem.
And eureka! It worked. But I saw something odd. In the upper left frame free space is 1,47 MB.
After checking all NZBGET settings, I can't find anything that has changed there.
The actual unrarring does happen on my ext HDD, and the files are there. But something is also using storage on my internal hdd (which is an old laptops 4 GB).

I had an older version of filemanager installed some time ago, but never tried to unrar. So it could be that the required utils is more than 2 GB?

But still that does not explain the fact that NZBGET isn't looking at my external HDD anymore for the size.
So could it be something filemanager has changed?
Thanks for your help!