Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!usc!jarthur!nntp-server.caltech.edu!tybalt.caltech.edu!toddpw
From: toddpw@tybalt.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: .bsq revisited. . .
Message-ID: <1990Oct30.011738.6470@nntp-server.caltech.edu>
Date: 30 Oct 90 01:17:38 GMT
References: <11225D0398DFE042CD@ritvax.isc.rit.edu>
Sender: news@nntp-server.caltech.edu
Organization: California Institute of Technology, Pasadena
Lines: 24
Nntp-Posting-Host: tybalt.caltech.edu

WKF2298@RITVAX.ISC.RIT.EDU (Wonko the Sane) writes:

>	I'm thankful for whoever asked about the .bsq files, but it hasn't
>helped.  I've been trying to get files off of wuarchive.wustl.edu and most
>of the files have an extension of .bsq.Z
>	I cannot find a FiLeStArT in it, nor will BINSCII touch it.  What
>is the .Z?

The .Z means that you need the unix utility 'uncompress' to get the .Z off of
it. I believe that VMS versions of uncompress are available but I don't know
where you can obtain them.

>	Another problem, and it may be specific to the particular VAX system
>that I'm using, but you cannot FTP a file that is ASCII via Binary or vice
>versa.  You would think that an ASCII could be sent Binary, but who knows.

The reason to use ascii transfer is when the two computers at each end use
different line-seperator characters -- unix uses linefeeds, and Apple has
always used carriage returns. Using ascii transfer translates these properly.
If the two systems use the same line seperator then you should be able to use
binary for text files without problems.

Todd Whitesel
toddpw @ tybalt.caltech.edu