not@home.com wrote:
>Milf Lover how do you post a group of files easily
>
>I have trouble posting more than one at a time
>
>Hef
>
>heflarue@gmail.com
Hi Hef,
The poster you are replying to is an advertising robot, so
will never respond to your message. However, here is a
helpful excerpt from the FAQ over at the short-hair group,
which may answer some of your questions...
Q. How do I read/post messages?
A. You need a newsreader program, sometimes called a "client".
There are many Usenet clients out there, some free and some
for sale. If your web browser comes with an email program,
then it probably can also read newsgroup messages. Outlook
Express comes with Microsoft's Internet Explorer, and the
Firefox web browser comes with Thunderbird, which can handle
both email and newsgroup messages.
The major drawback of these "integrated" newsgroup message
programs is that they don't handle binary files attached to
messages very well. For decoding binary file attachments,
a stand-alone program is much more useful.
If you try a standalone newsreader client, make sure that it
can handle yEnc files, or your tasks will be more difficult.
Unfortunately, clients that are great for text messages are
often poor for binary files, and clients that handle files very
well are often difficult to use in managing text discussions.
The best solution is to use one program for files, and another
one for text messages.
For a free program to manage files, I recommend XNews which
is easy to begin with and very versatile after you get familiar
with it. For managing text discussions, Forte made a free
version of their Agent newsreader client, called Free Agent.
Free Agent is now discontinued, but it can still be found on
the internet, with the help of a search engine.
The noteworthy Useneteer "mjello" says this:
"Many people end up using two newsreaders, one for
downloading binaries and one for discussions (Xnews
is free and does that well)."
He also has a handy list of useful websites about Usenet clients:
http://www.binaries4all.com/
http://www.slyck.com/Newsgroups_Guide
http://www.usenetmonster.com/infocenter/articles/usenet_binaries_tutorial.asp
When you get some more experience with Usenet and want to try
sending a file, the best choice is Power Post 2000.
Q. Can you help me use Power Post 2000?
A. Yes. Here are some tips for using PP2K...
Very easy to use... but the sounds in the program are
incredibly annoying, so click View -> Program Settings
-> Program tab, and uncheck "Play Sounds". Under the
same tab, set your "Default Max Lines Per Part" to 2,500
to 3,500 for yEnc encoded posts, or 5,000 to 7,000 if you
use UUEnc instead. Why? Because lines in a yEnc message are
twice as long as UUEncoded lines. Using 3,200 lines for
a yEnc encoded post is a very good idea.
This is how the subject header displayed for a sample post:
Short hair at the beach [20of20] "bch_1152.jpg" yEnc (1/1) 27.8 Kbytes
To get that subject header, I used this PP2K header format:
Short hair at the beach [$1of$2] $K$F
"Short hair at the beach " is a short description
"[$1of$2] " inserts the file number and file count
"$K$F" inserts the filename and the size in Kilobytes
You must include "$F" in the header, and for best results
you should NEVER type anything after the $F. The version
of PP2K I use also adds "yEnc" to the end of my posts,
and puts quotes around the filename. With other versions,
you may have to add "yEnc" manually. Why? Read below.
The early requirements for yEnc encoding specified that
the word "yEnc" appear in the subject, and there should
be quotes around the filename. These are now options,
no longer required, but are still a nice thing to do for
two reasons... first, "yEnc" alerts the viewer that it's
a yEnc encoded file, in case their system requires them
to do something differently when they download yEnc files.
Secondly, putting the filename in quotes allows it to be
decoded correctly by older, early-generation yEnc software.
If you wish to send a 0-part text message, to describe
your post, click the tab in PP2K to "prefix 0/N text".
Make sure to send it with "First File Only", not "All Files".
One reason that PP2K is the standard for posting binaries
is that it allows you to do segment fills. Not important
for small pictures, but if you're posting a larger file that
PP2K splits up into 45 segments, and only 44 make it to your
server, you can choose to repost only the missing segment
instead of the whole file.
To repost a single segment, you right-click the file on PP2K's
main screen and a list of actions pops up. choose "Re-Queue
Selected Files". Then right-click the file again, and choose
"Task Properties..." In the posting box that pops up, click
the button to "Uncheck all", then check the box(es) next to
the segment(s) you wish to repost, then click the "OK" button.
Now just post the file as normal, and only the segments
you have chosen will be reposted. Now when you refresh the
list of headers in your client, your post should be complete.
Q. Why use yEnc encoding for binary files, instead of UUEnc?
A. Simply, yEnc encoding makes files 30% smaller on the Usenet
server than the UUEnc encoding scheme. They are still the same
size when decoded back into JPG or AVI files, but yEnc files
can be uploaded and downloaded 30% faster than UUEnc. Smaller
storage demands on your service and faster downloads means that
your news service is more likely to hold all the posts in a
newsgroup for a longer time.
YEnc files can be easily decoded by using a modern newsreader
client, like Agent, XNews, NewsBinPro, or NewsGrabber.
Forte's Free Agent newsreader has been discontinued since
version 4.0 came out, but a Google search will turn up places
where Free Agent can still be downloaded. Free Agent supported
yEnc files after version number 1.93.
The most common problem that people have with yEnc encoded files
is when using Outlook Express as a newsreader client. As mentioned
above, OE is very poor at dealing with binary files. If you must
use OE, get a yEnc decoder for Outlook Express to enable you to
decode the files seamlessly. yDecode has a free version which
will enable you to do most of what you need to do and the paid-for
version (30 US$) will do it all. yProxy is similar although it has
no free version, but costs only 20 US$.
http://www.ydecode.com
http://www.yproxy.com
Q. Should I include thumbnail "contact sheets" for previews?
A. When posting a set of picture files, this is optional. Some
people appreciate being able to see what a set is all about in
one glance, so those people might appreciate a preview sheet.
For pictures that are reasonably small files individually, it
is often just as easy to preview a set by downloading a few of
them. When posting a set of large high-resolution pictures,
a preview sheet of thumbnails is more useful, since each picture
may be several megabytes in size. Another method to help others
with large image files is to convert a sampling of files down to
a smaller size, and post those as previews.
When posting a large multimedia file, including a picture preview
is always a great help to the downloader. Always strive to do so.
Q. Should I include a parity set with a post?
A. As with preview pictures, this is more helpful with large
video files than with sets of pictures. It is customary among
most newsgroups to include a 5% to 10% parity recovery set with
a large video file, but not as common to post parity sets with
picture files. It's always a nice thing to do, but not a
requirement.
A good tip for making parity sets is to use QuickPar, and set your
parity block size to be the same size as your posting program's
segment size. For instance, in QuickPar the default block size is
384,000 bytes. In PP2K I set the number of lines per segment to
3,200. That's yEnc lines, which are twice as long as UUEnc lines,
so for a UUEnc encoded posting program, I would set the number of
lines to 6,400 (2x lines, since the lines are 1/2 as long, get it?)
3,200 lines of yEnc encoded text equals about 384,000 bytes of
encoded data. Making the segment size in your posting program
the same as the block size in your parity set is a Very Good Idea.
It means that a downloader who is missing four segments only has
to find four parity blocks... so they know that a file marked
"vol06+4.PAR2" will be exactly what they need. "vol10+9.PAR2"
will contain 9 QuickPar parity blocks, etc.
When making a set of data integrity verification files, there
are two tips which will always benefit you. First, always test
your verification files after making them. In rare cases, a
parity set is created incorrectly and may not report itself as
bad during its creation. Trust but verify.
Second, make two data verification checkers using two different
formats. There are four formats in widespread use: par2, par, csv,
and sfv. Choose two, test both results yourself, and you will
save yourself the trouble of having to repost something else later.
Q. Should I post a "nzb" file with my binary post?
A. This is optional, since nzb files do not have universal support
among major newsreader clients. A .nzb file is an XML document
which an "nzb aware" newsreader can read and interpret. The nzb
file tells the newsreader what files belong to its set and automates
the process of downloading an entire set of files. Originated by
the makers of the NewsBinPro newsreader, the nzb is useful but is
not supported by all newsreader client programs at present, making
its utility limited, and thus inclusion is optional.
Grouse
--
Confidence is always sexy, a woman with short hair
is saying that she doesn't need to wave a flag to
feel sexy.
"I have made this longer, because I have not had
the time to make it shorter."
-- Blaise Pascal
|
|
){kind=link}