y version from 5.5.6 through 9, which is what I'm
currently using).
-Fred Ridder
> Date: Wed, 13 Feb 2013 09:16:06 -0800
> From: poshedly at bellsouth.net
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
> To: robert at lauriston.com; framer
To all,
My coworker is running FrameMaker 11.0 and is frustrated because twice this
morning, FrameMaker crashed on his terminal (luckily creating recovery files,
though).
The warning pop-up window that displayed announcing this glorious impending
shutdown stated "Internal Error 11014, 8122692,
lists.frameusers.com; techwr-l at techwr-l.com
Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
Syed,
In our case:
* The C-drive is the hard drive on our own desktop computer and is where FM is
installed.
* The network drive is not a partition of the desktop hard drive, but
ght just stay with it, eh?
-- Ken in Atlanta
From: "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-0
Note that Ken and his coworker were able to reproduce the problem.
Sometimes FrameMaker has problems using source files are on network
file servers, sometimes it doesn't. If you've experienced no problems,
count yourself lucky.
On Wed, Feb 13, 2013 at 12:03 PM, Alan T Litchfield
wrote:
> If it w
esday 14:24
*To:* Fred Ridder; poshe...@bellsouth.net; rob...@lauriston.com;
framers@lists.frameusers.com; techw...@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 mailto:poshe...@bellsouth.net>> wr
esday 14:24
To: Fred Ridder; poshe...@bellsouth.net; rob...@lauriston.com;
framers@lists.frameusers.com; techw...@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 wrote:
> I just learned from Adobe t
dly at bellsouth.net"
; "robert at lauriston.com" ;
"framers at lists.frameusers.com" ;
"techwr-l at techwr-l.com"
Sent: Wed, February 13, 2013 2:24:07 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
On Wed, Feb 13, 2013
I haven't worked anywhere without source control in years, but before
that, I encountered so many problems editing FrameMaker files on
network shared drives that I eventually decided it was easier to work
on a local copy.
On Wed, Feb 13, 2013 at 11:27 AM, Ken Poshedly
wrote:
> 1. Copied the enti
From: Fred Ridder
To: poshedly at bellsouth.net; robert at lauriston.com; "framers at
lists.frameusers.com"
; techwr-l at techwr-l.com
Sent: Wed, February 13, 2013 2:01:54 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
Actually, there is *less
On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly
mailto:poshe...@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 installe
On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly mailto: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 instal
net
Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
To: docu...@hotmail.com; rob...@lauriston.com; framers@lists.frameusers.com;
techw...@techwr-l.com
I was only aware that an .lck file prevents two people from working on the same
file simultaneously, each with pe
bellsouth.net; robert at lauriston.com; "framers at
lists.frameusers.com"
; techwr-l at techwr-l.com
Sent: Wed, February 13, 2013 12:28:30 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
Note that creation of a .lck file is an option that the user can turn
y version from 5.5.6 through 9, which is what I'm
currently using).
-Fred Ridder
> Date: Wed, 13 Feb 2013 09:16:06 -0800
> From: poshe...@bellsouth.net
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
> To: rob...@lauriston.com; framers@li
to
> do before. Capisce?
>
> -- Ken in Atlanta
>
>
>
> From: Robert Lauriston
> To: Ken Poshedly ; framers at lists.frameusers.com;
> TECHWR-L
> Sent: Wed, February 13, 2013 12:11:02 PM
> Subject: Re: "FrameMaker has
: "FrameMaker has detected a problem and must quit" Really?!
That's a pretty radical change. Does FM11 not create .lck files when
you open an .fm file?
On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly wrote:
> I just learned from Adobe tech support (via phone call) that the permission
That's a pretty radical change. Does FM11 not create .lck files when
you open an .fm file?
On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly 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 a
with no crashes.
-- Ken in Atlanta
From: Ken Poshedly
To: techwr-l at techwr-l.com
Sent: Wed, February 13, 2013 10:47:05 AM
Subject: "FrameMaker has detected a problem and must quit" Really?!
To all,
Please excuse this x-posting (Framemaker list), but no replies at all
To all,
My coworker is running FrameMaker 11.0 and is frustrated because twice this
morning, FrameMaker crashed on his terminal (luckily creating recovery files,
though).
The warning pop-up window that displayed announcing this glorious impending
shutdown stated "Internal Error 11014, 8122692,
101 - 120 of 120 matches
Mail list logo
