CompuServe Thread

#ftp from amiga sites

11 messages in this thread
#95923From: dan barberApr 16, 1993 11:06 PM
Hello, I have a question about downloading amiga files from ftp sites(eg oes.orst.edu). Although cumbersome, here is the procedure I use: 1) login to Sun ws @ school via Atalk3. 2) ftp to site. Locate file(s) of interest and get them (Ive tried binary and ascii mode, cr and no cr) 3) uuencode file for transfer via kermit (cant do binary mode with Atalk3 Kermit!) 4) uudecode at home, try to uncomress, and poof, file is corrupted! Does anyone have any suggestions? p.s. A few files have been transfered this way and worked. Most do not though. Thank You! Dan Barber
#95945From: Pete MilesApr 17, 1993 4:08 AM
Dan, To ftp files form sits do the folowing for example. 1. Via an internet link ftp wuarchive.wustl.edu You will be asked for the login prompt so type ftp At the password type your machine name For myself I would type pmiles@cix.compulink.co.uk After a load of intro stuff you end up with the ftp> prompt. Find the directory you want then type binary at the prompt. Type Get filename and all things being equal your prog should be squirted down the line to you. Pete
#95997From: Deryk RobossonApr 17, 1993 3:05 PM
Dan, Here is they way that I FTP from my internet account: ftp wuarchive.wustl.edu You will be prompted for your username, either 'FTP' or 'ANONYMOUS' will do. Next, you will be prompted for a password. Either your InterNet address (ie jester@m-net.ann-arbor.mi.us) or any other character will do, as the system will tell you what it expects, but it doesn't care. The file area for ftp.wuarchive.wustl.edu for the Amiga section is 'BIN' for binary transfers. Then you type 'GET <filename>'. From there you must download the file from your account using your preference of protocols. I hope that this has helped! Deryk
#96283From: dan barberApr 19, 1993 8:36 PM
Thanks Deryk! I think I will try again tonight, but I haven't had much luck in decompressing those files! Maybe I should just drive into school and copy files directly to floppy! One interesting note though, when I ftp, it tells me how many bytes have been transfered. When I view the file size after ftp'ing, it matches what ftp told me it sent. However, when I use Kermit (text mode) to bring the file to my Amiga, the number of bytes sent is greater than the bytes of the file. There must be some overhead Kermit tacks on, or somethin. Still havin fun! Dan Barber
#96328From: Deryk RobossonApr 20, 1993 1:49 AM
Dan, Yeah, I think that Kermit pads the end of a file just like XModem. Someone correct me if I'm wrong ;). Now when you 'GET' the files from the FTP site, try using 'sz filename.lha' to send via ZModem from the mainframe. I'm assuming (note the word 🙂 ) that the terminal that you are using supports ZModem, if not, try another protocol other than Kermit. Now, if the files that you get are UU Encoded, you've got to get a program to decode these text files back into binary, called UU Decoding. I hope that I've helped ya out there Dan! If you need anything else, feel free to ask….if I can't answer it, I'm sure that some GURU here can. Deryk
#96867From: James Du BoisApr 23, 1993 2:10 AM
Deryk, Kermit doesn't pad the end of the file with blanks like XModem. In ASCII file mode, kermit will make sure all characters are within the 96 printable ASCII codes ( 32 – 128 ) so that the characters will make it past any devices that use the control codes for other purposes. To get a binary file I would use SET FILE TYPE BINARY and SET BLOCK-CHECK 3 on my machine and use REMOTE SET FILE TYPE BINARY and REMOTE SET BLOCK-CHECK 3 to make sure that both kermits were using the same attributes. If you don't make sure then you will wind up using the lowest common attribute, i.e. FILE TYPE TEXT and BLOCK-CHECK 1 since kermit will negotiate these things in the initial packet. James Du Bois via Whap!
#96337From: Marlene Zenker/SYSOPApr 20, 1993 6:23 AM
You should be using Kermit in binary mode. Type: set file type binary from within Kermit. Steve
#96282From: dan barberApr 19, 1993 8:36 PM
Thanks for the info Pete! I would like to say that the problem isn't getting the files to the internet site I am logged into, or even getting them downloaded to my Amiga, but after uudecoding and unarcing (lz), the decompression fails because the file is corrupted. It puzzles me because some things have downloaded successfully, the majority haven't however. Dan Barber
#96053From: Betty Clay/SYSOPApr 17, 1993 10:09 PM
It's been a long time since I had an Internet account, but I did transmit binary files with AtalkIII. I had to "set filetype binary" on the host before starting the download, but it worked fine.
#96284From: dan barberApr 19, 1993 8:36 PM
Thanks Betty, I will try that and see if it helps. If anything, your suggestion will help reduce the number of bytes transfered (uuencode). Dan Barber
#97009From: Jim DuttonApr 24, 1993 2:59 AM
Dan, If your mainframe is a U*ix host, you might try uudecoding there before transferring the file to your PC at home. You could also take care of any need to "uncompress" any .Z (or .TAR?) files. I have found in the past, that the Amiga based "uudecode" programs don't always work, but downloading the file to U*ix first and then decompressing it there, worked just fine. Real World:southern Illinois,USA Internet:ca0008 at siucvmb.siu.edu