Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!hplabs!hpfcdc!hpfclm!gillam
From: gillam@hpfclm.HP.COM (Larry Gillam)
Newsgroups: comp.sys.apple
Subject: Re: Appleworks GS question
Message-ID: <11270007@hpfclm.HP.COM>
Date: 5 Jan 89 20:27:59 GMT
References: <8901031338.AA15074@mitre.arpa>
Organization: Hewlett Packard -- Fort Collins, CO
Lines: 44


I received AppleworksGS for Christmas, and I'm generally happy with it so far,
although I've had 2 crashes, one when the "Frantic" freeware NDA was 
accidentally activated, and one other that if it repeats itself I will 
document.  A question I had concerns printing (actually I have 2 questions).  
First, why does underlined text come out printed twice when printing a 
spreadsheed in draft mode (on the same line).  This appears to be a bug.  
Ideally it would be nice if underlining was supported, but at least it should 
just print out as normal text.

	I to, was having problems with the draft mode. Mine were with the
	the word processing module. I became VERY frustrated and finally
	got through to Claris(wasn't easy!) Their tech. rep. told me that
	that there is a KNOWN bug when using the draft mode. My problems
	arose when I tried to print more than one page and using different
	fonts. I was told, by Claris, not to use the draft mode. The problem
	had to do with some driver supplied by Apple(?). Claris was working
	with Apple to resolve the problem. When, I don't know. I have stopped
	using the draft mode and have had no problems. Although, it's painful
	waiting for the "optimized"(?) driver to finish. I'd hate to see
	how long it would take to not use the "optimized" driver! 

	Another observation....I'm running out of RAM DISK and after an
	afternoon of changing from module to module, I found that I wasn't
	able to successfully load a previously generated text file(1.5 pages).
	When opened, I got the "busy" icon and it never went away. After
	5 min. I did a apple-control-reset and came back into the WP module.
	Re-opened it and it loaded just fine. Hmmm.....I went into the
	Control panel and looked at free RAM and it said 1.46MB. Looked OK, 
	but I suspected I had run out of system RAM, so I did some playing 
	around and discovered that as I opened and closed windows the RAM 
	free was decreasing....never increasing. It appeared that the RAM 
	was not being released when a module session was closed! The ONLY 
	way I was able to free the RAM was to go the FILE menu and "Quit". 
	When the package was re-started the RAM was then available. I don't 
	think I should have to go the trouble of "quiting" to be able to free 
	enough RAM to load a document! I certainly hope this is fixed in later 
	releases. 


					Larry