Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!seismo!rochester!pt.cs.cmu.edu!spice.cs.cmu.edu!mjp
From: mjp@spice.cs.cmu.edu.UUCP
Newsgroups: comp.sys.amiga
Subject: problems with shar
Message-ID: <1149@spice.cs.cmu.edu>
Date: Fri, 27-Feb-87 00:18:19 EST
Article-I.D.: spice.1149
Posted: Fri Feb 27 00:18:19 1987
Date-Received: Sun, 1-Mar-87 07:42:27 EST
Reply-To: mjp@spice.cs.cmu.edu (Michael Portuesi)
Organization: Carnegie-Mellon University, CS/RI
Lines: 51

Keywords:

John Wilkes writes:

> Seems like every time I run the shar program to unshar some wonderful
> thing from the net, the guru visits.  Usually the Amiga croaks almost
> immediately when shar is run, but on a fresh boot, it seems like shar
> will run to completion one time, then the guru visits with the next
> program, whatever it happens to be.  Almost always get a 4 in the left
> half of the guru number (illegal instruction) but the address varies some.
> This is with 1.2R, and workbench not loaded.  If memory serves, this did
> not happen (at least not as consistently) with 1.2G and earlier.  Certainly
> did not happen with 1.1.  A colleague uses the RRD and has the same problem,
> but he always gets a 3 in the left half of the guru number.  

I have the same problem you describe with shar.  The only thing I've
noticed is that I've had the problem with both 1.1 *and* 1.2.  I have
1.2R, and shar usually functions about two or three times before
killing the machine.  Only copying a new version of the executable on
my workbench disk solves the problem.

> Oh yes, the shar program is whatever appeared in comp.sys.amiga some time
> ago, and was compiled with Lettuce 3.03 (or whatever the latest pre-3.10
> version was).  

I assume you are using the version written by Dave Wecker, of vt100
fame.  My version is compiled using Manx version 3.20a.  I sent mail
to Dave describing my plight; he never heard of the problem until I
mentioned it.  Since then, I've been keeping a careful watch on shar's
behavior to try to discover some cause for it.  I've noticed that
un-SHARing a file from ram: makes the machine die very often (.sh file
in ram:, destination directory on df0:) while disk-to-disk (.sh in
df0:, destination on df0:) tends to work much more reliably.  However,
shar did crash the system unSHARing the sources to vt100 2.6
disk-to-disk.  I haven't tried un-sharing a file using the RRD, as my
memory configuration isn't big enough to perform such feats.

BTW, my configuration is:  1.2R, 512K, 68010, one drive.  Shar failed
with 1.1 under the same hardware configuration and with a 2
drive/68000 system.

If I make any amazing discoveries, I'll post (and notify Dave!)

					--M

-- 

Mike Portuesi / Carnegie Mellon University Computer Science Department
ARPA:	mjp@spice.cs.cmu.edu
UUCP:	{harvard | seismo | ucbvax | decwrl}!spice.cs.cmu.edu!mjp
BITNET:	s314mp1u@cmccvb (but only if you must)

"Amiga hackers do it graphically, with lots of sound effects"