Author Topic: yEnc decoder issue caused by folder name  (Read 4706 times)

Offline al3x

  • Contributor
  • ***
  • Posts: 23
yEnc decoder issue caused by folder name
« on: December 03, 2007, 07:29:00 PM »
i tried to download some yEnc encoded files today.

the download folder was named by the nzb file and contained these chars:
a-z, A-Z, space and some special chars: . [ ] - @

total number of chars: 157

the download was started and completed. but the decoding-process only showed "Decoding" and didn't start.
so more and more files completed and weren't written to disc correctly.

after some hours the whole program finally crashed.

there seems to be a bug in the yEnc decoder module..

later on i manually renamed the folder to something simple and short and redownloaded everything.
now the decoding process completed and files appeared.

so there seems to be some problems with the yEnc decoder ???

thx,
alex ;)
« Last Edit: December 03, 2007, 07:42:51 PM by ch4os »

Offline Rdl

  • Administrator
  • *****
  • Posts: 3938
Re: yEnc decoder issue caused by folder name
« Reply #1 on: December 06, 2007, 12:00:25 PM »
it seems to me that this belongs to category 'long path+filename' and currently it isn't handled well by alt.binz.

Offline al3x

  • Contributor
  • ***
  • Posts: 23
Re: yEnc decoder issue caused by folder name
« Reply #2 on: December 06, 2007, 06:58:28 PM »
i think it's related to the yenc decoder as well. some small files like .nfo etc. were stored correctly in the same folder.
but all yenc files couldn't be decoded.

the path wasn't too long imho, 24 chars for the usenet folder and another 157 for the subfolder...
maybe it failed because of the "@" in the path?

whatever... no problem at all as long as i rename the subfolders, so don't worry about this too much :D

Zeikzeil

  • Guest
Re: yEnc decoder issue caused by folder name
« Reply #3 on: December 06, 2007, 07:33:52 PM »
The '@' character in a path shouldn't be a problem. If you say there was a .nfo file in the folder do you mean the folder with the @ character in it or a parent folder?
Please try to be as specific as possible. The more info Rdl has the easier it is for him to get to the problem ;)

Offline al3x

  • Contributor
  • ***
  • Posts: 23
Re: yEnc decoder issue caused by folder name
« Reply #4 on: December 06, 2007, 08:19:44 PM »
If you say there was a .nfo file in the folder do you mean the folder with the @ character in it or a parent folder?

why should a .nfo file get stored alone in a parent folder? ;D
it was stored in the correct subfolder of the current download... so there was a .nfo file and some other small files which weren't encoded with yEnc, all in the destination folder. the main files (the rar archive) couldn't get decoded and remained in the temp folder of altbinz.

Offline Rdl

  • Administrator
  • *****
  • Posts: 3938
Re: yEnc decoder issue caused by folder name
« Reply #5 on: December 06, 2007, 08:31:43 PM »
You're wrong if you think that .nfo file and other 'small' files aren't encoded with yenc when posting. I bet rars had longer name then then those files so they've hit 255 char full path limit.

Offline al3x

  • Contributor
  • ***
  • Posts: 23
Re: yEnc decoder issue caused by folder name
« Reply #6 on: December 06, 2007, 08:41:59 PM »
You're wrong if you think that .nfo file and other 'small' files aren't encoded with yenc when posting. I bet rars had longer name then then those files so they've hit 255 char full path limit.

you're right. they were encoded as well.
but i'm sure they didn't scratch the 255 char limit.

maybe the limit for yenc is below that?