mjp@spice.cs.cmu.edu.UUCP (02/27/87)
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"
cjp@vax135.UUCP (02/27/87)
John Wilkes writes: > Seems like every time I run the shar program to unshar some wonderful > thing from the net, the guru visits. I've noticed shar guruing immediately and repeatably when shar is in ram: or Perry's rrd. If instead shar is brought in from disk for the run, it completes. This is while unshar-ing source and dest on df1:. Most peculiar. I've also encountered mysterious gurus on occasion, such as crashing when I remove WB from df0: (light off). Shar might be the culprit? Configuration: 512K + 512K Alegra, external drive, pm, popcli-II, rrd. Charles Poirier
hull@hao.UUCP (02/28/87)
Looks like ye olde Stack problem again. I was having a lot of trouble with
shar -u fetching the Guru on the second use with v1.1; in some cases I had
to load it into Ram: and execute from there, as it would crash when/if fetched
from the disk. Under v1.2 it croaked even more readily. One day when I just
happen to have had enough sleep and was thinking somewhat more clearly, the
question of STACK miraculously popped into my otherwise impenetrable brain.
I typed "Stack 15000" ran it again (from the disk) and it WORKED. I suppose
that it didn't occur to me to try Stack because it ran ok the first time for
some invocations. Oh well.
Howard Hull
[If yet unproven concepts are outlawed in the range of discussion...
...Then only the deranged will discuss yet unproven concepts]
{ucbvax!hplabs | decvax!noao | mcvax!seismo | ihnp4!seismo} !hao!hull
hull@hao.ncar.edupage@ulowell.UUCP (02/28/87)
cjp@vax135.UUCP (Charles Poirier) wrote in article <1781@vax135.UUCP>: >I've noticed shar guruing immediately and repeatably when shar is in >ram: or Perry's rrd. If instead shar is brought in from disk for the >run, it completes. I've had it guru on df0, df1, dh0 and ram. Haven't tried PIPE. :-) It usually gurus right away, but sometimes I can get the first file off, then it crashes after it says "Creating" . Sigh. Time to take out Metascope... I'm sick of unsharing things by hand, although mg1a helps a lot. ..Bob PS Anyone writing sed (Unix stream editor) for the Amiga? Just a thought... -- Bob Page, U of Lowell CS Dept. ulowell!page, page@ulowell.CSNET