Path: utzoo!attcan!uunet!super!udel!mmdf
From: phils%tekigm2.tek.com%CERNVAX.BITNET@cunyvm.cuny.edu
Newsgroups: comp.sys.amiga
Subject: Re: Long Standing Manx bug
Message-ID: <5711@louie.udel.EDU>
Date: 28 Nov 88 19:25:24 GMT
Sender: mmdf@udel.EDU
Lines: 47

In article <1037@ncar.ucar.edu> hull@hao.UCAR.EDU (Howard Hull) writes:
.. describes longstanding bug in z editor ...
>and it is STILL THERE.  &^%$#@! why can't he fix this sob?  The way it works
>is one types to the bottom of the page, and somehow, there, while typing
>furiously, the line gets too long.  Then, while one is still typing, the
>screen announces "cursor below page bottom" or something of that ilk.
>So what.  But THEN the keyboard stops responding and the red power light
>begins to flash (no requester) and one gets the Guru.  Has anyone else run
>into this beast?
Count me in.

>                  I have lost literally hours of very creative stuff this
>way, and have had great difficulty trying to remember what I put down.
Me too.

>ram: files or df0/1: files.  It strikes without warning.  There seems no
>way to recover the text...

>Sooooo.  Am I doing anything wrong?  Is this puppy another one of those
>stack sensitive ogres?
I seriously doubt it. I've had it happen with both very large and very small
stack sizes.

>                        Does anyone have a way of dumping ram: to a disk so
I once managed to dump memory to a disk file by calling up 'db' and doing a
memory dump, redirecting output to a disk file. It didn't help a whole
lot: I got a lot of scattered line fragments which took me nearly as long to
re-assemble as it would have taken to rebuild the original text.


>                    Howard Hull
>                    hull@hao.ucar.edu

If it's of any help, I usually am successful in avoiding the loss of
everything by noting that I have always encountered a delay of at least a
few keystrokes between the 'cur past bot' message and the crash. I make use
of this knowledge to do a quick 'write', then hit ^L to redraw the screen,
whenever I get the message. Somehow, this often avoids the Guru altogether.

However, I too would like a fix, not a work-around.

Phil
--
------------------------------------------------------------------------------
Phil Staub
Tektronix, Inc., Vancouver, Washington 98668
phils@tekigm2.MEN.TEK.COM