Uploading to ABMS

NOW - to the UPLOAD part. I am trying to do like in this guide:
http://www.djm.org.uk/ngguide/

But now I'm a bit lost. The guide is for uploading an AVI file, while I try to upload a folder containing a VIDEO_TS folder for the dvd #1 of a set.
When I right-click the folder and choose "Add to" and the folder name, a WinRAR archive is made (eventually).

I don't, though, see this next part in the guide happening: "
Now after that's done you should be left with a set of RAR files of your movie...". I just see the archive.

PS: In the WinRAR compression settings I chose "Normal" instead of "Store" (that the guide recommends for an AVI file) as I figure video_ts files could use compression on the usenet server?!
Are all the RAR files in ONE file due to the compression?

When I then open QuickPAR, following the guide and do "add files", I seem to only be able to select the WinRar FOLDER (= one archive file), and not the individual RAR files.
OK, now I try to do "Create", and it is making PAR2 from just ONE - 1 - file: Must be the archive I can see/open. No individual RAR files. Judging from the source file size, the whole DVD 1 is likely in there.
Or have I done something wrong??

I have now created par files, and run "verify" and Quickpar says "No repair needed".

Should I post this, when I don't see all the RAR files in a list?
Original Post
Originally Posted By: kajsa89

I don't, though, see this next part in the guide happening: "
Now after that's done you should be left with a set of RAR files of your movie...". I just see the archive.


So you just have one file? You've missed a step - "split to volumes, bytes" needs to have 50,000,000

Quote:
PS: In the WinRAR compression settings I chose "Normal" instead of "Store" (that the guide recommends for an AVI file) as I figure video_ts files could use compression on the usenet server?!
Are all the RAR files in ONE file due to the compression?


No, choose store. DVD is also compressed.

Quote:

When I then open QuickPAR, following the guide and do "add files", I seem to only be able to select the WinRar FOLDER (= one archive file), and not the individual RAR files.
OK, now I try to do "Create", and it is making PAR2 from just ONE - 1 - file: Must be the archive I can see/open. No individual RAR files. Judging from the source file size, the whole DVD 1 is likely in there.
Or have I done something wrong??


Sounds like it. When you have the 90 or so rar files, Open quickpar and navigate to the folder that they are located in. Click on the first rar file, and shift-click on the last. That'll select all the rar files. Then follow the guide. 5% is fine for a DVD. I usually use 3% and never had a complaint. OK, maybe I did once. Don't bother with the SFV file.
Originally Posted By: Pete
Originally Posted By: kajsa89

I don't, though, see this next part in the guide happening: "
Now after that's done you should be left with a set of RAR files of your movie...". I just see the archive.


So you just have one file? You've missed a step - "split to volumes, bytes" needs to have 50,000,000


First I set to "Normal", then I tried once more with "Automatic". There's no slternative for 50,000,000 or any other number, so I must define one manually.

Thanks so very much for you fast reply!
Originally Posted By: kajsa89
I get this pop-up box in PowerPost when I attempt to upload:
"441 Posting failed. You are not allowed to post!"

Why not??


Make sure you are allowed to post through your news server. For some news servers, you have to set your account up to post. Typically it is a setting in your account or you may have to send an e-mail to the news server company requesting posting priviledge. It all depends on the news server.

Also you may have to post to a different dns name for posting.

Who is your news server??

*****

NOT DO, DEAD - Dr Sung Park - from the TNT Show Monday Mornings

*****

Thanks for directing my attention in that server direction!
It is:
Easynews.com

I found the needed info in the Member FAQ there. Thanks.

EDIT: I got uploader status pretty instantly. Seems I am now posting this: "1978-09-19 Passaic NJ - Turnpike version Masked and Redubbed - authored and song chapters - DVD 1"
WHEN ADDING A FILE/FILES TO QUEUE IN YENC-Power-Post, what will be the practical consequences for the DOWNloader of checking or not checking these under "CHECKSUMS"?:

- "Generate .SPV file"?
The tutoral says "do one", while Pete above said "Don't bother with the SFV file."

- "Generate .PAR file"?
Already done in QuickPar, so why here?

- "Generate .PAR2 file"?
Already done in QuickPar, so why here?

- "Generate .NZB file"?
Something to do with finding the files even if using a different server than me? I have checked this for most of my uploads so far, but don't really know what I'm doing...


Typically you only want PowerPost to generate the NZB.
Originally Posted By: kajsa89
WHEN ADDING A FILE/FILES TO QUEUE IN YENC-Power-Post, what will be the practical consequences for the DOWNloader of checking or not checking these under "CHECKSUMS"?:

- "Generate .SFV file"?
The tutoral says "do one", while Pete above said "Don't bother with the SFV file."
Pete is right of course. Nobody here uses it. It's an old system that a few die hards use, but par2 does everything it does, and it's one more file to worry about if it goes missing. No need for it.

Originally Posted By: kajsa89
- "Generate .PAR file"?
Already done in QuickPar, so why here?
par is the older, obsolete version - you want only par2 files.
Originally Posted By: kajsa89
- "Generate .PAR2 file"?
Already done in QuickPar, so why here?
If it's already done, exactly. They added in this feature so people could skip the QuickPar step, but it had some problems at one time and I'm not sure it's maintained as well as QuickPar is. Safer to stick with QuickPar.

Originally Posted By: kajsa89
- "Generate .NZB file"?
Something to do with finding the files even if using a different server than me? I have checked this for most of my uploads so far, but don't really know what I'm doing...
It's good to do an NZB file. What it is, is a list of all the files in the set. So someone can download the NZB file and use that to queue up the file set. It's especially useful in really busy newsgroups. And there are various services to let people find the NZBs without having to wade through a big newsgroup. More info on the web, but -- good to do one.
Thanks SO much, buzzy!

Speaking of PAR2:
What kind of function has the file that is only named *.PAR2 above all the RAR files as compared to the PAR2 files such as *.vol000+01.PAR2 that follows the RARs?

Q about WinRAR and the function to "Split in volume, bytes" (translated from Norwegian, not sure if this is the exact wording in the English version):
Pete told me he usually defines 50,000,000 bytes, so I have done that regardless of the size of the upload. Are there any guidelines for how many bytes are recommendable for an upload of so-and-so many GBs?
guide you've mentioned says

"The purpose of the volume being split is so that its easily posted and downloaded from UseNet and missing blocks can be easily repaired using QuickPAR PAR2 archives, just posting the full 700MB is not acceptable. 15,000,000 is ideal for files from 150-2100MB after that you may think about increasing the size to 20,000,000 or in the case of uncompressed DVD Rips 50,000,000."
Originally Posted By: kajsa89
Speaking of PAR2:
What kind of function has the file that is only named *.PAR2 above all the RAR files as compared to the PAR2 files such as *.vol000+01.PAR2 that follows the RARs?


The smaill PAR2 file doesn't contain any blocks to repair a damaged file, but it does have the ability to test your download for errors. Saves your bandwidth.

I always download the PAR2 file first,and it should always be posted before the main files. Run the PAR2 file while you're downloading, and tick the "Monitor" box. This will automatically check your download as it's progresses, saving you some time.
Originally Posted By: BigRay5264
guide you've mentioned says

"The purpose of the volume being split is so that its easily posted and downloaded from UseNet and missing blocks can be easily repaired using QuickPAR PAR2 archives, just posting the full 700MB is not acceptable. 15,000,000 is ideal for files from 150-2100MB after that you may think about increasing the size to 20,000,000 or in the case of uncompressed DVD Rips 50,000,000."
It made sense to use smaller files with par - when all the files (rar and par) had to be the same size. 1 recovery block was one file back then, so you didn't necessarily want big files if you could avoid it, because even a one byte error would take a whole par file to repair.

But with par2 there's no reason to use anything smaller than 50 MB at this point, and 100MB is fine too. One bad spot in a file can be fixed with one small par2 block, it doesn't need a whole par file. So really the only considerations are minor ones - how many files you want to end up with. Less files (bigger size) is better, mostly. Unless your goal is to billboard the newsgroup with your posting.

If you really want to do it right, use a file size that an exact multiple of the par2 block size. Eg, 7000 lines x 128 bytes / line = 896,000 bytes. x 100 = 89,600,000 bytes. Doesn't matter much, though.

Just a reminder, it's important to make sure the number of lines in QuickPar and the number of lines in PowerPost are set to the same number!! 7000 or so is good. That is far more important than the file size.
Originally Posted By: buzzy

Just a reminder, it's important to make sure the number of lines in QuickPar and the number of lines in PowerPost are set to the same number!! 7000 or so is good. That is far more important than the file size.


Where in QuickPar and PowerPost may line number be set? I don't see it. By now, I only hope my uploads are correct..

What are the consequenses if the number of lines are NOT the same?
In Powerpost - View>Program Settings>Program>Default Max Lines per part >

Using a Quickpar Blocks size of 480,000 bytes/128 = 3750 or 960,000 bytes/128 = 7500

7500 lines per part * 128 bytes = 960,000 bytes
3750 lines per part * 128 bytes = 480,000 bytes per block

If you miscalculate you will need slightly more than 1 PAR2 block for each missing part. (EFFICIENCY)
-----------------------------------------------------------------
http://quickpar.co.uk/PostingGuide.htm
Getting the block size right

PAR2 files should work perfectly well no matter what block size you choose, but some values for the block size will be much more efficient than others.

It is strongly recommended that you choose a block size that is either equal to or an exact multiple of the article posting size which you plan to use with your news-posting software. When you do this, a single missing article will only require the use of one block of recovery data for repair. If the block size is not an exact multiple of the article size, then it is highly likely that downloaders will need to fetch two recovery blocks to repair one missing article. This means that they are forced to download twice as much recovery data.

NB Many news services do not propogate very large article sizes. Virtually all services handle article sizes up to 500KB in size and most handle articles as large as 1MB. You should set your news posting software and the block size in QuickPar appropriately.

QuickPar lets you set your preferred article size in the Options dialogue for both UUEncode (based on 45 bytes per line) and yEnc (based on 128 bytes per line). Commonly used values include 3000 lines for yEnc (giving a block size of 375KB) and 8000 lines for UUEncode (giving a block size of just over 351KB).

You should also ensure that the "Restrict block size to multiples of UseNet article size" checkbox is ticked.
-----------------------------------------------------------------

<<<INSERT BUZZY COMMENTS HERE>>>

*****

NOT DO, DEAD - Dr Sung Park - from the TNT Show Monday Mornings

*****

Thanks. One more:
In Powerpost - View>Program Settings>Program>
should one tick "auto-detect PAR2 block size"?


Quote: "QuickPar lets you set your preferred article size in the Options dialogue for both UUEncode (based on 45 bytes per line) and yEnc (based on 128 bytes per line)."
Well, it also lets me define "Exact".

Which alternative will one be better off choosing, then:
- yEnc?
- UUEncode?
- Exact?


PS: "Restrict block size to multiples of UseNet article size" checkbox HAS INDEED been ticked.
Originally Posted By: kajsa89
Thanks. One more:
In Powerpost - View>Program Settings>Program>
should one tick "auto-detect PAR2 block size"?
no, just set it once to whatever you're using in QuickPar and leave it at that forever.

Always post using yEnc, it cuts the upload and download size by a lot.
Originally Posted By: kajsa89
Thanks, this was interesting: http://quickpar.co.uk/PostingGuide.htm
The author of QuickPar and I went over some things when par2 first came out, and he incorporated some comments into that page. But it's meant to apply to all kinds of newsgroups - so for ABMS, it's better to follow the advice you get here, because:

- some of the things that were issues when par2 first came out aren't so much any more ... nobody should be using a newsreader that can't download incomplete files.
- subsequent testing showed that bigger files work fine.
- some of what's there doesn't apply so much to us - file splitters, for example.

The people who post to ABMS have done it as well or better than anybody for as long as I can remember, going back to when I first heard about ABMS - Pete, Shabby, bobsmo, etc.

To ASTRAWEB users:
1.How many lines do you use in order to avoid ""441 Article too big"-ish error message? See quote below.

2. How big parts for storage do you define in WinRAR to fit to line number?


QUOTE from the FAQ:
"The default is 1950 for yenc powerpost (11b) and many EXPERIENCED posters leave at that. If you wish to play around with this setting, we can only say that we've tested it up to 3000 with success. With any higher value, you will risk your post being rejected by our servers if not by other servers when your post propagates out to the rest of the world."
Originally Posted By: kajsa89
To ASTRAWEB users:
1.How many lines do you use in order to avoid ""441 Article too big"-ish error message? See quote below.

2. How big parts for storage do you define in WinRAR to fit to line number?


QUOTE from the FAQ:
"The default is 1950 for yenc powerpost (11b) and many EXPERIENCED posters leave at that. If you wish to play around with this setting, we can only say that we've tested it up to 3000 with success. With any higher value, you will risk your post being rejected by our servers if not by other servers when your post propagates out to the rest of the world."


Could someone comment on this, please? Seems Astraweb recommends max 3000-ish lines? When I've tried to post to Astraweb with the 7000 lines setting, it says it is too big. Due to the longer retention period at Astraweb, I'd like to post there rather than to the one I use (Easynews).
Guess I will try an upload with 50 MB size with 3000 lines. Huh?
Every usenet message is essentially a text file that is converted into a binary file by your news reader. Ergo alt.binaries. Each of these text files is made up of a number of lines.

It barely makes any difference what you choose. The smaller the number the more segments you'll upload, so there's a higher chance that one will be missing when downloaded, but otherwise...
Originally Posted by ABMS Guardian:
Originally Posted by kajsa89:

"Failed: Recovery block checksum mismatch": what is the practical significanse of this? Will it be ok to upload anyway?

ABSOLUTELEY NOT


OK. I will get back to this in (minimum) two weeks. I am leaving for vacaton tomorrow. Any idea what is the problem/ solution?

Originally Posted by kajsa89:
Originally Posted by ABMS Guardian:
Originally Posted by kajsa89:

"Failed: Recovery block checksum mismatch": what is the practical significanse of this? Will it be ok to upload anyway?

ABSOLUTELEY NOT


OK. I will get back to this in (minimum) two weeks. I am leaving for vacaton tomorrow. Any idea what is the problem/ solution?

It sounds to me the PAR2 files are corrupted.

Originally Posted by IvanNF:
Originally Posted by kajsa89:
Originally Posted by ABMS Guardian:
Originally Posted by kajsa89:

"Failed: Recovery block checksum mismatch": what is the practical significanse of this? Will it be ok to upload anyway?

ABSOLUTELEY NOT


OK. I will get back to this in (minimum) two weeks. I am leaving for vacaton tomorrow. Any idea what is the problem/ solution?

It sounds to me the PAR2 files are corrupted.

I did it like I have always done it...(?).
I have rebooted since last time, though, so I will check the properties once I get home.

Likes (0)
×
×
×
×
×