Page 1 of 1

Error with 640B5

PostPosted: Wed Jul 11, 2012 2:22 am
by DaveXVI
I tried 6.40B5, and for every file I tried to download, I got an error like this:
[22:10:19] ERROR NNTPSpooler - NNTP_GetDownloadVector - Warning: Can't Create NB! Filename:(UnderC) [021/852] - "xxxxxxxxxxxxxxxxxxxx" yEnc

I got the same result whether I used the new element types in the download path name, or just a regular folder name. Reinstalling my old version fixed it.

Is there something we have to change in the spooling?

Re: Error with 640B5

PostPosted: Wed Jul 11, 2012 8:45 am
by Quade
It's basically saying it can't open the destination file to write chunks to. Probably because of the pathing. It's not clear why though. Are these NZB files?

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 2:02 am
by DaveXVI
No, they were just rar files. As I said, I tried it both with and without the new path placeholders.

Somewhere the description of the beta mentioned a visual editor for the paths, but I didn't see anything that showed me the final result. On the edit screen for the paths, there was a text box (going from memory, since I've uninstalled the beta) about a sample that I expected to show the result, but it remained blank no matter what I put in the path being edited (which only showed the $year type stuff, not the final result). Was there another place to see the actual path?

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 6:53 am
by Quade
Were you using UNC paths?

"\\Server\drive\"?

I'm looking for some difference between how you did it and I do it.

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 9:39 am
by DThor
Recently a user had a somewhat similar problem and after a bunch of back and forth it was determined the destination drive was removable and he would frequently detach and re attach the device. Anything other than a fixed local device is useful information out of the gate.

DT

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 3:14 pm
by DaveXVI
All of my drives are locally attached, although they are encrypted, so they have to be mounted with TrueCrypt before use. But that is done before starting Newsbin (in fact, the newsbin folders, including the executable, are all on encrypted drives, so it won't start unless the drives are mounted), and the encryption has been absolutely transparent to every program I've run for the last several years, including every version of NB.

The path I first used was K:\$nb640B5\$(GROUP)$(MONTH), where K: is a local (encrypted) drive. I formed the path using the edit tool in the options panel to insert the new placeholder names. When I got errors with that, I thought maybe it was because the tool didn't put a backslash between the last two components, so I added that, to get K:\$nb640B5\$(GROUP)\$(MONTH). And when *that* didn't work, I just went back to K:\$nb640B5\, which is the format I have always used (with the switch set to append the name of the newsgroup). That didn't work either, but it worked after I reinstalled the old version.

Just now I tried it again -- reinstalled B5, left the path alone so it said "K:\$nb34b5\$(GROUP)\", tried to download a small rar file, and got
[11:25:41] ERROR NNTPSpooler - NNTP_GetDownloadVector - Warning: Can't Create NB! Filename:xxxxxxxx.rar

Reinstalled the old version, removed the $(GROUP)\ from the download path, worked fine.

OS is Win7-64, all critical updates applied.

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 3:33 pm
by Quade
Pretty sure the problem is the $ at the beginning of the path.

K:\$nb640B5\$(GROUP)$(MONTH)

I'd try it without the dollar sign. I'll check the code out too.

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 3:43 pm
by DaveXVI
Quade wrote:Pretty sure the problem is the $ at the beginning of the path.

K:\$nb640B5\$(GROUP)$(MONTH)

I'd try it without the dollar sign. I'll check the code out too.


That was it! I should have thought of that. Thanks.

Re: Error with 640B5

PostPosted: Thu Jul 12, 2012 3:57 pm
by DaveXVI
Please disregard the post that was here before.

I thought that the new path feature had broken something in the "Download to New Folder" feature, but it turned out that I was downloading from a completely new group, so I didn't have a base folder for it to start from.