🚀 go-pugleaf

In article <765@dukempd.phy.duke.edu> fang@dukempd.phy.duke.edu (Fang Zhong) writes:
>	I just found out that a chapter of my thesis writen with FullWrite 
>caused system bomb.  After I opened the file, FullWrite would say 'Updating..'
>then Error ID=25 came out. I checked that ID=25 is 'out of memory'. That can
>not be true, since the file is only 35 page long and our mac has 5MB ram. I
>used MacTools to verify the file. MacTools said that the file was ok.

I'm sorry I can't help you, but things like this have happened to me too.
Usually FullWrite does something like this when I use the indexing. Just
typing normal text and adding a few sidebars seems to be ok. Sometimes I
get a document that seems to be ok until I try to open a footnote. The
wrong text appears and the program usually crashes soon after that.

Aston Tate really needs to exterminate those bugs or write an interactive
program for rescuing FW documents. I could probably live with occasional
lost footnotes or index entries.

FW is great, but much too unreliable.


_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
|     Juri Munkki jmunkki@hut.fi  jmunkki@fingate.bitnet        I Want   Ne   |
|     Helsinki University of Technology Computing Centre        My Own   XT   |
~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~