[comp.sys.atari.st] FTP Arc Transfers

yz2y@vax5.CIT.CORNELL.EDU (12/12/88)

     	I'm hoping someone out there can help me with this one. Recently I
have been attempting to obtain ARC files from ftp sources such as 
him1.cc.umich.edu and cs.orst.edu. Now that I have finally figured out how
to find my way to these files once I am connected, I am encountering another
problem. Somewhere along the transfer line between the archive site and my
ST, the format of the ARCed files becomes 'screwed up'. For when I try to
unarc them, I consistently get the same message: "The file *******.ARC has a
bad header." .
	The transfer procedure I am using involves first sending the files to
my school's mainframe system ( I have tried this on both our VAX 8530 and IBM
7171 systems). I then use Kermit on Uniterm 2.0c to send them to my ST. I do
have binary mode set all the way, except on Uniterm; and the actual transfer
process works fine. Any help on this matter would be greatly appreciated.
        A suggestion to the operators of the above-mentioned FTP sites would
be to use Dumas UUEncode on their files. I believe this would greatly reduce
the chance of this type of error occurring.
	Also, while I'm on the topic. How many times do users of this newsgroup
have to request the locations of other ST Archive Sites before they finally
get a response?!!!!!

	Thanks in Advance,
	Steve Coco

-------------------------------------------------------------------------------
Steve Coco
YZ2Y@CRNLVAX5                       "Don't Dream It, Be It!"
YZ2Y@CORNELLA                               - Richard O'Brien
YZ2Y@VAX5.CIT.CORNELL.EDU
-------------------------------------------------------------------------------

kline@arizona.edu (Nick Kline) (12/12/88)

The problem with FTP transfers is that you want binary transfer, since there
are just text files.   In the ftp program, you can specify that you want 
to do a binary transfer.  You do this by typing 'binary', once you are in
the ftp program and connected.  

Another problem area is transferring files from your friendly UNIX machine to
your trusty Atari, via modem.  If you use kermit to transfer your files,
you also need to specify binary transfers, otherwise kermit does some weird
carraige return/line feed translation between the UNIX and the Atari.

-Nick Kline

===========================
|Hey, I'm just some guy...|
|Nick Kline!arizona.edu   |
=========================== 

hyc@math.lsa.umich.edu (Howard Chu) (12/12/88)

In article <17540@vax5.CIT.CORNELL.EDU> yz2y@vax5.cit.cornell.edu (Steve Coco) writes:
%
%     	I'm hoping someone out there can help me with this one. Recently I
%have been attempting to obtain ARC files from ftp sources such as 
%him1.cc.umich.edu and cs.orst.edu. Now that I have finally figured out how
%to find my way to these files once I am connected, I am encountering another
%problem. Somewhere along the transfer line between the archive site and my
%ST, the format of the ARCed files becomes 'screwed up'. For when I try to
%unarc them, I consistently get the same message: "The file *******.ARC has a
%bad header." .
%	The transfer procedure I am using involves first sending the files to
%my school's mainframe system ( I have tried this on both our VAX 8530 and IBM
%7171 systems). I then use Kermit on Uniterm 2.0c to send them to my ST. I do
%have binary mode set all the way, except on Uniterm; and the actual transfer

You must set binary mode in Uniterm as well.

%process works fine. Any help on this matter would be greatly appreciated.
%        A suggestion to the operators of the above-mentioned FTP sites would
%be to use Dumas UUEncode on their files. I believe this would greatly reduce
%the chance of this type of error occurring.

Uuencoding, unfortunately, is not proof against incompatibility. Take an
EBCDIC system for example. There is now Old EBCDIC, New EBCDIC, and proposed
New EBCDIC. All of these systems will have difficulty transferring a file
purporting to consist entirely of plain text. (The archives at him1 are
stored on an IBM mainframe, thus this problem is relevant...) It's much more
a sure thing to rely on binary mode in ftp and kermit than whatever strange
transmutations will occur to a file labelled as "plain text." Sad, almost
nonsensical, but true.

%	Also, while I'm on the topic. How many times do users of this newsgroup
%have to request the locations of other ST Archive Sites before they finally
%get a response?!!!!!
%
%	Thanks in Advance,
%	Steve Coco

Depends on how many other people have asked this week, and how much network
bandwidth we feel like wasting generating replies.

Perhaps we need a monthly posting of archive sites, listings of the contacts
at each site, etc... [I suspect it will only help a little bit. Many times
the often-repeated questions are asked by people who do not regularly read
the newsgroup, or don't subscribe to the mailing list, so they'll rarely
benefit from regular repostings of any information...]

Maybe better - instead of automatically forwarding mail to the Info-Atari
mailing list, check to see if the message sender is already a subscriber.
If not, return the message with a "standard info" message attached...

--
  /
 /_ , ,_.                      Howard Chu
/ /(_/(__                University of Michigan
    /           Computing Center          College of LS&A
   '              Unix Project          Information Systems

c60a-2bn@web-2a.berkeley.edu (Lawrence Chiu) (12/13/88)

Can anyone tell me how to connect to a site using ftp?  I am confused.

Also, how does one decode the binary files?  Thanks in advance.

Lawrence Y. Chiu; University of California, Berkeley.

yz2y@vax5.CIT.CORNELL.EDU (12/13/88)

       Thank you for all responses, but maybe I should have emphasized this in
my original message: I AM USING BINARY AT EVERY STAGE!!!!!!!!!!!!!!!
I hope that someone can find another suggestion for me.
       I've also had requests for more info on the two ftp sites that I 
mentioned before. The first-cs.orst.edu- does not really have a lot of Atari
files but it does have Uniterm 2.0e and accompanying files. To get to this,
do an anonymous login, any password, step through the directories: pub/atari/
uniterm, then do a ls.
      The second site - him1.cc.umich.edu - has tons of ARCed files for the ST.
To get to these, do an anonymous login, any password, cd PC7:  (don't forget 
the colon!) , and ls ?  . One thing about this site is that it can sometimes
be difficult to get connected to it, but just keep trying.
      Again, if anyone has info on other ftp sites, please let the net know.

					-Steve Coco

------------------------------------------------------------------------------
Steve Coco
yz2y@vax5.cit.cornell.edu               "Don't Dream It, Be It"
YZ2Y@CRNLVAX5                                -Richard O'Brien
YZ2Y@CORNELLA
------------------------------------------------------------------------------

wsflinn@violet.waterloo.edu (Scott Flinn) (12/14/88)

In article <512@stag.math.lsa.umich.edu> hyc@math.lsa.umich.edu (Howard Chu) writes:
>In article <17540@vax5.CIT.CORNELL.EDU> yz2y@vax5.cit.cornell.edu (Steve Coco) writes:
>%
>%     	I'm hoping someone out there can help me with this one. Recently I
>%have been attempting to obtain ARC files from ftp sources such as 
>%him1.cc.umich.edu and cs.orst.edu. Now that I have finally figured out how
>%to find my way to these files once I am connected, I am encountering another
>%problem. Somewhere along the transfer line between the archive site and my
>%ST, the format of the ARCed files becomes 'screwed up'. For when I try to
>%unarc them, I consistently get the same message: "The file *******.ARC has a
>%bad header." .

>You must set binary mode in Uniterm as well.

I have also had this problem (although I have only tried ftp once!)
After connection, I typed 'binary', and received the message
"200  Type is now image".  I then transfered an ARC file to a
local machine.  From there, I uuencoded it, downloaded it with UniTerm's
kermit (NOT binary mode), uudecoded it on my Atari, and tried to
deARC it.  The file was nine small ARC's all 'stored' in a single
outer ARC file.  The outer file unARC'ed perfectly(?), but I received
"The file ********.ARC has a bad header." for _every_ one of
the smaller ARC files.
  
Questions:
   1. At what stage am I screwing up (or should it be working)?
      I am using ARC version 5.21.
   2. Has _anybody_ transfered binaries from him1.cc.umich.edu
      successfully?  What did you do ... exactly?
   3. If the problem is that I must have binary mode set when I
      download the _uuencoded_ binary file from the local machine
      to my Atari (a process which has worked flawlessly a zillion
      times before), WHY?

Thanks muchly for any advice!
--
Me:      Scott Flinn                   /  "If it doesn't fit, force it.
Domain:  wsflinn@violet.waterloo.edu  /  If it breaks, then it didn't
UUCP:    watmath!violet!wsflinn      /  fit anyway."

yz2y@vax5.CIT.CORNELL.EDU (12/14/88)

        In my previous posting, I stated that while doing FTP transfers to my
ST I had binary mode set all the way except on Uniterm. Needless, to say I 
expected and got a lot of responses saying that there is no way I can transfer
a binary file without having binary mode set on Uniterm also. Well, here's my
response to that one:
	For the past month or so, I had been unsuccessfully trying to transfer 
Arc-ed files to my ST with binary mode set on Uniterm (as well as everywhere
else). The only response I kept getting was BAD CHK errors on Uniterm. Then,
one time I accidentally forgot to enable binary mode on Uniterm, and lo & 
behold it was transferring!!
        Since that time, I have successfully transferred AND de-ARCed many 
files from both ATARINET and comp.binaries.atari.st (which, by the way Howard
Chu, are all UUEncoded) WITH BINARY MODE DISABLED! However, I can only transfer
but not de-arc the FTP .ARC files this way (Yes, I've tried binary on for these
too).
        Now, I don't want a lot of responses back saying that I must be crazy
or that I'm not doing what I think I'm doing, because two other ST owners at 
Cornell have done the same thing.
        We were also contemplating the idea that perhaps Cornell uses some non-
standard software (which they tend to like to do) on their mainframe system,
which would cause this whole strange scenario. Any thoughts on this one?

                                    -Steve Coco

------------------------------------------------------------------------------
Steve Coco
yz2y@vax5.cit.cornell.edu                  "Don't Dream It, Be It!"
YZ2Y@CRNLVAX5					-Richard O'Brien
YZ2Y@CORNELLA
------------------------------------------------------------------------------

mike@ncrcpx.UUCP (Mike Reiss) (12/14/88)

I have an Atari ST connected to a Unix machine, connected to another Unix 
machine, ...  connected to the world (??? USENET).  Anyway, I am not a Unix
guru.  I don't know anyone here that really is.  I keep hearing about these
"ftp" connections and they sound great.  I wish someone would tell me what
this is all about and how to make use of it.

thanks,

mike

keithj@ux1.lbl.gov (Keith J Groves) (12/15/88)

Hi Steve,
      I too seem to have trouble de arcing files by way of FTP
transfer. I use kermit after receiving the files on our computers
then make the final transfer to my ST with kermit using Uniterm.
I haven`nt tried using my Flash Kermit accessary though, but I 
suspect I`ll get the same results.  If you find out anything, I
sure would appreciate a comment or two.  Thanks in advance.

                       Keith Groves

mcli@uhura.cc.rochester.edu (Maurice Ling) (12/15/88)

One thing to check when downloading *.ARC files is that the host computer
(your mainframe system) is set to binary mode.  This is usually done by typing: 
"set file type binary" at the kermit prompt.  Then, use uniterm in binary 
kermit mode to download the file.  uuencoded files are in ASCII form, so 
you can download them in ordinary ASCII mode.  

good luck,

Maurice



*******************************************
*                                         *
* Optics...  The wave of the future       *
*                                         *
* BITNET  :  MCLI_SS@UORDBV, MCLISS@UORVM *
* UUCP    :  ...rochester!ur-tut!mcli     *
* Internet:  mcli@tut.cc.rochester.edu    *
*                                         *
*******************************************

4204_5147@uwovax.uwo.ca (Claude Morin) (12/15/88)

In article <17540@vax5.CIT.CORNELL.EDU>, yz2y@vax5.CIT.CORNELL.EDU writes:
> 
>      	I'm hoping someone out there can help me with this one. Recently I
> have been attempting to obtain ARC files from ftp sources such as 
> him1.cc.umich.edu and cs.orst.edu. Now that I have finally figured out how
> to find my way to these files once I am connected, I am encountering another
> problem. Somewhere along the transfer line between the archive site and my
> ST, the format of the ARCed files becomes 'screwed up'. For when I try to
> unarc them, I consistently get the same message: "The file *******.ARC has a
> bad header." .
> 	The transfer procedure I am using involves first sending the files to
> my school's mainframe system ( I have tried this on both our VAX 8530 and IBM
> 7171 systems). I then use Kermit on Uniterm 2.0c to send them to my ST. I do
> have binary mode set all the way, except on Uniterm; and the actual transfer
> process works fine. Any help on this matter would be greatly appreciated.
>         A suggestion to the operators of the above-mentioned FTP sites would
> be to use Dumas UUEncode on their files. I believe this would greatly reduce
> the chance of this type of error occurring.
> 	Also, while I'm on the topic. How many times do users of this newsgroup
> have to request the locations of other ST Archive Sites before they finally
> get a response?!!!!!
> 
> 	Thanks in Advance,
> 	Steve Coco
> 
> -------------------------------------------------------------------------------
> Steve Coco
> YZ2Y@CRNLVAX5                       "Don't Dream It, Be It!"
> YZ2Y@CORNELLA                               - Richard O'Brien
> YZ2Y@VAX5.CIT.CORNELL.EDU
> -------------------------------------------------------------------------------

rosenkra@hall.cray.com (Bill Rosenkranz) (12/16/88)

---
In article <1475@helios.ee.lbl.gov> keithj@ux1.lbl.gov (Keith J Groves) writes:
=Hi Steve,
=      I too seem to have trouble de arcing files by way of FTP
=transfer. I use kermit after receiving the files on our computers

i TOO had troubles, but it was ONLY with utermisc.arc from him1. the arc
itself is composed of several other arcs. arc t on the main file
was a-ok after ftp BUT arc t on the arcs within the arc gave errs.
a quick peek with a dump util showed 0x0D,0x0A (cr-lf) messing up the
headers and elsewhere so i just wrote a filter to find these and filter
the 0x0D (cr) out. the resulting new arc was fine. this leads me to
believe that the original posting may be flakey, especially since the
other 5 or 6 arc files i moved in exactly the same way (ftp from
him1, image type/kermit on unix side, binary mode (always!)/uniterm
binary mode).

give it a try. it only took about 5 min to write such a code. just make
surce u open the files on binary mode (fopenb/openb of "rb", depending on
yer compiler...).

-bill

mcli@uhura.cc.rochester.edu (Maurice Ling) (12/16/88)

In article <499@ur-cc.UUCP>, mcli@uhura.cc.rochester.edu (Maurice Ling) writes:
> 
> 
> 
> *******************************************
> *                                         *
> * Optics...  The wave of the future       *
> *                                         *
> * BITNET  :  MCLI_SS@UORDBV, MCLISS@UORVM *
> * UUCP    :  ...rochester!ur-tut!mcli     *
> * Internet:  mcli@tut.cc.rochester.edu    *
> *                                         *
> *******************************************

sorry, my signature should read:


*******************************************
*                                         *
* Optics...  The wave of the future       *
*                                         *
* BITNET  :  MCLI_SS@UORDBV, MCLISS@UORVM *
* UUCP    :  ...rochester!uhura!mcli      *
* Internet:  mcli@uhura.cc.rochester.edu  *
*                                         *
*******************************************

sbigham@dukeac.UUCP (Scott Bigham) (12/16/88)

Yet another monkey wrench to throw in the works:

Is the ARC used to arc these binaries the same as the arc found on most Unix 
systems?  Or what is this ARC 5.21 thing the last person mentioned?  The only
other ARC program I've seen is (you guessed it) ARCed.

I have some file called ARCX.TTP given me by a friend of mine who does this
sort of thing regularly (and who's unfortunately at another college at the 
moment).  Does it bear any relation to anything discussed above (or anywhere
else in the newsgroup, for that matter)?

						sbigham

-- 
Scott Bigham                         "The opinions expressed above are
Internet sbigham@dukeac.ac.duke.edu   (c) 1988 Hacker Ltd. and cannot be
USENET   sbigham@dukeac.UUCP          copied or distributed without a
...!mcnc!ecsgate!dukeac!sbigham       Darn Good Reason."

jlong@afit-ab.arpa (Jeffrey K. Long) (12/16/88)

I have downloaded many arc files from UMICH.EDU using FTP.  I too had problems
with the 'Bad Header" messages until I started using the mainframe to De-arc 
the files and THEN downloading them via UniTerm!  Those of you who are having
these problems may want to try that.  I suspect that these files were originally
arced on a mainframe and that our ST version of arc isn't compatible.

hyc@math.lsa.umich.edu (Howard Chu) (12/16/88)

In article <1165@dukeac.UUCP> sbigham@dukeac.UUCP (Scott Bigham) writes:
>Yet another monkey wrench to throw in the works:
>
>Is the ARC used to arc these binaries the same as the arc found on most Unix 
>systems?  Or what is this ARC 5.21 thing the last person mentioned?  The only
>other ARC program I've seen is (you guessed it) ARCed.
>
Until recently, ARC did not exist on most Unix systems. However, within the
past year, three major versions have come out, based on MSDOS ARC  versions
5.12, 5.20, and 5.21. If your Unix ARC doesn't claim to be any particular
version, it is probably based on 5.12. I released 5.20 and 5.21; the former
to alt.sources and the latter on comp.sources.unix. If you don't have it,
get it from uunet or any other unix archive site...

>I have some file called ARCX.TTP given me by a friend of mine who does this
>sort of thing regularly (and who's unfortunately at another college at the 
>moment).  Does it bear any relation to anything discussed above (or anywhere
>else in the newsgroup, for that matter)?

ARCX will only extract files from archives, and it won't extract squashed
files. ARC 5.21 will both create and extract from archives with squashed
files, as well as the usual crunched and squeezed... (Too bad it's so slow.
Still looking at it to see what new things I can do with it. Should have
5.32 in a couple days; look for it in a week or two.)
--
  /
 /_ , ,_.                      Howard Chu
/ /(_/(__                University of Michigan
    /           Computing Center          College of LS&A
   '              Unix Project          Information Systems

yz2y@vax5.CIT.CORNELL.EDU (12/17/88)

	Thank you everyone for your responses to my FTPing troubles. I'm 
happy to say that the problem appears to be solved, thanks to a suggestion by
Howard Chu. It seems that since I am using Kermit in a VMS environment rather
than a Unix environment, I have to set the filetype to 'Fixed' instead of 
'Binary'. That did the trick, 'cause I just finished downloading and
successfully de-arcing 3 files from him1. The ironic part is that I still 
didn't have 'binary' set on Uniterm!
	Thanks again, Howard and everyone else, for helping solve a 2-month 
long nerve-racking problem. Boy, don't you just love/hate (pick one) it when
the hardest problems get solved by the simplest solutions!

				Happy Holidays,
				Steve Coco

------------------------------------------------------------------------------
Steve Coco
yz2y@vax5.cit.cornell.edu             "Don't Dream It, Be It!"
YZ2Y@CRNLVAX5                                - Richard O'Brien
YZ2Y@CORNELLA
------------------------------------------------------------------------------

RUBIN@POLYGRAF.BITNET (David Rubin) (12/17/88)

The best way to get these .ARC files from umich is to FTP them (binary) to
the UNIX machine.  If you have an IBM PC on the network, simply FTP the
files directly to the 3.5" disk on the IBM -- the Atari can read this
disk directly and un-arc the file.  I have been successful this way.

It is not necessary for UMICH to uuencode its files.  This would not be
desirable since uuencode increases the size of the file by about 35%,
meaning longer transfer times and more disk space consumed on UMICH (and
less space for the programs).  If you need to, it is best to uuencode
the file after the ftp, then use Kermit to get it to the Atari and
uudecode it there.
-------
David Rubin                        |     INTERNET: RUBIN@graf.poly.edu
Polytechnic University             |       BITNET: RUBIN@POLYGRAF
Brooklyn, NY                       |

poole@forty2.UUCP (Simon Poole) (12/19/88)

In article <17549@vax5.CIT.CORNELL.EDU> yz2y@vax5.cit.cornell.edu (Steve Coco) writes:
>
>        In my previous posting, I stated that while doing FTP transfers to my
>ST I had binary mode set all the way except on Uniterm. Needless, to say I 
>expected and got a lot of responses saying that there is no way I can transfer
>a binary file without having binary mode set on Uniterm also.
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You can definitly only transfer binary files with UniTerm Kermit if you have
binary mode set (the 8th bit is explictly stripped if binary mode is not
turned on) (but uuencoded files are not binary in this sense).  

>	For the past month or so, I had been unsuccessfully trying to transfer 
>Arc-ed files to my ST with binary mode set on Uniterm (as well as everywhere
>else). The only response I kept getting was BAD CHK errors on Uniterm. Then,
>one time I accidentally forgot to enable binary mode on Uniterm, and lo & 
>behold it was transferring!!

Typical situation where this will occur is:

   UniTerm 8 Bit, no parity

   Serial connection somewhere along the line != 8 Bit, no parity

7 Bit text transfers will work with this combination, 8 Bit binary
will not! (setting the RS232 port to the proper settings will force
the transfer to 7 bit binary with prefixing).  


-- 
----------------------------------------------------------------------------
UUCP:   ...mcvax!cernvax!forty2!poole			Simon Poole
BITNET: K538915@CZHRZU1A
----------------------------------------------------------------------------