Path: utzoo!attcan!uunet!super!udel!gatech!ncar!hao!hull
From: hull@hao.ucar.edu (Howard Hull)
Newsgroups: comp.sys.amiga
Subject: Re: Put ASpice on the stack list
Message-ID: <1131@ncar.ucar.edu>
Date: 14 Dec 88 01:10:00 GMT
References: <1117@ncar.ucar.edu> <4037e9fb.1285f@maize.engin.umich.edu>
Sender: news@ncar.ucar.edu
Reply-To: hull@hao.UCAR.EDU (Howard Hull)
Organization: High Altitude Observatory/NCAR, Boulder CO
Lines: 33

I am using the uudecode posted as 905@s.cc.purdue.edu (Craig Norberg)
v02i020 dated 8 Sep 87 18:08:25 GMT, modified and contributed by
Bryce Nesbitt, designed to emulate uudecode.c 5.3-1 (Berkley) 4/10/85

I was surprised to see the response to which this is a follow-up, so
I have not as yet had the opportunity to test to see if the problem
can be recreated.  I have a mix of 1.2 and 1.3 software on 1.2 ROMs
and have been experiencing a higher than normal crash rate lately.
Some of the crashes may be related to the Manx z editor and a VT100
v2.8 containing most of the "a" patches.  I just this weekend dredged
up my VT100 2.8 sources and the recently posted VT100 2.8diffs and
from it I produced a new executable under Manx 3.6a (it previously
was compiled under 3.4a).

I may not even be able to return to the environment I previously
had without going back to recompile under 3.4a.  I suppose it would
be nice if the problems were mine only; I just thought it worth the
trouble to notify the net of a potential difficulty.  Now that I've
redone VT100, my attention will turn to the matter of what to do about
the Manx z editor.  Most advice I got from the net was to get another
editor!  I have the stevie shar, so I may shortly try that...

Other than the uudecode stack incident originally reported, the ASpice
seems to load and run ok; I did get some out of memory errors on the
four stage counter example in CHAPTER 10 of the aspice.docs (with or
without three of the last four lines stripped to remove the memory/money
exerciser part).  This condition arose even though a memory monitor
(similar to mclk) I had running showed 2450K to start, 1900K with
spice loaded, 1600K with at the height of the spice crunching, and
all resources returned when done.  That remains as yet another mystery
to be investigated at the next opportunity.
						Howard Hull
						hull@hao.ucar.edu