Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.binaries.ibm.pc.d
Subject: More silence in comp.binaries.ibm.pc
Message-ID: <8472@bsu-cs.bsu.edu>
Date: 2 Aug 89 04:32:39 GMT
Expires: 23 Aug 89 04:32:38 GMT
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 93

The bad news:

Due to a delay in completing the OS upgrade of bsu-cs, and the fact
that I am scheduled to be out of town Auguest 2 through August 10, the
silence in comp.binaries.ibm.pc will extend to around August 11.

The good news:

Except for incoming submissions that have just arrived, all normal
submissions have been cleared and the input queue is empty.  There are
some things that need further action (stuff that doesn't work or
doesn't extract, or whose copyright status isn't clear, etc.).  But
everything that could be posted has been posted.  So the silence will
not really cost you much by way of software in comp.binaries.ibm.pc.

Notes:

1.
Some info postings were due to appear this week in comp.binaries.ibm.pc,
explaining how to extract and decode posted binaries and how to submit
software for posting.  These will appear after August 10.  If you are
still looking for this information, please ask others at your Usenet
site -- there is a good possibility that somebody will be able to
answer your questions.  However, here is some brief information to tide
you over:

EXTRACTING:  The simplest sequence for extracting most posted software
is:

     a.   Use the "combine" script (given below) on all parts of the
          posting in sequence.  This will usually give you a zoo
          archive.  E.g., for a three-part posting, save it in files
          called "part01", "part02", and "part03", and then give the
          command:

               combine part01 part02 part03

     b.   Use zoo to extract the contents of the archive.
     c.   Don't forget to read the text in part 1 of each posting.
          It contains some information about the software, so you can
          decide if you want to bother with it.

When transferring files from a UNIX machine to your PC, if you are
using Kermit, be sure that Kermit on both ends knows whether the file
is text or binary.  Probably 90% of all file transfer problems
discussed in comp.binaries.ibm.pc.d involve not correctly telling the
transport software what type of file is being transferred.  In most
cases you will tell Kermit "set file type binary" at the UNIX end and
"set eof noctrl-z" at the MS-DOS end.

The "combine" script is an executable file containing:

     cat $* | sed '/^END/,/^BEGIN/d'| uudecode

SUBMITTING:  Archive the software with "zoo", "arc", "pkzip", "tar", or
"cpio" "abe".  Encode the resulting archive to make it printable
(except in the case of "abe") using "uuencode" or "btoa".  Split the
resulting file into pieces no more than about 45 kilobytes long.  Use
an informative subject heading, and mail each piece to:

     UUCP address:     iuvax!bsu-cs!ibmpc-binaries
     Domain address:   ibmpc-binaries@bsu-cs.bsu.edu

For inquiries, as opposed to submissions, use the following address:

     UUCP address:     iuvax!bsu-cs!ibmpc-binaries-request
     Domain address:   ibmpc-binaries-request@bsu-cs.bsu.edu

(You can also send inquiries to my personal mailbox, but in the long
run the address above is better it allows inquires re moderation to be
separated from my own mail.)

When submitting software, be sure to include your email address
somewhere in the body of your first message.  Message headers often get
mangled by mail gateways, with the result that you mail can be
unreplyable unless I can find a return address in the body.

Also, be sure to include a Subject: heading.  I often have to scan
through several hundred messages to find the one I am looking for, and
if a message doesn't have a Subject: heading, there is a distinct
possibility that it will simply get buried in my tremendous pile of
mail and never be seen again.

2.
Any email sent to me during the last three or four days has either been
answered already a few minutes ago, or won't be answered until after
August 10.

(With apologies to newsadmins, this article is posted with a long
expiration date.)
-- 
Rahul Dhesi 
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi