#: 11045 S10/OS9/6809 (CoCo)
    11-Jun-91  22:46:34
Sb: #11043-Zip and Unzip
Fm: James Jones 76257,562
To: MARK HAMILTON 70524,1507 (X)

To get both those messages, what probably had to happen is that the xmodem
transfer was OK, but, thanks to xmodem's being designed for CP/M, it left stray
junk at the end.  There are a couple of ways around this:

1. Assuming that the attributes are set, type "load ar".  ar will then be
   in memory even though you get an error message; the error message is
   caused by the trailing xmodem droppings.  Now, if you have the "save"
   program, you can "del /d0/cmds/ar; save ar" and you'll have just ar,
   ready to go.  Save is unbundled from OS-9 Level Two, but there are
   freely-copyable equivalents here.  (Catch-22?  No, because once you've
   loaded something, you can run it from memory, so you can "load save",
   and then save save as well as save ar.) 2. Look at the module length that
ident shows for ar.  Use a program like
   ded to chop the file /d0/cmds/ar to that length.

Method (1) is probably the safest, since you don't have to remember or write
down any lengths--load and save do it all for you.