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: Automatic Backups in FrameMaker From:Laurie Rubin <lmr -at- SYL -dot- NJ -dot- NEC -dot- COM> Date:Fri, 4 Nov 1994 14:04:08 -0500
My experience with those gray captured graphics frames...
I've received them in my files, but wasn't so concerned as I assumed they were
primarily used as placeholders for memory conservation (captured graphics do
take up alot of memory, well, I'm am not so sure for referenced files).
When I get a gray graphic -- not more than one every so often in a file -- I
open the Object Properties option under Graphics, and click on the Set button.
The actual graphic replaces the grey frame. I have not lost a single
captured graphic file (and all are referenced) as a
result of the procedure I just described.
Laurie
> Paul MacGyver asked:
> >For those of you who use FrameMaker, do you have Frame configured to
> >do automatic backups for each document? If so, why?
> We do not have Frame configurd for automatic backups where I work. The reaso
> n
> is much as you have stated. We do frequent tape backups, and have had high
> reliability of the system (so far!), and the automatic backup documents
> would end up taking up more space.
> On the other hand....
> There's a specific problem that we haven't encountered here, but I did have
> come up frequently while doing contract work earlier this year. It deals wit
> h
> imported graphics. For reasons I never fully understood, Frame would sometim
> es
> do nasty things to graphics in anchored frames. We'd suddenly see the image
> turn to a "grey box." (Lots of us have seen that, I know.) If the graphic wa
> s
> imported by reference, though, Frame would suddenly and maliciously go to the
> original graphic file, reach into the file, and trash the file. And not just
> the graphic on the page I was viewing, -all- graphics in that Frame file.
> You read that correctly. Frame would destroy files separate from the Frame
> document file, even if those files were located in a different directory than
> theFrame document. (Frame tech support, BTW, assured me that "this could
> not be happening." It happened more than once.)
> In those cases, I was sometimes able to save a day's work by reverting to the
> back-up, -if- I could exit without saving before Frame automatically updated
> the auto backup file.
> If you have the slightest hint of this problem, go with the autobackup featur
> e.
> If not, then balance the possible loss against the consumption of hard drive
> space.
> Rick Lippincott
> Eaton Semiconductor
> rlippinc -at- bev -dot- etn -dot- com