Article 46065 of comp.sys.cbm:
From: cbm@gac.edu (c.b.c Monthly Posting)
Newsgroups: comp.binaries.cbm,comp.sys.cbm,news.answers,comp.answers
Subject: comp.binaries.cbm FAQ v0.4
Date: 6 Dec 1995 21:55:27 GMT
Organization: Gustavus Adolphus College
Lines: 196
Approved: mmiller3@poblano.gac.edu (comp.binaries.cbm)
Message-ID: <4a53gf$gg5@lunen.gac.edu>
NNTP-Posting-Host: mmiller3@zariski.gac.edu

Archive-name: cbm-binaries-faq-part2
Comp-answers-archive-name: commodore/binaries-faq-part2
News-answers-archive-name: commodore/binaries-faq-part2
Version: 0.4
Author: Michael Jay Miller (mmiller3@gac.edu)


Comp.binaries.cbm Frequently Asked Questions

Written by Mike Miller, moderator, comp.binaries.cbm

The information in this FAQ was taken from many sources, including Chris
McBride's previous FAQ, the comp.sys.cbm FAQ, and assorted postings to the
three *.cbm groups.  Any and all questions, advice, etc. can be sent to
cbm-request@gac.edu.  Submissions for the group can be sent to cbm@gac.edu.

This version adds a couple advice notes for submissions and removes some
of the junk I should have cleared up by now.

1. What's the purpose of comp.binaries.cbm?

   Comp.binaries.cbm is the Usenet newsgroup for the legal distribution of
binary files for the 8 bit Commodore machines. This includes Pets,
VIC-20s, Plus 4s, C16s, C64s, C128s, and C65s.  If you're looking for
other Commodore-produced machines, check the comp.binaries.amiga group for
the Amiga line, and comp.binaries.ibm.pc.* for the Colt line.

2. What are all these other programs posted with the FAQ?

   Along with the FAQ, every month (usually the 2nd weekend of the month)
the following files are posted in text or uuencoded form:

The FAQ                 This file
BASIC uudecode          An improved version of Randall Williams' BASIC
                        program for changing the rest of the files to a
			Commie-usable form.
ACE 128/64 version 13   A Unix-like environment for the 64/128 that includes
                        full uuencoding/uudecoding software, documentation,
                        and other utilities for using your computer.
UUXfer                  A uuencoding/uudecoding program that doesn't require
                        ACE for use.
BCode and UnBCode       C Source for two programs that create and dissolve
                        NUCoded archives.
SEQ to BASIC            A program to convert SEQ text files to BASIC
                        program listings.  To convert a BASIC listing to
                        a SEQ file, do these commands:
                        (assuming the program is in memory and DV is the
                         drive's DeVice number.)
                        OPEN 8,DV,8,"filename,S,W"
                        CMD 8
                        LIST
                        PRINT#8:CLOSE8

3. So how do I use these things?

   Well, (if you are using your home system for everything) you should
capture or download the BASIC uudecoder, and either type it in or list it
off the disk and press return on each line.  Then capture another uuencoded
program and use the BASIC uudecoder to uudecode it. (For example, you may
choose to first get UUXFer or ACE for the better uuencode/uudecode
programs therein.  (If this sounds confusing, it is.  Remember, all
suggestions on changes to the FAQ can be sent  to  cbm-request@gac.edu ;-)
   If you can use a UNIX account to transfer files from, you can either
use uuencode/uudecode or BCode's NUCode option.  NUCode is backward
compatible with uuencode, but includes better support for multiple file
sections and CRC checking.  Most UNIX systems support programs such as
Kermit, sx, sb, and sz, which send files with Kermit, X-Modem, Y-Modem,
and Z-Modem protocols, respectively.

4. What are all these file extensions? 

   Compressed files, documentation and notes files, many different program
document files, and others have file extensions.  The comp.sys.cbm FAQ has
an extended listing of extensions; here is a summary of what you might see
on comp.binaries.cbm:

   .txt, .doc           Text files.  Usually documentation, but can be
                        descriptions of hardware modifications or other
                        such text.

   .sda, .sfx           Self DeArcing/SelF eXtracting LHArchive files.
                        These are compressed file(s) with a program
                        attached to dissolve them.  Usually LOAD and
                        RUN to dissolve; some .sda files are 64 or 128
                        specific.

   .arc, .lzh, .lha,    Assorted file archive types.  You need a program
   .lbr, .lnx, .zip     that handles that specific file type to dissolve.

   .uu                  UUEncoded file.

   .uua                 UUEncoded Archive file.  This means there are a
                        number of UUEncoded files listed together, one
                        after the other.

   x!<name>, x!!<name>  ZipCode Archived 1541 disks.  Use ZipCode to recreate
                        the source disk.

   .cvt                 GEOS Converted file.

5. By the way, what are all these [comments-MJM]?  I assume you added them?

   Yes, if I feel it's necessary to add a comment (perhaps answering a
question posed in the text of a post, correcting or adding information to
a description, or adding my personal comments from testing the software
[not unless necessary-MJM], they will appear in brackets and have my
initials added to the end.

6. OK, I can get files now.  How do I submit a file for posting?

   Unless you're submitting a short BASIC program (which can be posted by
changing it into a text file, then inserting it into a post/mail), the best
way to submit a file or files is to:

    1. Create an archive file containing the file(s) to post and the
       documentation for them.
    2. UUencode the file.
    3. Check your uuencoded file for length--please break all long files
       before the 1000 line point.  (breaking at around 950 lines works well)
       Also, please make sure that all filenames are Commodore-legal
       (length, PetScii chars, etc.)
    4. Mail the file(s) to cbm@gac.edu or (if your software allows)
       post to comp.binaries.cbm.  Note that mail is guaranteed to get here
       while posting may not, depending on your software.  A post not
       working is extremely rare, however.

    **  When mailing/posting, please use a Subject: line with this style **
       Subject: progname  (part x/x) Machine.info filetype description
       Where
         progname       The name of the program (not necessarily the
                        filename.
         (part x/x)     The uuencode file section part (and feel free to
                        include a long description of your file in a
                        (part 0/x) post.  If there is no included
                        documentation, or you must have some peripheral
                        (REU, 1581, 1571, etc.) PLEASE do a (0/X)
                        or tack the info on before the uuencoded part of
                        (1/X).  Thank you for your cooperation.
         Machine.info   The machine it runs on and the video standard
                        (if it matters)
                        C64, C128, Vic-20, Pet, Plus 4, C16, C65
                        NTSC, PAL  (or the first letter)
         filetype       What kind of program this is--
                        game, (disk/file) utility, demo, prod(uctivity), text,
                        SID, digi(tized music/sfx), pict(ure), or something
                        similar if it doesn't fit these.
                        Also, tack in GEOS, ACE, or similar OS notes here.
                        GEOS Note: please use either GeoPack or a PRG
                                   file Convert 2.5 format if possible.
                                   It'll make my life easier!
         description    If you've got any room left on the line, fit in a
                        short (5 words or less) description of what this is.

    5. You should get a receipt notice when I check the mailbox (I'll
       be checking every day)  I'll post the file after it's been checked
       and tested.  I plan on doing this at least every weekend and
       (if school allows) whenever I get a post.

**Note: Please don't try to post non-distributable copyrighted software. 
        This newsgroup is only for legal software distribution.

6. What's with this testing?  Don't you trust me?

   Well, I trust most of the people out there, but I want to make sure
that the uuencoding process worked, the program does what the docs and
your information says it does, and make sure it doesn't do things other
than what it is supposed to (like sending "n0:ha ha" to all drives.)  Plus
I have to make sure you didn't post non-distributable copyrighted
software.  Also, I change all archives to either .sda or .sfx if necessary.

7. What if I missed a cool demo the other week?

   If you have FTP access, I would recommend trucking on over to
ccnga.uwaterloo.ca or ftp.funet.fi and looking for it there.  Otherwise,
I'm going to add every posted file to my personal program archive, so go
ahead and request a repost/mailing at cbm-request@gac.edu.  I can't
guarantee either, but generally I'll be able to mail or repost it.

8. So, where else can I get files on the Internet?

   Commodore FTP sites can be found numerous places on the Internet, and a
list is posted in comp.sys.cbm frequently.  Here are two sites to get you
started:

ftp.funet.fi            Both have files in the /pub/cbm/* hierarchy
ccnga.uwaterloo.ca      

9. Great.  What if I have another question for you?

   You can send all questions/comments/flame mail/etc. to
cbm-request@gac.edu.  I would appreciate comments on this FAQ (I know the
style is looser than other FAQs out there.  I like it that way. :-)

Michael Miller
Moderator, comp.binaries.cbm
- cbm-request@gac.edu -


