Afterthoughts are always enlightening.
I don't think I've ever seen anyone reporting this problem describe the
other main applications - like MS office apps, and utilities, browsers,
messaging tools, background agents like Acrobat's watched folder daemon,
etc. - that are running at the same time
using Adobe FrameMaker
software.
Subject: [EXTERNAL] Re: [Framers] FrameMaker crashes
!---|
This message is from an external sender
This email originated from outside of the organization.
Do not click links or open attachments
and start fresh
in the morning; it’s Windows!
Craig
From: Framers on
behalf of Bertrand Meyer (SIT)
Sent: Monday, October 3, 2022 7:16 AM
To: 'An email list for people using Adobe FrameMaker software.'
Cc: me...@inf.ethz.ch
Subject: [Framers] FrameMaker crashes
I
I remember FM in 1999 and also 1989!
It's not likely that Adobe will find and fix this longtime issue soon. But
if you haven't reported it to the bug site, and discussed it with tech
support, it's worth a try.
A kludgy workaround might be to create a Windows/DOS batch file that
launches FM and
software.
Cc: me...@inf.ethz.ch
Subject: Re: [Framers] FrameMaker crashes
Hello,
I have observed the same behaviour at my customer's offices since at least
FrameMaker 14. They have some high end HP workstations with heaps of RAM,
very large displays [4K+], with fast graphic cards.
What
Hello,
I have observed the same behaviour at my customer's offices since at
least FrameMaker 14. They have some high end HP workstations with
heaps of RAM, very large displays [4K+], with fast graphic cards.
What happens is that the display of the FrameMaker document will become
corrupted
> Does anyone know any way to present them from happening?
Sorry, I obviously meant "prevent".
-- Bertrand Meyer
From: Bertrand Meyer (SIT)
Sent: Monday, 3 October, 2022 14:16
To: 'An email list for people using Adobe FrameMaker software.'
Cc: me...@inf.ethz.ch
Subject: FrameMaker
I have the very latest version of FrameMaker (Windows) and it still, like
earlier versions, freezes after a few days of use, unpredictably, with a
botched-up display (see example below) and no responsiveness. I have to kill
the process with the Task Manager, get rid of *.lck files, get rid of the
