TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: OK, Frame's the obvious choice f From:"PICKETT-HARNER, Molly" <MOP1 -at- NIORDS1 -dot- EM -dot- CDC -dot- GOV> Date:Thu, 19 Jan 1995 17:24:00 EST
This has never been a problem on my Mac. Can you increase your [Windows]
memory allocation for FrameMaker?
[This is easy to do when necessary w/Macs; however, because of automatic
memory swapping, hefty programs typically won't crash an appropriately
configured Mac.]
When you're swapping text in & out, if you haven't much/enough memory &/or
bring in a graphic that's too big for your allocation -- it's goodbye
document!
Molly Pickett-Harner
mop1 -at- niords1 -dot- em -dot- cdc -dot- gov
----------
From: TECHWR-L
To: Multiple recipients of list TECHWR-L
Subject: OK, Frame's the obvious choice f
Date: Thursday, January 19, 1995 7:52AM
In his negative run-down of FrameMaker (Windows), Patrick Brian O'Connell
didn't mention the worst bummer of all, namely, that the machine crashes
when
you "page" through graphic-heavy files.
