Re: FrameMaker has detected a problem and must quit Really?!

Best practice is to use a version control system such as Subversion. Gives you the performance of local files, all the advantages of network sharing, plus additional advantages. On Mon, Feb 18, 2013 at 1:40 PM, rebecca officer rebecca.offi...@alliedtelesis.co.nz wrote: Hi Gary That's

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

About the network switch over. We have just done that and how well applications play depends upon what protocols and configurations are set up, and how switches are managed (oh so many variables). Certainly, when we had Novell (which served well for decades) it had an annoying habit of

RE: FrameMaker has detected a problem and must quit Really?!

: FrameMaker has detected a problem and must quit Really?! Hi Ken I'm the person who asked Kapil to clarify, so I suspect I've contributed to what you're feeling is the argumentative tone. Given that, I wanted to explain *why* I reacted like that. Very likely other people are in the same

RE: FrameMaker has detected a problem and must quit Really?!

@lists.frameusers.com Subject: Re: FrameMaker has detected a problem and must quit Really?! Hi Ken I'm the person who asked Kapil to clarify, so I suspect I've contributed to what you're feeling is the argumentative tone. Given that, I wanted to explain *why* I reacted like that. Very likely other people

Re: FrameMaker has detected a problem and must quit Really?!

About the network switch over. We have just done that and how well applications play depends upon what protocols and configurations are set up, and how switches are managed (oh so many variables). Certainly, when we had Novell (which served well for decades) it had an annoying habit of

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

shedly at bellsouth.net; framers at lists.frameusers.com > Subject: Re: "FrameMaker has detected a problem and must quit" Really?! > > Hi Ken > > I'm the person who asked Kapil to clarify, so I suspect I've contributed > to what you're feeling is the argumentative tone.

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

> alan at alphabyte.co.nz<mailto:alan at alphabyte.co.nz>; poshedly at > bellsouth.net<mailto:poshedly at bellsouth.net>; framers at > lists.frameusers.com<mailto:framers at lists.frameusers.com> > Subject: Re: "FrameMaker has detected a problem and must quit"

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

Best practice is to use a version control system such as Subversion. Gives you the performance of local files, all the advantages of network sharing, plus additional advantages. On Mon, Feb 18, 2013 at 1:40 PM, rebecca officer wrote: > Hi Gary > > That's interesting. It sounds very like the

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

ary 16, 2013 2:02 PM > To: isaacs at adobe.com; kverma at adobe.com; Syed.Hosain at aeris.net; > alan at alphabyte.co.nz; poshedly at bellsouth.net; framers at > lists.frameusers.com > Subject: Re: "FrameMaker has detected a problem and must quit" Really?! > > Hi

Re: FrameMaker has detected a problem and must quit Really?!

Zaeem Hosain (syed.hos...@aeris.net) syed.hos...@aeris.net; Dov Isaacs isa...@adobe.com; Alan T Litchfield a...@alphabyte.co.nz; framers@lists.frameusers.com framers@lists.frameusers.com Sent: Fri, February 15, 2013 7:33:39 AM Subject: RE: FrameMaker has detected a problem and must quit Really

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

e...@adobe.com> To: "Syed Zaeem Hosain (Syed.Hosain at aeris.net)" ; Dov Isaacs ; Alan T Litchfield ; "framers at lists.frameusers.com" Sent: Fri, February 15, 2013 7:33:39 AM Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Hello Every

Re: FrameMaker has detected a problem and must quit Really?!

cs; Alan T Litchfield; framers@lists.frameusers.comSubject: RE: "FrameMaker has detected a problem and must quit" Really?! Hi, Dov. What you say below is indeed what I would expect, and what is also my experience, with the Adobe applications I use (FrameMaker, PhotoShop and Acrobat Pro)– pretty mu

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

Ken, I think you are wrong. The tone has not been argumentative, but several people (myself included) have merely been saying the same/ similar things. Now, if your co-worker is still experiencing problems with opening files across the network then you need to look at the local

Re: FrameMaker has detected a problem and must quit Really?!

boun...@lists.frameusers.com] On Behalf Of dave.st...@gdc4s.comSent: Wednesday, February 13, 2013 11:50 AMTo: framers@lists.frameusers.com; techw...@techwr-l.comSubject: RE: "FrameMaker has detected a problem and must quit" Really?! 2013-02-13-03T19:50Z ¡_YIKES_! If Ken was

Re: FrameMaker has detected a problem and must quit Really?!

To: Ken Poshedly poshe...@bellsouth.net; framers@lists.frameusers.com framers@lists.frameusers.com Cc: techw...@techwr-l.com techw...@techwr-l.com Sent: Thu, February 14, 2013 4:39:30 PM Subject: RE: FrameMaker has detected a problem and must quit Really?! Ken Poshedly wrote: Fourth, my coworker has

Re: FrameMaker has detected a problem and must quit Really?!

:* Re: FrameMaker has detected a problem and must quit Really?!* *** ** ** 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

Re: FrameMaker has detected a problem and must quit Really?!

On 2013-02-14 14:44, Ken Poshedly wrote: I posted my first frameusers list inquiry Wednesday morning, but never saw it or any replies for quite sometime. After waiting an hour or so and not seeing either my message or any replies on the frameusers list, I posted to the techwr-l e-mail list (and

RE: FrameMaker has detected a problem and must quit Really?!

Zaeem Hosain (syed.hos...@aeris.net) Sent: Friday, February 15, 2013 5:43 AM To: Dov Isaacs; Alan T Litchfield; framers@lists.frameusers.com Subject: RE: FrameMaker has detected a problem and must quit Really?! Hi, Dov. What you say below is indeed what I would expect, and what is also my

RE: FrameMaker has detected a problem and must quit Really?!

...@adobe.com] Sent: 2013-02-14-Thursday 16:05 To: framers@lists.frameusers.com Cc: Stamm, David-P45904; techw...@techwr-l.com 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

Re: FrameMaker has detected a problem and must quit Really?!

Ken, I think you are wrong. The tone has not been argumentative, but several people (myself included) have merely been saying the same/ similar things. Now, if your co-worker is still experiencing problems with opening files across the network then you need to look at the local

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

On 2013-02-14 14:44, Ken Poshedly wrote: > I posted my first frameusers list inquiry Wednesday morning, but never > saw it or any replies for quite sometime. > > After waiting an hour or so and not seeing either my message or any > replies on the frameusers list, I posted to the techwr-l e-mail

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

Behalf Of Syed Zaeem Hosain (syed.hos...@aeris.net) Sent: Friday, February 15, 2013 5:43 AM To: Dov Isaacs; Alan T Litchfield; framers at lists.frameusers.com Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Hi, Dov. What you say below is indeed what I would expect,

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

mailto:isa...@adobe.com] Sent: 2013-02-14-Thursday 16:05 To: framers at lists.frameusers.com Cc: Stamm, David-P45904; techwr-l at techwr-l.com Subject: RE: "FrameMaker has detected a problem and must quit" Really?! All, Sorry I couldn't respond to this thread earlier. Driving much o

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

From: Kapil Verma <kve...@adobe.com> To: "Syed Zaeem Hosain (Syed.Hosain at aeris.net)" ; Dov Isaacs ; Alan T Litchfield ; "framers at lists.frameusers.com" Sent: Fri, February 15, 2013 7:33:39 AM Subject: RE: "FrameMaker has detected a problem

RE: FrameMaker has detected a problem and must quit Really?!

From: framers-boun...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Alan T Litchfield There is some weird behaviour on the list this morning. I seem to be getting the messages in discontinuous threads and out of order. Probably because the conversation

Re: FrameMaker has detected a problem and must quit Really?!

On Wed, 13 Feb 2013 13:41:28 -0800, Combs, Richard richard.co...@polycom.com wrote: All the geezers who cut their teeth on VT-100s may now begin reminiscing. My first one was an ASR-33 TTY. Really. Rolls of paper and UPPER-CASE ONLY. 110 baud, which gave you 10 characters per second.

RE: FrameMaker has detected a problem and must quit Really?!

; FrameMaker Users List Subject: RE: FrameMaker has detected a problem and must quit Really?! Jeff Coatsworth wrote: I'm getting that one right after this one occurs - 11014, 7732533, 7724103, 5985284 I've figured out that it's something to do with WinXP because working on another terminal

Re: FrameMaker has detected a problem and must quit Really?!

...@triviewgroup.com To: framers@lists.frameusers.com framers@lists.frameusers.com Sent: Thu, February 14, 2013 7:27:22 AM Subject: RE: FrameMaker has detected a problem and must quit Really?! From: framers-boun...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Alan T

RE: FrameMaker has detected a problem and must quit Really?!

-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of dave.st...@gdc4s.com Sent: Wednesday, February 13, 2013 11:50 AM To: framers@lists.frameusers.com; techw...@techwr-l.com Subject: RE: FrameMaker has detected a problem and must quit Really?! 2013-02-13-03T19

RE: FrameMaker has detected a problem and must quit Really?!

...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of John Sgammato Sent: Wednesday, February 13, 2013 12:12 PM To: Alan T Litchfield Cc: framers@lists.frameusers.com Subject: Re: FrameMaker has detected a problem and must quit Really?! I have been told numerous

RE: FrameMaker has detected a problem and must quit Really?!

: FrameMaker has detected a problem and must quit Really?! I think that there may be some confusion about local vs. network folders/drives. Perhaps I read too much into Ken's responses from the Adobe tech! In my case, all application executables are on my drive C and the data files are on drive E

RE: FrameMaker has detected a problem and must quit Really?!

Ken Poshedly wrote: 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. Go figure? You really find it surprising that it

RE: FrameMaker has detected a problem and must quit Really?!

Ken Poshedly wrote: Of COURSE things work faster when all are on the same drive -- I just happen to mention it here. I guess I wasn't sufficiently clear. That's not what I said -- or meant. What's faster is reading from or writing to a drive that's _inside your PC_ and _directly connected_

RE: FrameMaker has detected a problem and must quit Really?!

: Thursday, February 14, 2013 1:24 PM To: Syed Zaeem Hosain (syed.hos...@aeris.net); Alan T Litchfield; framers@lists.frameusers.com Subject: RE: FrameMaker has detected a problem and must quit Really?! Importance: High With regards to network folders and drives, Adobe software in general

RE: FrameMaker has detected a problem and must quit Really?!

...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Wednesday, February 13, 2013 12:17 PM To: dave.st...@gdc4s.com; framers@lists.frameusers.com; techw...@techwr-l.com Subject: Re: FrameMaker has detected a problem and must quit Really?! To all

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

pies > 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; rober

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

Now about those questions. On 14/02/13 3:48 AM, Ken Poshedly wrote: > So the questions: > > * What do those internal error numbers specifically mean? I have no idea and don't really want to know. > * Is/are the error/errors caused by a hardware problem or a software > problem? Looking

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

There is some weird behaviour on the list this morning. I seem to be getting the messages in discontinuous threads and out of order. It's like listening to a conversation in a bar. Alan On 14/02/13 9:09 AM, Robert Lauriston wrote: > Note that Ken and his coworker were able to reproduce the

"FrameMaker has detected a problem and must quit" Really?! - support for networked drives

using FM 8.0 the "wrong" way and with no crashes. -- Ken in Atlanta From: Ken Poshedly <poshe...@bellsouth.net> 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?!

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

An HTML attachment was scrubbed... URL:

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

> From: framers-bounces at lists.frameusers.com [mailto:framers- > bounces at lists.frameusers.com] On Behalf Of Alan T Litchfield > > There is some weird behaviour on the list this morning. I seem to be getting > the > messages in discontinuous threads and out of order. Probably because the

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

13, 2013 4:41 PM To: Jeff Coatsworth; FrameMaker Users List Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Jeff Coatsworth wrote: > I'm getting that one right after this one occurs - 11014, 7732533, 7724103, > 5985284 > > I've figured out that

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

On Wed, 13 Feb 2013 13:41:28 -0800, "Combs, Richard" > wrote: >All the geezers who cut their teeth on >VT-100s may now begin reminiscing. My first one was an ASR-33 TTY. Really. Rolls of paper and UPPER-CASE ONLY. 110 baud, which gave you 10 characters per second. The Hazeltine "glass

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

Coatsworth; FrameMaker Users List Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Jeff Coatsworth wrote: > I'm getting that one right after this one occurs - 11014, 7732533, 7724103, > 5985284 > > I've figured out that it's something to do with WinXP becaus

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

dej...@triviewgroup.com> To: "framers at lists.frameusers.com" Sent: Thu, February 14, 2013 7:27:22 AM Subject: RE: "FrameMaker has detected a problem and must quit" Really?! > From: framers-bounces at lists.frameusers.com [mailto:framers- > bounces at lists.frameusers.com

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

Yes, well, some of us remember using a punch card and a knitting needle. You stabbed the card bundle somewhere along the edge with the knitting needle, shook the deck, and the ones that fell out were the ones you wanted. More sophisticated systems used two knitting needles, which was the upper

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

rt at lauriston.com<mailto:robert at lauriston.com>; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>; techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com> Subject: RE: "FrameMaker has detected a problem and must quit" Really?! On Wed, Feb 13,

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

-OFFICE.corp.adobe.com From: framers-bounces at lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of John Sgammato Sent: Wednesday, February 13, 2013 12:12 PM To: Alan T Litchfield Cc: framers at lists.frameusers.com Subject: Re: "FrameMaker has detected a problem and m

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

M To: Alan T Litchfield; framers at lists.frameusers.com Subject: RE: "FrameMaker has detected a problem and must quit" Really?! I think that there may be some confusion about local vs. network folders/drives. Perhaps I read too much into Ken's responses from the Adobe tech! In my case, all

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

Ken Poshedly wrote: > 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. Go figure? You really find it surprising

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

Ken Poshedly wrote: > Of COURSE things work faster when all are on the same drive -- I just happen > to mention it here. I guess I wasn't sufficiently clear. That's not what I said -- or meant. What's faster is reading from or writing to a drive that's _inside your PC_ and _directly connected_

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

: Thursday, February 14, 2013 1:24 PM To: Syed Zaeem Hosain (Syed.Hosain at aeris.net); Alan T Litchfield; framers at lists.frameusers.com Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Importance: High With regards to network folders and drives, Adobe software

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

t 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 FrameMa

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

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 th

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

ces at lists.frameusers.com] *On Behalf Of *Ken Poshedly > *Sent:* Wednesday, February 13, 2013 12:17 PM > *To:* Dave.Stamm at gdc4s.com; framers at lists.frameusers.com; > techwr-l at techwr-l.com > *Subject:* Re: "FrameMaker has detected a problem and must quit" Really?!* >

RE: FrameMaker has detected a problem and must quit Really?!

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@lists.frameusers.com; techw...@techwr-l.com Yes, an .lck file is created

RE: FrameMaker has detected a problem and must quit Really?!

: 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 permission to save the file

RE: FrameMaker has detected a problem and must quit Really?!

On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly poshe...@bellsouth.netmailto: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

RE: FrameMaker has detected a problem and must quit Really?!

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 poshe...@bellsouth.net wrote: I just learned from Adobe tech support

Re: FrameMaker has detected a problem and must quit Really?!

*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 poshe...@bellsouth.net mailto:poshe...@bellsouth.net wrote: I just

FrameMaker has detected a problem and must quit Really?!

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,

Re: FrameMaker has detected a problem and must quit Really?!

From: Ken Poshedly poshe...@bellsouth.net To: techw...@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 from there so far. My coworker

Re: 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 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

Re: FrameMaker has detected a problem and must quit Really?!

-l.com Sent: Wed, February 13, 2013 12:11:02 PM Subject: Re: 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 poshe...@bellsouth.net wrote: I just learned

Re: FrameMaker has detected a problem and must quit Really?!

: Re: 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 poshe...@bellsouth.net wrote: I just learned from Adobe tech support (via phone call

Re: FrameMaker has detected a problem and must quit Really?!

To: poshe...@bellsouth.net; rob...@lauriston.com; framers@lists.frameusers.com framers@lists.frameusers.com; techw...@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

Re: FrameMaker has detected a problem and must quit Really?!

Ridder docu...@hotmail.com To: poshe...@bellsouth.net; rob...@lauriston.com; framers@lists.frameusers.com framers@lists.frameusers.com; techw...@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

RE: FrameMaker has detected a problem and must quit Really?!

Subject: RE: FrameMaker has detected a problem and must quit Really?! On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly poshe...@bellsouth.netmailto: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

Re: FrameMaker has detected a problem and must quit Really?!

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 poshe...@bellsouth.net

Re: FrameMaker has detected a problem and must quit Really?!

...@hotmail.com; poshe...@bellsouth.net poshe...@bellsouth.net; rob...@lauriston.com rob...@lauriston.com; framers@lists.frameusers.com framers@lists.frameusers.com; techw...@techwr-l.com techw...@techwr-l.com Sent: Wed, February 13, 2013 2:24:07 PM Subject: RE: FrameMaker has detected a problem and must

Re: FrameMaker has detected a problem and must quit Really?!

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

Re: FrameMaker has detected a problem and must quit Really?!

detected a problem and must quit Really?! On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly poshe...@bellsouth.net 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

RE: FrameMaker has detected a problem and must quit Really?!

; techw...@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 instead a separate

RE: FrameMaker has detected a problem and must quit Really?!

: FrameMaker has detected a problem and must quit Really?! Keep calm and Make Frames I would have to say that the person Ken spoke to must be a tech-idiot, but that would not be the first I have spoken to at Adobe (re previous discussions on Adobe's appalling registration system and advice to me

Re: FrameMaker has detected a problem and must quit Really?!

Subject: FrameMaker has detected a problem and must quit Really?! To all, Please excuse this x-posting (Framemaker list), but no replies at all from there so far. My coworker is running FrameMaker 11.0 and is frustrated because twice this morning, FrameMaker crashed on his terminal

RE: FrameMaker has detected a problem and must quit Really?!

...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Wednesday, February 13, 2013 9:48 AM To: FrameMaker Users List Subject: FrameMaker has detected a problem and must quit Really?! To all, My coworker is running FrameMaker 11.0 and is frustrated because twice

Re: FrameMaker has detected a problem and must quit Really?!

Now about those questions. On 14/02/13 3:48 AM, Ken Poshedly wrote: So the questions: * What do those internal error numbers specifically mean? I have no idea and don't really want to know. * Is/are the error/errors caused by a hardware problem or a software problem? Looking at

Re: FrameMaker has detected a problem and must quit Really?!

There is some weird behaviour on the list this morning. I seem to be getting the messages in discontinuous threads and out of order. It's like listening to a conversation in a bar. Alan On 14/02/13 9:09 AM, Robert Lauriston wrote: Note that Ken and his coworker were able to reproduce the

RE: FrameMaker has detected a problem and must quit Really?!

: Wednesday, February 13, 2013 11:28 AM To: Fred Ridder; rob...@lauriston.com; framers@lists.frameusers.com; techw...@techwr-l.com Subject: Re: FrameMaker has detected a problem and must quit Really?! My coworker did the following (with my help as I followed Fred's previous e-mail): 1. Unchecked

Re: FrameMaker has detected a problem and must quit Really?!

From: dave.st...@gdc4s.com dave.st...@gdc4s.com To: framers@lists.frameusers.com; techw...@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

Re: FrameMaker has detected a problem and must quit Really?! - support for networked drives

and with no crashes. -- Ken in Atlanta From: Ken Poshedly poshe...@bellsouth.net To: techw...@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

Re: FrameMaker has detected a problem and must quit Really?!

10 secs after the first. -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Robert Lauriston Sent: Wednesday, February 13, 2013 4:15 PM To: framers@lists.frameusers.com Subject: Re: FrameMaker has detected a problem

Re: FrameMaker has detected a problem and must quit Really?! - support for networked drives

Adobe support said working on local copies was the workaround for the problem. That's not the same as saying that FrameMaker can't work with files on a network drive, just a tacit admission that the implementation is buggy. There's nothing FM11-specific about that. You can find lots of examples

RE: FrameMaker has detected a problem and must quit Really?!

...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Wednesday, February 13, 2013 9:48 AM To: FrameMaker Users List Subject: FrameMaker has detected a problem and must quit Really?! To all, My coworker is running FrameMaker 11.0 and is frustrated because

Re: FrameMaker has detected a problem and must quit Really?!

Log files and errors are often only for the engineers who created the product. Unfortunately, technical writers aren't involved in that process. If technical writers would be involved, they probably would add "The following error codes are for Adobe technicians

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

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; framers at lists.frameusers

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

ubject: Re: "FrameMaker has detected a problem and must quit" Really?! To: docudoc at hotmail.com; robert at lauriston.com; framers at lists.frameusers.com; techwr-l at techwr-l.com I was only aware that an .lck file prevents two people from working on the same file simultaneously,

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

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

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

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 wrote: > I just learned from Adobe tech suppo

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

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,

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

. -- Ken in Atlanta From: Ken Poshedly <poshe...@bellsouth.net> 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

"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 permissions > in > FrameMaker 11.0 have been modified so that the data files should

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

12:11:02 PM Subject: Re: "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 supp

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

sed 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?!

com> 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 12:28:30 PM Subject: RE: "FrameMaker has detected a problem and must quit" Really?! Note that creation of a .lck file is an opt

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

Ridder <docu...@hotmail.com> 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,

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

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 mailto:poshedly at bellsouth.net>> wrote: > I just learned from Adobe tech support (via phone call) that the permissions > in > FrameMaker 1

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

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

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

To: Fred Ridder ; "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:24:07 PM Subject: RE: "FrameMaker has detected a problem and must quit" Really?

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

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

  1   2   >