Resuming incomplete files which show up as completed?

[imune]

I've downloaded some rar files of 66 MB size each. Although all of them appear as complete on the server

Code: Select all

Selected posts:	1
Total parts:	371
Available parts:	371 (100%)
Parts with bodies:	0 (0%)
Size:		66 MB

two only came out with these sizes:

part2.rar 850 KB (!)
part3.rar 45 MB


Curiously enough the files are not marked as incomplete or having an error, there's no question mark on them, they appear as regular deleted headers. Is there any way to resume download to complete a file or is this impossible since it's already been decoded? And how come there are no errors?

[alex]

you just mark for download the deleted headers, they will be undeleted automatically.

but the result most likely will be the same try to save attachments without deleting article bodies and if you get the same result check in the parts mode what is wrong with individual parts, maybe some kind of spam or the server returned corrupted bodies.

[imune]

Unfortunately you were right. Even after downloading headers and only then saving attachments manually, the resulting file is 35 MB instead of 66.

I can't remember whether I've used ALT+D or ALT+SHIFT-A, in any case when I select properties on said header it shows again "Parts with bodies: 0 (0%)". Does this mean that after decoding this rar it's headers have been deleted again? And how do I check in parts mode?

Yesterday on my first try of downloading those headers my speed was very slow so I assumed that a new try today at full speed would return things to normal. Unfortunately I was wrong. In case it might help, here's one of the headers:

Code: Select all

Part: (1/371)  Message-ID: <70c29$44fbc79d$55b06bef$8618@news.usenext.de>

[alex]

file menu->default toolbar->show parts

you can open individual parts in the article view to see what is wrong

i cannot find the file by message-id, but i can e.g. get it through search service given the subject

probably you can see in the headers with which poster program has been used to make the post.

but in the first place just try to download bodies to see whether all bodies are available at your server. the trivial reason is maybe they are not.

default settings in UE in such a case is to download available parts and then to save attachments and delete headers ignoring errors, you can change it in properties->articles->saving attachments by unchecking "delete incomplete bodies", too many users were complaining about increasing database directory, in short to have the option checked was the only way to go for newbies.

if not all parts are available the resulting size of the attachment will be less than the one you see in the header properties, so it needs par2 recovery or you need to find those missing article bodies elsewhere.

if you press "space" (download only, not save) if all parts are available you'll see the green notepad icon in the end, if there are errors you'll probably see half green notepad icon with question sign (see explaining icons topic in the selected help topics area on the web page). you can see the error in the articles error pane in the task manager or in the header properties (context menu->properties) - most likely "no such article".

[imune]

properties->articles->saving attachments by unchecking "delete incomplete bodies"

LOL, I already unchecked the setting with the incomplete bodies.

I've switched over to parts view and all 371 parts of each rar were shown as regular parts, there was no question mark or anything. Doing a properties on any part came up with

Code: Select all

Subject: Numb3rs_Staffel1_komplett.part003.rar (368/371)
Author: Power-Poster@power-post.org (Hoover2)
Date: Mon, Sep 04 08:51
Message-ID: <4ddc1$44fbcce7$55b06bef$8618@news.usenext.de>
Newsgroup: alt.binaries.tv.deutsch  (regular, compact binary)
Dests:	All newsgroup servers (compact binary newsgroup)

Accidentally I double clicked on one part which of course started downloading again which I cancelled. Naturally the headers of this particular rar were no longer marked as "deleted" and showed up in the main view of that newsgroup again. However, I only got to see the 1 part I double-clicked on, the remaining 370 do not show up anywhere?

From what I understand all parts ARE there on the server, they just don't get downloaded completely. Unfortunately I cannot use the par files to fix the incomplete files because I'm only interested in the first file of that multipart rar which approximately spans accross rars 1-5. To rebuild em with pars I would have to download all 93 rars + the corresponding pars which is too much for trying out a TV show I missed when it aired.

[Josef K]

Code: Select all

Subject: Numb3rs_Staffel1_komplett.part003.rar

Try a different server or tweak your settings - maybe something was overlooked. This file saved with the correct size for me and verified fine with the par2.

[alex]

imune:

after you download all parts.

do you see all parts with cyan notepad icon?

so when you invoke context menu->properties on the partial (green nodepad icon) you see 100% parts have bodies?

also when you expand partial in the parts mode you don't see any duplicate parts like

(2/371)
(2/371)

then it could be some kind of spam but it is not likely since UE service would list duplicates as well if they were at at least one of three header feed news servers and it is not the case.

since josef was able to download this file the post itself is ok.

thus it might be your server (then try a different server to see whether it is the case) or if you experience the same problem with all downloads it might be something on your computer like firewall corrupting incoming stream.

if you expand the partial in the parts mode and (given you downloaded all parts) you open part sources you may find what is wrong if it is half size every second part on average is a kind of corrupted, with yenc posts you should be able to see headers, then yenc begin on the top and yenc end at the bottom of every article source (article source you can open from article view, context menu).

if you see something wrong some parts are corrupted on your server.