"FrameMaker has detected a problem and must quit" Really?!

[Ken Poshedly]

To all,

I will be glad to supply the specific adobe.com e-mail address for the service 
tech (Shekhar, in India) that I talked with earlier today (Wednesday) in private 
(off-list) e-mails.

He was very professional, seemed to understand the specifics of my problem and 
even phoned me right back when our call dropped.

I also provided him with the specific internal error numbers that came up in the 
FM 11.0 crash notification pop-up window. (They were the same at each crash.)

He then confirmed what I described and asked if I could be placed on "hold" 
while he checked into it.

I was on hold perhaps no more than a minute when he came back on the line and 
told me that the fix is to place the working files on the same hard drive where 
FM 11.0 is installed.

I inquired as to if he is sure about this and he agreed without hesitation, 
saying this was sp[ecific with FM 11.0 (I don't recall if it does or will apply 
to FM 12.0.)

As I described in another e-mail here, that SEEMS to have cleared up my 
coworker's problem. It's been an hour or so since he got back into things and so 
far, no more crashes.

Please note that my coworker's FM crash problems occurred intermittently, 
perhaps several times a week and not all day every day, so we'll have to see 
what happens over the next few days, etc.

I'm still on FM 8.0 and because I like the user interface as it is and I've had 
no crash problems, I might just stay with it, eh?

-- Ken in Atlanta




________________________________
From: "Dave.Stamm at gdc4s.com" <Dave.Stamm at gdc4s.com>
To: framers at lists.frameusers.com; techwr-l at techwr-l.com
Sent: Wed, February 13, 2013 2:52:16 PM
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/20130213/96a5a222/attachment.htm>