Mac user seeks advice on decoding binary files from alt.binaries.multimedia.comedy.seinfeld newsgroup and playing them on Mac using QuickTime or other software.
I was looking at the alt.binaries.multimedia.comedy.seinfeld newsgroup and being a Mac user, I'm not familiar with the decoding method so I can video those on my Mac.
What software on the Mac do I need to decode those postings to alt.binaries.multimedia.comedy.seinfeld ? What software on the Mac do I need to play them? Does Quicktime support whatever format they are in?
Thanks!
East
I'd bet many are (using) the DivX codec.
Cant speak for MAC users or DivX support for da' MAC
Sorry
kc
kc wrote:
Is that something that is unique to Windows?
Maybe you need a binary usenet program? When a binary file is posted to usenet it is encoded in unicode(?) and not in binary (which is what you need it to be). A binary usenet program will translate it, and build each post into a single file so that you can use it.
Macs can run Divx files with minor difficulties http://www.macdivx.com/
Byron.
i got your back east coast and i welcome you....Macs Rule!!!
check out those new powerbooks!!!! and safari rocks....no more IE for me
below is a quote from a message that was on a binaries groups for macs..i think os x
Subject: Re: Switch From: maelstrom Newsgroups: alt.binaries.mac.osx.apps
In article , Brian wrote:
this should provide you with all the info you need...
ABM FAQ beta
(alt.binaries.mac.*)A quick reference for downloading, decoding and uploading for the abm groups. For more detailed information, please check the Survival Guide.
---------------------------------------------------------------------- ---
This version of the FAQ replaces all earlier versions of the FAQ and Survival Guide. Please give a copy of this text file to anyone who needs help with downloading from or uploading to abm. If you have suggestions for improving this FAQ, please post them in abma with the subject "FAQ suggestion".
Conventions for this FAQ: abm = alt.binaries.mac and its subgroups FAQ = Frequently Asked Questions SG = Survival Guide ISP = Internet Service Provider
---------------------------------------------------------------------- ---
TABLE OF CONTENTS
2. General Information [2.1] What is this FAQ about? [2.2] What groups does this cover? [2.3] DO's and DON'Ts & General Usenet etiquette [2.4] Definitions
3. Downloading [3.1] What do I need to download from these groups? [3.2] What newsreader should I use? [3.3] What do I need to expand the segments? [3.4] What other utilities would I need for these binaries? [3.5] What are CRCs? [3.6] What are PARs? [3.7] I don't have all the segments, how do I make a request? [3.8] How do I download the binaries if I'm on a PC?
4. Uploading [4.1] How do I prepare my binaries for uploading? [4.2] How should I set my newsreader for uploading? [4.3] How do I encode my binaries for uploading? [4.4] What is yEnc? [4.5] How should I name my posts? [4.6] What else should I include with my posts? [4.7] Is there an easier way to upload than doing it one at a time? [4.8] Reposting missing segments
7. Information for specific abm groups [7.1] alt.binaries.mac [7.2] alt.binaries.mac.audio [7.3] alt.binaries.mac.applications [7.4] alt.binaries.mac.applications.retro [7.5] alt.binaries.mac.apps [7.6] alt.binaries.mac.cd-images [7.7] alt.binaries.mac.fonts [7.8] alt.binaries.mac.games [7.9] alt.binaries.mac.osx.apps [7.10] alt.binaries.mac.serial.numbers
---------------------------------------------------------------------- ---
Each and every person that comes here is welcome to share knowledge and software. Every one, be you new or old, frequent or seldom, seeking answers or providing helpful advice, are always welcome. We are a loose knit group of people with a common thread - Macs and there use. Never feel intimidated or in awe of another. The only difference being is that they went through a transitional period of learning, asking questions, and testing before you arrived. Soon, you too will be as they. Be patient! Everything new is hard at first. But soon, you will be as good as everyone else and as such, you will be ready to help the next generation. If you find your time here to be frustrating, just ask for help. It will be forth-coming and in abundance. Nerves sometimes become frayed; a joke may be taken the wrong way; an observation may be taken as a sharp criticism. But at the end of the day, all is usually worked out. The only people that seek to disrupt our harmony intentionally are trolls and they usually appear in abundance in the summer months (breeding time). Although we encourage you to learn how to post and share knowledge, the most important reason for being here is to have fun and maybe make some new virtual-friends. We all have at one time or another caused disharmony in the group. It is acceptable although not encouraged. We are all learning how to cope just like we do with our family, our jobs, our way of life. We may loose sight of why we are here, but eventually, we remember.
2. General Information [2.1] What is this FAQ about?
This document is a quick reference for downloading, decoding, uploading and other questions for the alt.binaries.mac groups. This guide is designed to be concise and comprehensive for people with little or no experience. This is not intended to be step-by-step guide. For more extensive information, please look at the Survival Guide (SG). This FAQ is based on the things people seem to ask the most about. Please feel free to redistribute this to anyone in the group who requests help.
[2.2] What groups does this cover?
This FAQ covers the entire alt.binaries.mac hierarchy and includes a few others since they also deal with Mac binaries. The groups are generally addressed by using the first letter of each subcategory (i.e. alt.binaries.mac.applications = abma). This convention will be used from here on to refer to the individual groups. Here is the list:
Primary Groups -------------- alt.binaries.mac alt.binaries.mac.audio (NEW) alt.binaries.mac.applications alt.binaries.mac.applications.retro alt.binaries.mac.apps alt.binaries.mac.cd-images alt.binaries.mac.fonts alt.binaries.mac.games alt.binaries.mac.osx.apps alt.binaries.mac.serial.numbers
Secondary Groups ---------------- alt.binaries.mac.cd-images.d alt.binaries.mac.cd-images.parts alt.binaries.mac.games.adult alt.binaries.mac.hebrew alt.binaries.mac.playstation alt.binaries.mac.playstation.d alt.binaries.mac.playstation.parts alt.binaries.applications.mac alt.binaries.sounds.macintosh alt.binaries.warez.mac alt.binaries.warez.mac.req alt.binaries.warez.macintosh
The first nine groups are the more frequently read groups. abma is the "main" group and where most of the posters and readers visit on a regular basis. The secondary abm groups are still used but not as popular at this time. The last five groups have an honorary status and are included here as a reference since they also have to do with Mac binaries.
[2.3] DO's and DON'Ts & General Usenet etiquette
*LURK (observe and read posts) AND LEECH (download some binaries) for a few weeks before posting anything, including questions. To find out what's welcome or taboo, just ask! Observing will also help you avoid the mistake of duplicating very recent posts by rushing to contribute without knowing the group's posting history.
*RTFM (read the freaking' manual). Learn how to use your computer, software, and basic Internet tools like search engines. While others are willing to help, don't expect to be spoon-fed. Try reading your ISP's FAQs. Also, find out if your provider hosts any "local" newsgroups for members needing tech help and use them to their fullest extent.
*DON'T SHOUT unless you mean it. In posts and email, THIS IS SHOUTING. Turn off that caps lock.
*Read the "info" file of any post to find out any and all information given about that particular posting.
*Wait at least 24 hours for all the parts to arrive before posting any request for a repost.
*It's free, so lose any attitude you might have. Missing parts are NOT the posters fault. Courtesy will get you far, rudeness will get you ignored or worse killfiltered (labeled as 'invisible' so that your comments, request, etc. go unseen).
*Try to keep off topic discussion to a minimum. This is a community, so there will be conversations that have nothing to do with the Mac or binaries. If you do, please be considerate of others and note it in the subject with "OT:" example: joe.poster "OT: I think my neighbors are watching me!"
*Use http://versiontracker.com for updates and shareware apps.
*Use http://www.google.com for looking up more information on a particular posting.
*DO be courteous and patient.
*DO thank posters for their efforts and reposts.
*DO use "ATTN:" or angled brackets to direct a message to a particular person in the group. example: "ATTN: <joe.poster> here are your fills'
*DO learn to use filters for your nickname, requests or favorite poster.
*DO test your posting methods before you post to the abm groups (use alt.test or alt.binaries.test for all test posts).
*DO invest in a Premium News Server. One advantage is that your IP address is not appended to your post. Additionally, you will be getting more complete posts with less requests for reposts.
*DON'T make multiple requests. It wastes time and bandwidth.
*DON'T remind readers that you have been waiting for a request.
*DON'T start flame wars, especially those like Mac vs. PC, OS 9 vs OS X, etc.
*DON'T feed the trolls.
*DON'T toppost. Make all replies at the bottom of a thread to make it easier to follow.
*DON'T crosspost. Post messages to only ONE group at a time. If the message is needed in more than one group, make a message for each group.
*DON'T use your real name or email address. This limits your exposure to spam, stalkers and email harvesters.
*DON'T ask anyone to reply via email (this would eliminate their anonymity and your own), or post any personal information about another person which would violate their anonymity.
*DON'T ask to "trade" for something else. The abm groups are not warez sites.
*DON'T use excessive characters in a subject line. example: "I need xyz program really bad!!!!!!!!!!!!!!!!!!!!!!"
*DO smoke 'em if you got 'em.
[2.4] Definitions
Troll: a strange lonely form of usenet beast that "troll" usenet newsgroups with the sole hope of creating anger and confusion by posting annoying and abusive messages. Their desire (and perhaps the only desire they have) is to attempt to force reactions from otherwise sane people. When you're new to a newsgroup it's difficult to separate a "troll post" from a "flame war", but if you practice watching for awhile it gets easier. Difficult as it can be at times, PLEASE AVOID REPLYING TO ALL SUCH POSTS and thus feeding the trolls. Since trolls exist only for the attention they can generate, they will leave only � and always � when they are simply ignored.
Flame War: an entirely different set of ugly, vile, vulgar set of discussion threads that most typically pit two or more regular posters in a discussion they have already clearly espoused their views on (i.e. Mac vs PC or OS 9 vs OS X).
Poster: the individual that takes the time and effort (and risk! see Section 5) to upload and "post" a binary file.
Parts: created when a single attachment is uploaded by a newsreader.
The size of the part is determined by the 'News Part Size' in the
newsreader. The number of parts depends on the total size of the
attachment. All parts are needed to decode the file.
example: "ATTN: joe.poster - xyz.15 (1/3)" <== individual PARTS
"ATTN: joe.poster - xyz.15 (2/3)"
"ATTN: joe.poster - xyz.15 (3/3)"Segments: created by DropSegment or the StuffIt Deluxe application. A
single segment is attached to a message and then posted or downloaded.
It is very useful to know how many segments are in a particular post.
All segments are needed to join or decompress the file.
example: "ATTN: joe.poster - xyz.15 (1/3)" <== individual SEGMENTS
"ATTN: joe.poster - xyz.16 (1/3)"
"ATTN: joe.poster - xyz.17 (1/3)"Archive: the compressed data file of an image, installer, folder, or set of files on your drive.
File: the untouched image, installer, folder or individual component of an application.
Thread: a Usenet conversation; a series of replies which continue under the same subject header. Always post your replies to the BOTTOM of the thread.
3. Downloading [3.1] What do I need to download from these groups?
There are three minimum programs you will need. First, a newsreader for reading and sorting the thousands of messages. Second, a decompression utility for expanding/extracting the segments. Third, an imaging utility for creating, mounting or burning disk images of entire CDs.
[3.2] What newsreader should I use?
Currently there are several newsreaders for the Mac that are commonly used in abm:
OS yEnc Price
----- ---- -----
Halime X Y Free
Hogwasher 8.6/X Y $49
MacSOUP 9/X Y ?
MT-NW X Y Free
NewsWatcher 9/X N Free
Thoth 8.6/X Y $25
YA NewsWatcher 8.6 N Free (no longer supported)Brian Clark was the author of YA NewsWatcher and is now the author of Thoth. If you have used YANW then Thoth will be easy to learn.
Both Netscape Communicator and Microsoft Outlook/Entourage have built-in newsreaders but they do not handle binary attachments well. These programs are NOT recommended for downloading.
[3.3] What do I need to expand the segments?
The de facto program is StuffIt Expander, which is available for free from Aladdin Systems (www.aladdinsys.com). StuffIt Deluxe can also be used but it is a commercial application.
Occasionally Stuffit Expander cannot decode the downloaded binaries and additional utilities are required. Programs which can help decode problem files include UUCD, YA-Decoder and Rosetta.
[3.4] What other utilities would I need for these binaries?
Other than a newsreader and decompression utility you will need an imaging program.
OS Price Files it handles
----- ----- ------------------
CD-Copy 8.6 N/A .img
Disk Copy 8.6/X Free .img .smi .dmg (see note below)
Shrinkwrap 8.6 $30 .img .smi
Toast 8.6/X $90 .img .iso .bin .iso .toastYou might also need a yEnc decoder if the newsreader you have does not support it (see Section 4.4).
---------------------------------------------------------------------- ---
PLEASE NOTE
Apple changed the way .dmg files are created in OS X.2 and will not work in OS 9. If you are going to create a disk image, using OS X.2 and posting an OS 9 app, DO NOT use Disk Copy. The person downloading will not be able to open the disk image, so it would be better to use Toast to create the disk image.
Disk Copy X.2 .dmg will not open with Disk Copy for OS 9. ---------------------------------------------------------------------- ---
OS Price
----- -----
Rosetta 8.6/X $15
yEncTZ 8.6/X FreeFor CRC lists you will need two programs, ListFiles & ListCompare (OS 8.6-9.2.2). For PAR files you need MacPar Deluxe (OS X only).
[3.5] What are CRCs?
Cyclic Redundancy Check or CRC is a method for checking the integrity of files. ListFiles is used for generating a list of CRCs for all the segments in a posting. ListCompare allows you to compare the list given to you by the poster with the list you generate once you download all the segments. If a CRC or checksum is not the same for a given segment, then download the segment again to ensure there was not a problem on your end. This will relieve extraneous repost requests.
[3.6] What are PARs?
Parchive, parity files or PAR is a RAID-like system that allows you to recover/create the corrupt/missing segments of a post. The PAR set consists of a .par index and a number of .p## PAR files. If you are missing 3 segments from a posting, then 3 PAR files are all that is required to create the missing segments.
There are several PAR utilities, the best of which is MacPAR Deluxe. Unfortunately, all the PAR utilities are for OS X only.
[3.7] I don't have all the segments, how do I make a request?
If you have OS X and there are PARs for the post, then use MacPAR Deluxe for recovering/creating the missing segments. If you have OS 9 or are missing more segments than you have PARs, the you need to request for a repost.
First, be patient. It is proper Usenet etiquette to wait 24 hours after the last segment has been posted for the messages to propagate to your particular server. Even though the 'Net is fast, there can be delays. Patience is a virtue.
Second, use the "Search" function of your newsreader to find any missing parts, segments, or messages. If that doesn't help, open the newsgroup from the "Full Group List". This will pull all the message headers from the news server instead of from your cache file.
The proper way to request a repost of segments is to address the
poster, the title of the post, then number of segments. If the number
of segments is large then list the missing segments in the body of the
message. Please don't use exclamation points or other characters to
grab attention or demand that the poster hurry. Also, don't make the
same request multiple times; it wastes your time and others bandwidth
and is very annoying.
good example "ATTN: joe.poster - Please repost xyz segs 3, 4, 10"
bad example "!!!!!I NEED XYZ SEGS 3, 4, 10, 22, 37, 45, 67-72, 90
AND HURRY UP!!!!!"Another bad example is to reply directly to the posted binary. This shows up in the newsreader looking like a binary post and is easy to miss.
Some posters will create a REPOST REQUEST thread. Make any requests as a reply to this thread WITHOUT CHANGING THE SUBJECT LINE.
Request specific PARTS of segments; if each segment consists of 15 parts and only one part is missing, request just the missing part (i.e. Please repost Seg 1, part 2/15). Leave the incomplete segment unread in your newsreader and when the missing part comes in the segment will show complete.
Most important thing for repost requests is to make it easy for the poster! You are asking, but the poster is not obligated to respond. some posters will not make reposts at all.
Remember that it's not the poster's fault for the failings of your ISP. The poster may be kind enough to upload PARs with the post, but is not required. If your ISP is giving you constant problems, then it is recommended that you invest a small amount of money per month in a commercial news provider.
Remember that it is easier to catch flies with honey than it is with vinegar. Be patient and polite. It goes a long way and may get you a faster response from the poster.
[3.8] How do I download the binaries if I'm on a PC?
Much discussion has been made about how this should be done. Hopefully the following instructions are correct. If there is a problem, please post a message in abma with the subject "FAQ correction Section [3.8] How do I download the binaries if I'm on a PC?"
The one main piece of software you need is Stuffit Expander for Windows from Aladdin Systems (www.aladdinsys.com). The following information is for a binary that will result in a Toast image file only. If the binary is an installer or a folder with Mac files, it will NOT work.
Download all the segments as you normally would any other binary. Next, use Stuffit Expander for Windows to decode, join and decompress the segments. This should produce a Toast image file. A Toast disk image file can contain extensions such as "�image", "�image", ".image", ".img", ".toast", or ".timg". All of these extensions are optional, and virtually meaningless.
Burning the disc (information based on work by Kristopher Bachtal)
2. Get Nero Burning Rom at www.ahead.de/en/Download.htm, install it, and reboot.
5. In the open window that pops up choose to view all files then select the disk image file and click Open.
6. Next a Dialog box pops up and tells you this is a foreign file format and asks you to set some options. Choose OK.
7. The foreign image settings window then appears. Under "Type of Image" choose HFS (leave the rest of the settings alone) then click OK.
8. Next the Write CD window comes up. Select the Burn tab. Make sure the "Write" checkbox is checked. Check the "Disc-At-Once" checkbox. If you don't use the Disc-At-Once option or can't (some writer don't support it) you should probably check the Finalize CD checkbox. I also uncheck the simulation check box but you can leave it checked if you want (It just takes longer).
Once the writing process is complete, the disk will be ejected and you can try it on your PC.
---------------------------------------------------------------------- ---
PLEASE NOTE
Technology changes, sometimes a bit too quickly. Please refrain from adopting new "standards" when they are first introduced. At this writing yEnc, .par & .sitx are relative newcomers. None have been perfected or work on all Macs.
As newer technologies are introduced, make sure you use coding or compression methods that are proven and available to the majority of your target audience. When in doubt, ask and/or make sure your subject line clearly reflects the "oddity".
And like always, test your postings at alt.binaries.test. ---------------------------------------------------------------------- ---
[4.1] How do I prepare my binaries for uploading?
First, make sure that whatever you are going to upload works and is virus-free. Next, gather everything that goes with that post. The best item to post is the disk image of the CD or disk. Next best thing is the installer from the CD/disk. If you don't have either of those, then collect all installed items from your hard drive. Don't forget to create separate folders for each set of files (i.e. one folder for control panels, one folder for extensions, etc.).
Second, compress the disk image/installer/installed files using DropStuff or Stuffit Deluxe. Make sure the compression setting in the preferences is set to Fast and not Maximum. A setting of Maximum is painfully slow to expand, even with a G4 and has even caused some corruption of archives. Please note that version 7 of Stuffit and Stuffit Expander includes a new format, .sitx. This new format is not 100% compatible with older versions of Stuffit and Expander, therefore you are recommended NOT to use it.
If the resulting archive is larger than 5 megabytes, divide the archive into smaller segments. Set DropSegment (from Aladdin Systems) no larger than 5 megabytes. Remember that if you are posting something for someone on a 56K modem to make the segment size smaller (1 to 3 megabytes).
If you are going to post something that no one has asked for, do the group a courtesy and let them know what you will be posting. Include the name, version number, OS requirements, etc. example: "joe.poster INTENT TO POST: xyz 3.0 for 9/X"
[4.2] How should I set my newsreader for uploading?
The main setting that needs to be correct is the "News Part Size". The settings vary depending on your news server but most will find success with a setting between 200 to 495 kilobytes. If the "News Part Size" is too high or too low your post will not propagate well and you will be deluged with repost requests. For many posters the "magic" setting has been 395kb. Test your post and have others check for propagation on their servers.
[4.3] How do I encode my binaries for uploading?
Newsreaders have two or more settings as the encoding method. The encoding method is the way the newsreader converts the parts to raw text for upload.
The three main encoding methods are UUencode, BinHex, Y-encode. DO NOT use UUencode for posting; it is a Unix encoding method that doesn't work well with Mac files. BinHex is the preferred method of encoding; this encoding allows the resource fork in a Mac file to be handle correctly for posting. Y-encode or yEnc is the newest encoding method. yEnc is not supported on all newsreaders and is not an Internet standard as of yet.
If you choose to upload using the yEnc encoding, then make sure to use the yEnc+MacBinary setting in the Thoth preferences. Tests have shown that this setting doesn't cause as many problems for others to download.
######################################################################
##
# --- R E A D M E ---
#
######################################################################
##
### VERY IMPORTANT WARNING ###
Avoid using YA-NewsWatcher 5.0 and 5.0.1 for posting. It is well
documented that these versions will corrupt a file when it is Binhexed
and posted while two upload streams are active at once. An alternative
is to post with YANW 4.2.6 instead, which is highly reliable.Note: The bug causing corruption does not affect downloads in any way. Thus YANW 5.x is reliable for downloading files. ###################################################################### ##
[4.4] What is yEnc?
(This information provided by Winston)
yEnc is an 8-bit text format - that's how it archives its wonderful space savings on servers, for uploading, and for downloading. Most of the older newsreaders do not understand 8-bit text, they only understand 7-bit text.
When we "encode" items in BinHex, yEnc, UUencode, etc, we are taking one form of file (a binary in this case, the disk image or program) and turning it into raw text (the encoded format) for posting onto Usenet. Older methods of encoding are 7-bit, and they generally have around 30% or more "overhead" in the text conversion that adds to the size of the post in uploading, news server storage, and downloading. yEnc only adds 1-2% of this "overhead", as most people understand it.
Again, remember that if a post is marked as yEnc, then you will need a newsreader that supports this new encoding method.
If you would like to read more information on yEnc, please visit www.yenc.org.
[4.5] How should I name my posts?
There is much debate in abm about this. If you leave the actual file names intact, that makes it very easy for casual onlookers (software developers, search engines, and feds) to find your posts (and maybe you yourself). Renaming them with phonetic spelling, abbreviation, loopy names (i.e. Pigital Derformer instead of Digital Performer) or spelling the name backwards (i.e. PhotoShop7 would be 7phoSotohP) can protect you and abm, but it also makes it harder to know what the file really is. There is no right or wrong here.
Also make sure that the file name does not exceed 31 characters. If it is more than 31 characters, the file name will be truncated and be very hard for those people on non-OS X machines to join the segments.
Once the file has been named, it will appear in the subject line along with message title. Adding long comments, requests or extra characters (exclamation points etc.) in the post is not recommended. It makes the subject line longer than it should be.
Don't use numbering in your posts. Some people like to put a numbering
system into the subject line to list the number of segments. This will
cause the newsreader to separate the similar parts instead of keeping
the parts together for each segment.
example: "ATTN: joe.poster - xyz.1 (1/3) [1/24]"
"ATTN: joe.poster - xyz.1 (2/3) [1/24]"
"ATTN: joe.poster - xyz.1 (3/3) [1/24]"
"ATTN: joe.poster - xyz.2 (1/3) [2/24]"
"ATTN: joe.poster - xyz.2 (2/3) [2/24]"
"ATTN: joe.poster - xyz.2 (3/3) [2/24]"The additional numbering is not needed if you have an info file (see Section 4.6).
Another tip for naming is to post with the attachment name first. Most newsreaders will have a setting that allows for this setting. If you don't have this setting, make sure to make the first character of the subject line a hyphen, "-".
The reason for this convention is so that all binary posts "float" to the top of the list and can be sorted from the rest of the text only messages.
[4.6] What else should I include with my posts?
Everything that belongs with that binary i.e. serial numbers, manuals, cover/disk scans, etc. All of these should be included in the archive before segmenting.
Two other things that should be included with the post are the CRC list and an info file. The info file is a plain text document (SimpleText on Mac or Notepad on a PC) that gives all pertinent data for your post. The info file generally includes the unaltered name of the post, a short description of the application, what OS the application requires, what kind of disk image, number of segments, etc.
Both the CRC list and info file can be compressed into one archive and uploaded with the other segments.
If you are using OS X, it is recommended to upload PARs with your post. This allows people to recreate/recover missing/corrupt segments. A good rule for .pars is to create 1 .par for every 10 segments. If you are posting more than 150 segments or a whole CD, then only post 15 .pars. This should provide enough .pars for recovering most missing files.
Segments should be posted in the following order:
CRC & info file PAR index file (the .par file) Segments 1-end PAR files (the .p## files)
[4.7] Is there an easier way to upload than doing it one at a time?
There are several autoposters to make posting easier. Each autoposter has its own pros and cons. Personal preference is the only way to choose one for you.
OS Price Apps it works with
----- ----- ------------------
Hermes X $10 Thoth
Ibis X Free Thoth
Osiris X Free Thoth & MT-NewsWatcher
sQuidOmatic 8.6 Free Thoth & YA-NewsWatcher
YA-Autoposter 8.6 $15 YA-NewsWatcher
Yapper 9 Free YA-NewsWatcherWhatever method of posting you choose, always test post to alt.binaries.test first to make sure your method works. Post a message to one of the abm groups pointing others to the test post so they can test your method and give suggestions/pointers.
[4.8] Reposting missing parts or segments
Occasionally, due to server problems or errors, requests for a repost of segments will be made. As a courtesy, you can fill the request of people that missed or lost segments.
First, make sure that requests are made after the 24 hour period for message propagation. This will allow all possible messages to get to the many news servers. A small note in your info file will remind people to be patient.
Next, make a separate thread for repost requests. This allows you, the original poster, a single thread to look through for segment requests. example: "XYZ REPOSTS -> make request here"
After that, collect all the segments requested in a separate folder on your drive. Then post these as you did for the original posting. Make sure to rename your reposted segments so that they show up in the news readers as separate items and don't intermingle with whatever parts remain from the initial post. It is standard practice to rename reposted segments by adding an 'r' at the end for first reposts, 'rr' for second repost, etc.
If only one person has made a request, then you can make an ATTN to the single person making the request. example: "ATTN: jane - here are your fills"
One thing to remember is that no news provider is going to protect you from the Law. Period. When it comes to their neck or yours, who are they going to choose? The news providers are there to make money from you. It sounds cynical, but it's true. The best way they can do that is by providing a great news service, unedited and unfiltered. It is not their job to monitor or censor what goes through the pipe. BUT if a court or a Law Enforcement official says that what is going through the pipe (either to you or from you) is illegal, then the news providers are quite obligated to cooperate with the law. It is not your constitutional right to break copyright law. That means that fessing up your account information and your activity is something that an ISP or a news provider will most certainly do if handed a subpoena. That's how it works. Do not forget that. BE CAREFUL.
1. Important: Never, never assume that your anonymity is guaranteed. If you are foolish enough to engage in repetitive, provocative behavior, chances are good that someone will find you. 2. In the Preferences, in Personalities, make your anonymous personality using a bogus name and email address. 3. In the Preferences in Extra Header Lines, or in a saved personality file (depending on the version of the program you're using), put the following line (but don't include any spaces at the beginning): x-no-archive: yes 4. Get a privacy-oriented news server. Ask some of the regular posters for suggestions. Ask the service that you plan to use about their privacy policy. 5. If your ISP/news service adds an X-Trace header to your post, then you are guaranteed to be tracked should law enforcement so choose to do so. Avoid a service which adds this header to your post.
Since March 2001, Apple has given the Mac community a new operating system to work with, OS X. This new OS is built on a Unix foundation. The Unix foundation in the OS now creates a new kink in the operations of applications. Pre-OS X applications can run in OS X in what is called Classic Mode. In essence, OS 9 is run in emulation inside of OS X. Therefore, OS X is backwards compatible with older applications to an extent.
Most applications will run in Classic, but a few will not. If you are on a Mac and running OS X, it is recommended that you update all your applications to work natively in OS X.
There are three terms for the "flavors" of Mac applications.
classic = apps that only run in OS 10.2.2 (in Classic Mode) and previous carbon = apps that run in both OS 9 and X cocoa = apps that run only in OS X
[7.1] alt.binaries.mac
[7.2] alt.binaries.mac.audio
A newsgroup for anyone interested in Macintosh audio programs and their use. The purpose of this newsgroup will be:
1. To discuss use, configurations, and trouble-shooting Macintosh audio systems.
2. To share ideas, information, and specific experience regarding the use of the aforementioned.
3. To discuss third-party add-on products and exchange user created ideas.
5. To educate and inform others about the strengths, weaknesses, and general usage of Macintosh audio applications.
6. To allow announcements of products and events for Macintosh audio applications, third-party products, and user groups.
7. All binary posting will be in a either Binhex, or yEnc-binary so as to be macintosh user friendly.
Messages should be posted in a professional, polite manner as to not purposely offend or insult another person.
The charter is a statement of what constitutes good manners in the newsgroup. It will be enforced through cooperation, mutual respect, and peer pressure when necessary. Anyone who willfully persists in violating the newsgroup's charter will in all likelihood eventually be asked, by the newsgroup's regular participants, to stop posting. If further sanctions are necessary, they will be discussed with the offender, or in news.admin.misc.
[7.3] alt.binaries.mac.applications
This is the main group for discussion and exchange of Mac binaries.
[7.4] alt.binaries.mac.applications.retro
This group is for previous versions of the Mac OS and binaries for older machines. Generally this is for System 7 and previous.
[7.5] alt.binaries.mac.apps
[7.6] alt.binaries.mac.cd-images
This group is for bit-for-bit CD images.
[7.7] alt.binaries.mac.fonts
This group is for fonts, font utilities and clip art.
[7.8] alt.binaries.mac.games
This groups is for games.
[7.9] alt.binaries.mac.osx.apps
This group is for programs which run natively in OS X or cocoa apps.
[7.10] alt.binaries.mac.serial.numbers
This group is for the exchange of serial numbers, serial databases and their readers.
*Be prepared to join the community. Feel free to contribute in any way; posting binaries, discussions, educating newbies, posting handy web references, etc.
*Storage space at ISPs for newsgroup messages is limited. Therefore it is advisable for posters to use the following guidelines in the interest of increasing retention (the length of time messages stay on the news server):
Post slower, repost less, repost only segments and encourage others to do the same. Whenever possible, limit repost to missing parts, not the whole thing.
Nov. 2002: - This version is dedicated to winston's mom; "Our best wishes & prayers are with you." - Updated to reflect new technologies - Formatted to look like a standard FAQ - Added info on PARs - Added info on OS X - Updated info on downloading on a PC
10. Credits This FAQ is an update to the original FAQ/SG which was put together by LuvBunny, Doctor, Grizzle, jet, Matt Black, smoker, t.v.c.1.5, xxx, Zapf, and others...
The update and compilation was done by maelstrom with help from (in alphabetical order): ComicShop, highlight, Island Girl, Nerf Herder, Sir CJ, smoker, sQuid Pro Quo, and winston.