David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer) (12/24/90)
I'm having some difficulty connecting to ux1.cso.uiuc.edu where the Fish disks are supposedly located. It says my site is not registered, and to contact my administrator. Unfortunately, I doubt that Amiga software is a big priority at my university :-( so is there a way I can get around this, or is there somewhere else I can obtain the fish disks? Thanks a lot, Dave Plummer (Please don't assume this is common knowledge... if you know, please respond!) -- David Plummer - via FidoNet node 1:140/22 UUCP: ...!herald!weyr!70!David.Plummer Domain: David.Plummer@f70.n140.z1.FIDONET.ORG Standard Disclaimers Apply...
etxtomp@eos.ericsson.se (Tommy Petersson) (12/27/90)
In article <1033.27783F09@weyr.FIDONET.ORG> David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer) writes: >I'm having some difficulty connecting to ux1.cso.uiuc.edu where the >Fish disks are supposedly located. It says my site is not registered, >and to contact my administrator. Unfortunately, I doubt that Amiga >software is a big priority at my university :-( so is there a way I >can get around this, or is there somewhere else I can obtain the >fish disks? I have another ftp problem, maybe it could be answered at the same time? :-) Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by email and UUdecode it (I have tried both on a SparcStation and on my Amiga). The files are transferred from Sparc to MS-DOS diskettes using mtools, which has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which also has binary transfer as default. All files are corrupted, but not totally screwed up. If I have UUdecoded a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the archive before complaining about corrupt file. I have gotten one program (HamSharp, thanks!) by 'normal email' (not from the BITFTP server). I UUdecoded it on the Sun4 and moved it to my Amiga. It ran without any problems. Anyone with a solution? It seems like the ftp pucc does gives corrupted files, but if it were so, surely many other people would have run into it and complained? Thanks in advance, Tommy Petersson etxtomp@eos.ericsson.se
david@starsoft.UUCP (Dave Lowrey) (12/27/90)
In article <1990Dec26.172922.17717@ericsson.se>, Tommy Petersson writes: > In article <1033.27783F09@weyr.FIDONET.ORG> David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer) writes: > >I'm having some difficulty connecting to ux1.cso.uiuc.edu where the > >Fish disks are supposedly located. It says my site is not registered, > >and to contact my administrator. Unfortunately, I doubt that Amiga > >software is a big priority at my university :-( so is there a way I > >can get around this, or is there somewhere else I can obtain the > >fish disks? > > I have another ftp problem, maybe it could be answered at the same time? :-) > > Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for > me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by > email and UUdecode it (I have tried both on a SparcStation and on my Amiga). > The files are transferred from Sparc to MS-DOS diskettes using mtools, which > has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which > also has binary transfer as default. > > All files are corrupted, but not totally screwed up. If I have UUdecoded > a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the > archive before complaining about corrupt file. > > I have gotten one program (HamSharp, thanks!) by 'normal email' (not from > the BITFTP server). I UUdecoded it on the Sun4 and moved it to my Amiga. > It ran without any problems. > > Anyone with a solution? It seems like the ftp pucc does gives corrupted > files, but if it were so, surely many other people would have run into > it and complained? > I suspect your file transfer techniques have a flaw, or you aren't "re-assembling" the files correctly. First, are you sure that the file from BITFTP is corrupted? Can you transfer a known good binary file (such as a zoo file)from your Sparc to the Amiga, and have it arrive intact? When you uudecode the files from BITFTP, do they appear "whole" on the Sparc (does Zoo work ok on it on the Sparc)? The only problems I had with files from BITFTP was when I was using an editor to put the segments together, and the editor replaced blanks with tabs! ---------------------------------------------------------------------------- These words be mine. The company doesn't care, because I am the company! :-) Dave Lowrey | david@starsoft or {uhnix1,lobster}!starsoft!david Starbound Software Group | Houston, TX | "Dare to be stupid!" -- Weird Al Yankovic
etxtomp@eos.ericsson.se (Tommy Petersson) (12/27/90)
In article <186ce17d.ARN253b@starsoft.UUCP> david@starsoft.UUCP writes: >In article <1990Dec26.172922.17717@ericsson.se>, Tommy Petersson writes: > >> In article <1033.27783F09@weyr.FIDONET.ORG> David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer) writes: >> >I'm having some difficulty connecting to ux1.cso.uiuc.edu where the >> >Fish disks are supposedly located. It says my site is not registered, >> >and to contact my administrator. Unfortunately, I doubt that Amiga >> >software is a big priority at my university :-( so is there a way I >> >can get around this, or is there somewhere else I can obtain the >> >fish disks? >> >> I have another ftp problem, maybe it could be answered at the same time? :-) >> >> Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for >> me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by >> email and UUdecode it (I have tried both on a SparcStation and on my Amiga). >> The files are transferred from Sparc to MS-DOS diskettes using mtools, which >> has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which >> also has binary transfer as default. >> >> All files are corrupted, but not totally screwed up. If I have UUdecoded >> a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the >> archive before complaining about corrupt file. >> >> I have gotten one program (HamSharp, thanks!) by 'normal email' (not from >> the BITFTP server). I UUdecoded it on the Sun4 and moved it to my Amiga. >> It ran without any problems. >> >> Anyone with a solution? It seems like the ftp pucc does gives corrupted >> files, but if it were so, surely many other people would have run into >> it and complained? >> > >I suspect your file transfer techniques have a flaw, or you aren't >"re-assembling" the files correctly. I have one small program, UUCode.zoo. It's only in one mail file, and I just remove lines above and including the ----cut---- line. (it gives the same result even if I don't edit the file. So, re-assembling problems are out. (I'm not angry, I asked for help and suggestions...). As for the transfer techniques, see below. > >First, are you sure that the file from BITFTP is corrupted? Not really, and I have never said so. But it seemed like the only thing I could come up with, that I hadn't already tested. > >Can you transfer a known good binary file (such as a zoo file)from your Sparc > to the Amiga, and have it arrive intact? I have transferred the HamSharp program, which I got by 'personal email'. > >When you uudecode the files from BITFTP, do they appear "whole" on the >Sparc (does Zoo work ok on it on the Sparc)? > This machine actually didn't have a compiled zoo program. I found the source code in an archive and compiled (today). The same result: Archive UUCODE.ZOO: Length CF Size Now Date Time -------- --- -------- --------- -------- 2675 32% 1820 22 Aug 87 15:38:44 3964 UUEncode/POSTER 385 22% 301 22 Aug 87 15:38:32 5e4c UUEncode/README.fnf* Zoo: FATAL: Archive UUCODE.ZOO: Directory entry in archive is invalid. -------- --- -------- --------- -------- 3060 31% 2121 2 files ------------ *: directory entry may be corrupted. The irritating part of this is that I'm (almost) sure that UUCode.zoo was a file I didn't get through BITFTP... >The only problems I had with files from BITFTP was when I was using >an editor to put the segments together, and the editor replaced >blanks with tabs! > That would be a very possible error source, if it wasn't that I get the same result if I don't edit the file at all. Now it looks more like a problem with Sun's mailtool here, but it has worked perfectly once (on HamSharp)... > >---------------------------------------------------------------------------- >These words be mine. The company doesn't care, because I am the company! :-) > > Dave Lowrey | david@starsoft or {uhnix1,lobster}!starsoft!david >Starbound Software Group | > Houston, TX | "Dare to be stupid!" -- Weird Al Yankovic Tommy Petersson etxtomp@eos.ericsson.se
king@motcid.UUCP (Steven King) (12/28/90)
In article <1990Dec26.172922.17717@ericsson.se> etxtomp@eos.ericsson.se writes: >Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for >me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by >email and UUdecode it (I have tried both on a SparcStation and on my Amiga). >The files are transferred from Sparc to MS-DOS diskettes using mtools, which >has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which >also has binary transfer as default. > >All files are corrupted, but not totally screwed up. If I have UUdecoded >a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the >archive before complaining about corrupt file. I use Bitftp all the time, and haven't found any problems so far. I suspect you're not stripping the headers off the messages before you uudecode them. Uudecode is a rather dumb program. There's almost no error checking done whatsoever. Bitftp splits large files into multiple segments. If you just cat the segments together and then uudecode the large file, UUDECODE WILL TREAT THE MAIL HEADERS AS DATA AND DECODE THEM! Naturally this will mess up the files. You've got to make sure you strip out everything that's NOT uuencoded text. Anything between the "begin" and "end" lines is fair game to be decoded. Good luck! -- ---------------------------------------------------+--------------------------- They're furry, they're funny | Steven King They're Babs and Buster Bunny... | Motorola Cellular (Unabashed "Tiny Toon Adventures" plug) | ...uunet!motcid!king
etxtomp@eos.ericsson.se (Tommy Petersson) (12/28/90)
In article <5944@orchid3.UUCP> king@motcid.UUCP (Steven King) writes: >In article <1990Dec26.172922.17717@ericsson.se> etxtomp@eos.ericsson.se writes: >>Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for >>me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by >>email and UUdecode it (I have tried both on a SparcStation and on my Amiga). >>The files are transferred from Sparc to MS-DOS diskettes using mtools, which >>has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which >>also has binary transfer as default. >> >>All files are corrupted, but not totally screwed up. If I have UUdecoded >>a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the >>archive before complaining about corrupt file. > >I use Bitftp all the time, and haven't found any problems so far. I >suspect you're not stripping the headers off the messages before you >uudecode them. Uudecode is a rather dumb program. There's almost no >error checking done whatsoever. Bitftp splits large files into >multiple segments. If you just cat the segments together and then uudecode >the large file, UUDECODE WILL TREAT THE MAIL HEADERS AS DATA AND DECODE >THEM! Naturally this will mess up the files. You've got to make sure >you strip out everything that's NOT uuencoded text. Anything between >the "begin" and "end" lines is fair game to be decoded. > >Good luck! > No, that's not the problem. I have sent so many files using UUencode/decode before, so it's not any simple mistakes like that. However, I've now tried with Unix lharc on a large file on Sun, and it seems OK. I haven't bothered to move it to my Amiga, since lharc.zoo came corrupted... Our UUdecode on Sun isn't that stupid, if I try and just UUdecode the catenated file, it complains. The UUencode program at pucc is a bit sloppy, though. It only puts a begin line at the top of the first part, and an end at the bottom of the last part. So current status: BITFTP: 8 files received, 4 corrupt, 4 seems OK on Sun (lharced) MAIL: 10 files received, 1 corrupt, 6 OK, 3 lharced seems OK on Sun It's not so clear-cut any more... I've got several email's (and postings) with help. It seems like several of the chains in the link works OK most of the time, but may fail. If there is such a long chain as I use, almost every time there may be a new (small but fatal) error. Well, now that it seems like I've gotten files from bitftp that are not corrupted, things look a little better. If only I will be able to get lharc and a better UUdecode for my Amiga that's not corrupted... I got a KillChip utility, but it crashes the machine. Can anyone please send that or a similar program to me (again)... And/or tell me at which jumper I should solder a hardware switch... I thank everyone for the help I received, and hope the problem was more like temporary hickups in an involved machine. I'll be back with more problems next week! (wonder if I should choose WordSync or HAM-E...) Tommy Petersson etxtomp@eos.ericsson.se
GELSON%SBU.UFRGS.ANRS.BR@uicvm.uic.edu (Gelson Dias Santos) (12/28/90)
>"etxtomp@eos.ericsson.se" "Tommy Petersson" write: >>In article <1033.27783F09@weyr.FIDONET.ORG> >> David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer) writes: >>I'm having some difficulty connecting to ux1.cso.uiuc.edu where the >>Fish disks are supposedly located. It says my site is not registered, >>and to contact my administrator. Unfortunately, I doubt that Amiga >>software is a big priority at my university :-( so is there a way I >>can get around this, or is there somewhere else I can obtain the >>fish disks? >I have another ftp problem, maybe it could be answered at the same time? :-) > >Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for >me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by >email and UUdecode it (I have tried both on a SparcStation and on my Amiga). >The files are transferred from Sparc to MS-DOS diskettes using mtools, which >has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which >also has binary transfer as default. > >All files are corrupted, but not totally screwed up. If I have UUdecoded >a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the >archive before complaining about corrupt file. > >I have gotten one program (HamSharp, thanks!) by 'normal email' (not from >the BITFTP server). I UUdecoded it on the Sun4 and moved it to my Amiga. >It ran without any problems. > >Anyone with a solution? It seems like the ftp pucc does gives corrupted >files, but if it were so, surely many other people would have run into >it and complained? >Tommy Petersson >etxtomp@eos.ericsson.se 1) To David Plummer : Try BITFTP ... :-) 2) To Tommy Petersson: This is a quote from BITFTP helpfile. Sorry if it is too obvious, but you didn't tell you have tried it... "If BITFTP sends you a file you a uuencoded file that you cannot uudecode, the fist thing to do is to translate all occurences of 0x7E in the file to 0x5E and then try uudecoding again. (some gateways are changing 5Es to 7Es when files pass through them.)" ================================================================================ ***** # Gelson Dias Santos # /\/\ ** # BITNET: GELSON@SBU.UFRGS.ANRS.BR # Please, don't look my / \-------\* # HOME: Av. Bento Goncalves 948/12 # grammar/spelling errors. ! 0 0 ! _ ! # Porto Alegre - RS CEP:90620 # I am learning english ! ! ^^ ! ( ! # Brazil # \_()_/ _( ) #============================================================= (__(____(_____) # Alguem ai fala portugues? # =======================================================
king@motcid.UUCP (Steven King) (12/28/90)
In article <1990Dec27.141152.8028@ericsson.se> etxtomp@eos.ericsson.se writes: >[The editor] would be a very possible error source, if it wasn't that I get the >same result if I don't edit the file at all. Now it looks more like a >problem with Sun's mailtool here, but it has worked perfectly once (on >HamSharp)... I don't think I'd blame mailtool. Love it or hate it, I've never had it corrupt a file on me. This includes mailtool running under SunOS 3.x and under 4.x. Try editting the file. Just scan through it once, looking for defects. Corruption is often easy to see and sometimes simple to correct, say if you've got a blank line in there or something. There's also an inconsistency somewhere along the lines with uuencode. I've noticed it primarily on uuencoded .lzh files, but it may occur with others. Try converting all tildes "~" to carets "^" (or vice-versa). This is one form of "corruption" I've run into. I think it might stem from ASCII <--> EBCDIC conversions somewhere across the net. Then again, this file may actually be unrepairably corrupted. Sorry, you lose. -- ---------------------------------------------------+--------------------------- If Shakespeare were alive today he'd be writing | Steven King scripts for "Three's Company". | Motorola Cellular | ...uunet!motcid!king
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (12/30/90)
In <5954@orchid3.UUCP>, king@motcid.UUCP (Steven King) writes: >In article <1990Dec27.141152.8028@ericsson.se> etxtomp@eos.ericsson.se writes: >>[The editor] would be a very possible error source, if it wasn't that I get the >>same result if I don't edit the file at all. Now it looks more like a >>problem with Sun's mailtool here, but it has worked perfectly once (on >>HamSharp)... > >Try editting the file. Just scan through it once, looking for defects. >Corruption is often easy to see and sometimes simple to correct, say if you've >got a blank line in there or something. Another possibility are what look like 'short lines', but are actually lines that end with one or more spaces. MailTool won't mung a file this way, but you never know where the file has been before it got to you. It could have come through a machine/program that strips off trailing spaces. -larry -- The best way to accelerate an MsDos machine is at 32 ft/sec/sec. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+