"FrameMaker has detected a problem and must quit" Really?!
Ken Poshedly
poshedly at bellsouth.net
Thu Feb 14 13:30:49 PST 2013
First, my thanks to all for your interest and participation in this matter.
Second, just to confirm that by "data file" I mean the book or chapter being
composed using FrameMaker. In our case, the FrameMaker program files are
installed on our respective desktop computers (I _hope_ that's the correct term,
ok?). The book and chapter files are located on a separate physical hard drive
which is one of my company's network drives. It's about a month old Western
Digital hard drive; specifically a "WD My Book Live Duo", Model WDBVHT0040JCH -
NAS Server - 4 terrabytes with hardly anything on it because we backed
everything onto another drive while this one was installed and have only moved
some stuff onto it.
Third, I know what I heard and I repeated it to the Adobe tech support rep. And
yes, he confirmed what I've stated here. FrameMaker 11 is such that the work
files (as I've described them above) should be on the same physical drive as the
FM 11 program files.
Fourth, my coworker has experienced no FM crashes since moving his work files to
his hard drive where his FM program files are also located. Also, his files now
seem to open and process far faster than before. Go figure. Maybe my FM 8.0
installation is more forgiving of some unknown cross-drive anomaly and my
coworker's FM 11.0 installation demands absolute perfection of all hardware and
software components. I don't know.
I'm sorry that there is so much disagreement, but as I also said, I will be glad
to provide this rep's name and e-mail address so any of you can follow up with
him on your own.
-- Ken in Atlanta
________________________________
From: Dov Isaacs <isaacs at adobe.com>
To: "framers at lists.frameusers.com" <framers at lists.frameusers.com>
Cc: "techwr-l at techwr-l.com" <techwr-l at techwr-l.com>
Sent: Thu, February 14, 2013 4:08:42 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
All,
Sorry I couldn’t respond to this thread earlier. Driving much of the day
yesterday and I don’t “do e-mail” while driving. J
I am seriously hoping that there was a serious misunderstanding between Ken
Poshedly and the tech support person he spoke with. Maybe a language issue one
of a definition of what a “data file” is.
For the record, there is absolutely no restriction in FrameMaker – any version –
as to where FrameMaker document files (.fm files), FrameMaker book files, or any
assets used by same may reside on a user’s system. As long as Windows can open
the file for input and output, FrameMaker can open the document or book.
FrameMaker documents may be on the system volume or any other volume available
under Windows including external drives, SSDs, thumb drives, network shares,
etc.
Then there are the “data files” used internally by FrameMaker including those
in<X:\Program Files (x86)\Adobe\AdobeFrameMaker11\fminit> whereX:\Program Files
(x86)\Adobe\AdobeFrameMaker11 is the location where you designate that
FrameMaker be installed
and<C:\Users\username\AppData\Roaming\Adobe\FrameMaker\11> where username is
the user’s Window login ID. Maybe there was some issue of what happens if you
designate a location for FrameMaker installation that isn’t the system volume or
if you move the<C:\Users\username>directory to someplace other than the system
volume. I have not experienced problems with FrameMaker 11 installed on a volume
other than the system volume. I have not attempted to muck around with location
of the<C:\Users\username>directory which could be playing with fire with not
only FrameMaker, but other Windows applications.
Nonetheless, assuming a reasonably normal installation of FrameMaker 11, you
should have no problem with storing your FrameMaker documents and associated
assets anywhere that you can open a file within your system’s file system.
- Dov
Dov Isaacs
Principal Scientist
Adobe Systems Incorporated +1 408.536.2896 (tel)
+1 408.242.5161 (cell)
isaacs at adobe.com 345 Park Avenue
San Jose, CA 95110-2704 USA
http://www.adobe.com
Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.
ISAACS-OFFICE.corp.adobe.com
From:framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Dave.Stamm at gdc4s.com
Sent: Wednesday, February 13, 2013 11:50 AM
To: framers at lists.frameusers.com; techwr-l at techwr-l.com
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
2013-02-13-03T19:50Z
¡_YIKES_!
If Ken was informed correctly, below — and I _really_ hope he was _not_ — then
that effectively rings the death knell of FrameMaker’s use by my employer.
It was in only the last month that I got upgraded to FrameMaker 11, but I’m
happy to report that I haven’t encountered this type of problem. To conform to
_corporate_requirements_ we have FrameMaker installed on our C:\ drives, but the
files we produce and edit are on a server, so we work with them across our local
area network and, sometimes, the wide-area network.
Dov, if you see this, will you please confirm, modify, or refute the information
Ken posted below?
¡Thanks!
Dave Stamm
Information Engineer
General Dynamics C4 Systems, Inc.
Integrated Log Engr Svc, Logistics Section
1700 Magnavox Way, Suite 200 We'll hit your targets from here.™
Fort Wayne, Indiana 46804-1552; US
tel: 260-434-9620 fax: 260.434.9501 / 9509
dave.stamm at gdc4s.com http://www.gdc4s.com/
This message and / or attachments may include information subject to GDC4S S.P.
1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed only by
authorized recipients. Use, storage and transmission are governed by General
Dynamics and its policies. Contractual restrictions apply to third parties.
Recipients should refer to the policies or contract to determine proper
handling. Unauthorized review, use, disclosure or distribution is prohibited.
If you are not an intended recipient, please contact the sender and destroy all
copies of the original message.
From:framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Syed Zaeem Hosain
(Syed.Hosain at aeris.net)
Sent: 2013-02-13-Wednesday 14:24
To: Fred Ridder; poshedly at bellsouth.net; robert at lauriston.com;
framers at lists.frameusers.com; techwr-l at techwr-l.com
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly <poshedly at bellsouth.net> wrote:
> I just learned from Adobe tech support (via phone call) that the permissions
in
> FrameMaker 11.0 have been modified so that the data files should also be on
the
> same hard drive where FM 11.0 is installed. Working across drives (FM here,
>data
> files there) is no longer an accepted practice -- at least not with FM11.
Seriously? I can understand network-based locations causing issues, but I have
_never_ seen a problem where an executable (FrameMaker or otherwise!) is on one
drive and the “data” files are on a separate drive _on the *same* system_.
In fact, I do this right now – my C drive is the usual location for all
executables (FrameMaker, Office, compilers, etc.) and my E drive contains all my
other files (including the books and files I work on).
And, I do not have any problems with this setup whatsoever. I am surprised that
Adobe thinks that this would be a problem in any way! If really accurate, this
would be a strange, and completely unacceptable, artificial constraint.
Z
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130214/472a7b22/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 871 bytes
Desc: image001.png
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130214/472a7b22/attachment.png>
More information about the framers
mailing list