Author Topic: Problems with going portable  (Read 2370 times)

bobnick

  • Guest
Problems with going portable
« on: September 01, 2010, 04:52:41 am »
Hi,
I have been using Altbinz 0.25 on and off for some time (currently on Windows XP SP3).  I don't use it a great deal as I have Easynews and their HTTP interface serves the majority of my binary downloading

Recently, I have been trying to get Altbinz to work on a portable drive (using the Zip file download), however I have not been able to get relative paths working properly to negate the problems associated with driver letter changes.

I tried all the usual ways of entering relative paths eg.

"\documents\altbinz\downloads\" (i.e. the absolute path with the drive letter and colon removed)
also
"..\..\documents\altbinz\downloads\" (altbinz was two levels down the directory tree from root)

I even tried just leaving the directories in the default locations and thus used
".\download\"

Note: I have the option "Create subfolders based on NZB/root node name" enabled.

In each of the above cases using relative paths for the NZB and Temp folders seemed to work properly, however, for the download folder Altbinz would create the NZB named subfolder but would not decode files to it -  the downloads were stuck in "decoding" status.   

If I then changed the path back to absolute eg. "D:\documents\altbinz\downloads\"  the decoding would restart so file name length not seem to be a problem.

Altbinz seems to recognize the relative path otherwise it would not create the subdirectory in the right place but why it will not decode to that directory has me puzzled.


Any help would be much appreciated.

Regards,
Confused