Path: utzoo!attcan!uunet!lll-winken!ames!xanth!mcnc!rutgers!att!alberta!ubc-cs!van-bc!root
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: Atalk III 1.0e
Message-ID: <2147@van-bc.UUCP>
Date: 15 Jan 89 09:25:12 GMT
Sender: root@van-bc.UUCP
Lines: 33

In <14652@oberon.USC.EDU>, papa@pollux.usc.edu (Marco Papa) writes:
> Auto Chop in general should hardly be used at all since most files on BBS are 
> now ARC-ed or ZOO-ed, especially all those animations.  "Chopping" an ARC or 
> ZOO file will always produce a "munged" last file.  If you are transferring 
> a single file, it will be munged and ZOO or ARC won't be able to decompress it
> properly. When running the resulting program one will get the dreaded
> "unable to load XXXX: file is not an objetc module".  Whatever program you
> are using, please turn auto-chop off for .ARC and .ZOO files.

Well Marco, it's unfortunate that your program mungs .ARC or .ZOO files, but I
can assure you that it is not the case with all terminal programs. The one I am
most familiar with, Aterm 7.3, definitely does not mung them. That was fixed
ages ago. I always receommend that people leave AutoChop enabled on Aterm,
because there are VERY few files that will ever be adversely affected.

Aterm does not require 'twice the space' to do autochop.

You are welcome to the source code for Aterm 7.3 if you are interested. If you
are not on CIS (or any network where it might also be), I'd be happy to mail it
to you.

> -- Marco Papa 'Doc'

-larry

--
Frisbeetarianism: The belief that when you die, your soul goes up on
                  the roof and gets stuck.
+----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                |
| \X/    lphillips@lpami.wimsey.bc.ca or uunet!van-bc!lpami!lphillips  |
|        COMPUSERVE: 76703,4322                                        |
+----------------------------------------------------------------------+