youngb@pur-ee.UUCP (H. Bret Young) (05/04/88)
I just downloaded the fileto update the lattice 4.00 compiler to 4.01. It is file amfix400.arc on the lattice BBS. When I looked at the archive with "arc -v amfix400.arc" I got a big list of files and then some message like: don't know what to do with file yyyyyyyy you may need a newer version of arc. I used the arc off of the lattice BBS. The ARC program worked so I think the arc file is corrupted or I did something wrong. Has anyone had this problem with the arc file obtained from the lattice BBS? Did you find out what's wrong? Any help? Thanks, Bret usenet: ihnp4!pur-ee!youngb ARPA: youngb@eg.ecn.purdue.edu UUCP: youngb@pur-ee.UUCP
rminnich@udel.EDU (Ron Minnich) (05/05/88)
In article <8055@pur-ee.UUCP> youngb@pur-ee.UUCP (H. Bret Young) writes: >Has anyone had this problem with the arc file obtained from the >lattice BBS? Did you find out what's wrong? Any help? Yup, my amiga arc choked on it. Actually it reported an error but all the files were ok. Arc on a vax was just fine. If you can pull it to a vax de-arc it there. From there on you should be fine. ron -- ron (rminnich@udel.edu)
sbower@lehi3b15.UUCP (Steve Bower) (05/05/88)
In article <8055@pur-ee.UUCP> youngb@pur-ee.UUCP (H. Bret Young) writes: I just downloaded the fileto update the lattice 4.00 compiler to 4.01. It is file amfix400.arc on the lattice BBS. When I looked at the archive with "arc -v amfix400.arc" I got a big list of files and then some message like: don't know what to do with file yyyyyyyy you may need a newer version of arc. I used the arc off of the lattice BBS. The ARC program worked so I think the arc file is corrupted or I did something wrong. Has anyone had this problem with the arc file obtained from the lattice BBS? Did you find out what's wrong? Any help? Thanks, Bret I believe the "problem" is that (most versions of) xmodem work in ONLY 128-byte blocks, so any file that's sent gets padded with 0s or EOFs up to the next multiple of 128 bytes. This issue is most important when xferring executables (hence the program fixobj to get rid of those bytes). I encountered the same problem you describe, and it doesn't seem to affect the integrity of the archive. In other words, probably nothing to worry about. Steve. -- | Steven K. Bower | sbower@lehi3b15.uucp | The ideas presented | | Box 876, Lehigh Univ. | luskb@vax1.cc.lehigh.edu | herein aren't neces-| | Bethlehem, PA 18015 | luskb@lehiibm1.bitnet | sarily the ideas | | (215)758-1921 | bix: skbower | presented herein. |