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

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

2013-02-20 Thread Robert Lauriston

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 interesting. It sounds very like the problems we've seen: 3000+ page
 docs, lots of conditional text, sometimes can't create a PDF over the
 network.

 We're using a Novell server. Our IS team have checked for choke points,
 overloading etc, and can't find any problems. They reckon it's just Novell.
 We're going to be changing to a Microsoft server anyway, and they reckon
 that'll be happier with Frame. I hope they're right!

 Like you, we've resolved the issue by copying all the components to a
 local drive before creating the PDF. We're ok with having to do that part of
 the workflow locally, as long as we can keep editing the source files over
 the network.
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

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

2013-02-20 Thread Alan T Litchfield

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 resetting SMB connections periodically (atalk was 
dropped a few years prior). The new MS network doesn't seem to do that, 
or if it does, it seems to be masked.

I would suggest that if you have any issues after the switch, that you 
communicate your concerns immediately with the tech guys because there 
may be a fix they can offer.

One thing that can be ruled out as the problem is FM.

Alan

On 19/02/13 10:40 AM, rebecca officer wrote:
> Hi Gary
> That's interesting. It sounds very like the problems we've seen: 3000+
> page docs, lots of conditional text, sometimes can't create a PDF over
> the network.
> We're using a Novell server. Our IS team have checked for choke points,
> overloading etc, and can't find any problems. They reckon it's just
> Novell. We're going to be changing to a Microsoft server anyway, and
> they reckon that'll be happier with Frame. I hope they're right!
> Like you, we've "resolved" the issue by copying all the components to a
> local drive before creating the PDF. We're ok with having to do that
> part of the workflow locally, as long as we can keep editing the source
> files over the network.
> Cheers
> Rebecca
>
>-- 
AlphaByte
PO Box 1941, Auckland
http://www.alphabyte.co.nz

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

2013-02-19 Thread rebecca officer

Hi Gary
 
That's interesting. It sounds very like the problems we've seen: 3000+
page docs, lots of conditional text, sometimes can't create a PDF over
the network.
 
We're using a Novell server. Our IS team have checked for choke points,
overloading etc, and can't find any problems. They reckon it's just
Novell. We're going to be changing to a Microsoft server anyway, and
they reckon that'll be happier with Frame. I hope they're right!
 
Like you, we've resolved the issue by copying all the components to a
local drive before creating the PDF. We're ok with having to do that
part of the workflow locally, as long as we can keep editing the source
files over the network. 
 
Cheers
Rebecca

 Zimmerman, Gary gary.zimmer...@teradata.com 19/02/13 07:20 
Hi Rebecca,

Just for the record, we have had instances where very large (2000 page)
documents with extensive conditionalization have been unable to Save as
PDF over the network.  I don't believe FM crashed, it just hung
indefinitely and never finished PDF production.  This was probably due
to network timeout issues, as relocating all the component book files
(chapters, appendices, FM-generated TOC/index) to a local computer and
saving as PDF there alleviated the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an
issue for us with FM10, however we also removed a LOT of the
now-unnecessary conditions and conditional text from those books.

Cheers.

-- garyZ


 -Original Message-
 From: framers-boun...@lists.frameusers.com [mailto:framers-
 boun...@lists.frameusers.com] On Behalf Of rebecca officer
 Sent: Saturday, February 16, 2013 2:02 PM
 To: isa...@adobe.com; kve...@adobe.com; syed.hos...@aeris.net;
 a...@alphabyte.co.nz; poshe...@bellsouth.net;
framers@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 are in the same position as me.
 
 I wasn't feeling negative towards you, or disagreeing that following
 tech support's advice had fixed your problem. I lead a team of
writers
 who all work on a single multi-chapter docs set. We can't just
change
 our workflow so everyone's working on their local drives. And we're
 still on FM10 but planning to upgrade soon. So I looked at tech
 support's advice that FM11 didn't support networked drive locations,
and
 thought If that's true, we can't upgrade to FM11. If it's a
long-term
 decision from Adobe, we'll have to stop using FM. That seems awfully
 unlikely.
 
 So it mattered to me to get things clarified by someone higher in
Adobe
 than a tech support engineer. I'm relieved to find that FM11 does
still
 support networked drive locations, as I expected.
 
 We don't always find that FM10 talks nicely with our networked
servers,
 so sometimes we end up doing part of our workflow on our local
drives
 too. I'm not surprised that moving a doc to your local drive would
make
 a crashing doc behave. I just wanted people like Dov and Kapil to
 confirm that it's still the exception rather than the rule!
 
 Cheers and have a good day
 Rebecca
 
 
 
  Ken Poshedly poshe...@bellsouth.net 02/17/13 1:55 AM 
 To all,
 
 Maybe I'm wrong but the argumentative tone of all of this with
regards
 to my
 question is the pits.
 
 As far as I'm concerned:
 1. Contact Shekhar at tcs...@adobe.com and discuss it with him.
 2. We did what he told us to do.
 3. No more problems (so far).
 
 OK?
 
 -- Ken
 
 
 
 
 
 From: Kapil Verma kve...@adobe.com
 To: Syed 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?!
 
 
 Hello Everyone,
 
 Hope you are well. Well, there has been a flurry of emails on this
topic
 and I
 (as the product manager for FrameMaker) wanted to mention a couple
of
 things
 here to set the record straight J
 
 · Network file paths: FrameMaker 11 has been tested to work
with
 network
 file paths. There is absolutely no change in behavior between FM11
and
 the older
 versions. So, you should not have any problems when your files are
 stored on the
 network location. However, in case you are experiencing any crashes
when
 working
 with network files, we will be happy to take a look at your crash
logs
 and help
 your troubleshoot your specific issue.
 
 · FrameMaker Lock file:There is lot of discussion and some
 confusion
 around the purpose of the lock file. Lock file is created by FM to
tell
 the user
 that the file is open in another instance of FM. So, if we take the
 scenario of
 multiple users working on the same file set (which is stored

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

2013-02-19 Thread Jeff Coatsworth

When creating a PDF, I’d be looking to eliminate the network part of things by 
generating to a local location (leaving all the source files/resources where 
they are on the network). I seem to remember reading some “best practice” that 
recommended generating PDFs to a local location first, then copying them to 
their network home after.

From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of rebecca officer
Sent: February-18-13 4:40 PM
To: framers@lists.frameusers.com; Gary Zimmerman
Subject: RE: FrameMaker has detected a problem and must quit Really?!

Hi Gary

That's interesting. It sounds very like the problems we've seen: 3000+ page 
docs, lots of conditional text, sometimes can't create a PDF over the network.

We're using a Novell server. Our IS team have checked for choke points, 
overloading etc, and can't find any problems. They reckon it's just Novell. 
We're going to be changing to a Microsoft server anyway, and they reckon 
that'll be happier with Frame. I hope they're right!

Like you, we've resolved the issue by copying all the components to a local 
drive before creating the PDF. We're ok with having to do that part of the 
workflow locally, as long as we can keep editing the source files over the 
network.

Cheers
Rebecca

 Zimmerman, Gary 
 gary.zimmer...@teradata.commailto:gary.zimmer...@teradata.com 19/02/13 
 07:20 
Hi Rebecca,

Just for the record, we have had instances where very large (2000 page) 
documents with extensive conditionalization have been unable to Save as PDF 
over the network.  I don't believe FM crashed, it just hung indefinitely and 
never finished PDF production.  This was probably due to network timeout 
issues, as relocating all the component book files (chapters, appendices, 
FM-generated TOC/index) to a local computer and saving as PDF there alleviated 
the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an issue for 
us with FM10, however we also removed a LOT of the now-unnecessary conditions 
and conditional text from those books.

Cheers.

-- garyZ

 -Original Message-
 From: 
 framers-boun...@lists.frameusers.commailto:framers-boun...@lists.frameusers.com
  [mailto:framers-
 boun...@lists.frameusers.commailto:boun...@lists.frameusers.com] On Behalf 
 Of rebecca officer
 Sent: Saturday, February 16, 2013 2:02 PM
 To: isa...@adobe.commailto:isa...@adobe.com; 
 kve...@adobe.commailto:kve...@adobe.com; 
 syed.hos...@aeris.netmailto:syed.hos...@aeris.net;
 a...@alphabyte.co.nzmailto:a...@alphabyte.co.nz; 
 poshe...@bellsouth.netmailto:poshe...@bellsouth.net; 
 framers@lists.frameusers.commailto:framers@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 are in the same position as me.

 I wasn't feeling negative towards you, or disagreeing that following
 tech support's advice had fixed your problem. I lead a team of writers
 who all work on a single multi-chapter docs set. We can't just change
 our workflow so everyone's working on their local drives. And we're
 still on FM10 but planning to upgrade soon. So I looked at tech
 support's advice that FM11 didn't support networked drive locations, and
 thought If that's true, we can't upgrade to FM11. If it's a long-term
 decision from Adobe, we'll have to stop using FM. That seems awfully
 unlikely.

 So it mattered to me to get things clarified by someone higher in Adobe
 than a tech support engineer. I'm relieved to find that FM11 does still
 support networked drive locations, as I expected.

 We don't always find that FM10 talks nicely with our networked servers,
 so sometimes we end up doing part of our workflow on our local drives
 too. I'm not surprised that moving a doc to your local drive would make
 a crashing doc behave. I just wanted people like Dov and Kapil to
 confirm that it's still the exception rather than the rule!

 Cheers and have a good day
 Rebecca

  Ken Poshedly poshe...@bellsouth.netmailto:poshe...@bellsouth.net 
  02/17/13 1:55 AM 
 To all,

 Maybe I'm wrong but the argumentative tone of all of this with regards
 to my
 question is the pits.

 As far as I'm concerned:
 1. Contact Shekhar at tcs...@adobe.commailto:tcs...@adobe.com and discuss 
 it with him.
 2. We did what he told us to do.
 3. No more problems (so far).

 OK?

 -- Ken

 From: Kapil Verma kve...@adobe.commailto:kve...@adobe.com
 To: Syed Zaeem Hosain (syed.hos...@aeris.netmailto:syed.hos...@aeris.net) 
 syed.hos...@aeris.netmailto:syed.hos...@aeris.net;
 Dov
 Isaacs isa...@adobe.commailto:isa...@adobe.com; Alan T Litchfield 
 a...@alphabyte.co.nzmailto:a...@alphabyte.co.nz;
 framers@lists.frameusers.commailto:framers@lists.frameusers.com

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

2013-02-19 Thread Alan T Litchfield

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 resetting SMB connections periodically (atalk was 
dropped a few years prior). The new MS network doesn't seem to do that, 
or if it does, it seems to be masked.


I would suggest that if you have any issues after the switch, that you 
communicate your concerns immediately with the tech guys because there 
may be a fix they can offer.


One thing that can be ruled out as the problem is FM.

Alan

On 19/02/13 10:40 AM, rebecca officer wrote:

Hi Gary
That's interesting. It sounds very like the problems we've seen: 3000+
page docs, lots of conditional text, sometimes can't create a PDF over
the network.
We're using a Novell server. Our IS team have checked for choke points,
overloading etc, and can't find any problems. They reckon it's just
Novell. We're going to be changing to a Microsoft server anyway, and
they reckon that'll be happier with Frame. I hope they're right!
Like you, we've resolved the issue by copying all the components to a
local drive before creating the PDF. We're ok with having to do that
part of the workflow locally, as long as we can keep editing the source
files over the network.
Cheers
Rebecca

--

AlphaByte
PO Box 1941, Auckland
http://www.alphabyte.co.nz
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

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

2013-02-19 Thread rebecca officer

Hi Gary

That's interesting. It sounds very like the problems we've seen: 3000+
page docs, lots of conditional text, sometimes can't create a PDF over
the network.

We're using a Novell server. Our IS team have checked for choke points,
overloading etc, and can't find any problems. They reckon it's just
Novell. We're going to be changing to a Microsoft server anyway, and
they reckon that'll be happier with Frame. I hope they're right!

Like you, we've "resolved" the issue by copying all the components to a
local drive before creating the PDF. We're ok with having to do that
part of the workflow locally, as long as we can keep editing the source
files over the network. 

Cheers
Rebecca

>>> "Zimmerman, Gary"  19/02/13 07:20 >>>
Hi Rebecca,

Just for the record, we have had instances where very large (2000 page)
documents with extensive conditionalization have been unable to Save as
PDF over the network.  I don't believe FM crashed, it just hung
indefinitely and never finished PDF production.  This was probably due
to network timeout issues, as relocating all the component book files
(chapters, appendices, FM-generated TOC/index) to a local computer and
saving as PDF there alleviated the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an
issue for us with FM10, however we also removed a LOT of the
now-unnecessary conditions and conditional text from those books.

Cheers.

-- garyZ


> -Original Message-
> From: framers-bounces at lists.frameusers.com [mailto:framers-
> bounces at lists.frameusers.com] On Behalf Of rebecca officer
> Sent: Saturday, February 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 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 position as me.
> 
> I wasn't feeling negative towards you, or disagreeing that following
> tech support's advice had fixed your problem. I lead a team of
writers
> who all work on a single multi-chapter docs set. We can't just
change
> our workflow so everyone's working on their local drives. And we're
> still on FM10 but planning to upgrade soon. So I looked at tech
> support's advice that FM11 didn't support networked drive locations,
and
> thought "If that's true, we can't upgrade to FM11. If it's a
long-term
> decision from Adobe, we'll have to stop using FM. That seems awfully
> unlikely."
> 
> So it mattered to me to get things clarified by someone higher in
Adobe
> than a tech support engineer. I'm relieved to find that FM11 does
still
> support networked drive locations, as I expected.
> 
> We don't always find that FM10 talks nicely with our networked
servers,
> so sometimes we end up doing part of our workflow on our local
drives
> too. I'm not surprised that moving a doc to your local drive would
make
> a crashing doc behave. I just wanted people like Dov and Kapil to
> confirm that it's still the exception rather than the rule!
> 
> Cheers and have a good day
> Rebecca
> 
> 
> 
> >>> Ken Poshedly  02/17/13 1:55 AM >>>
> To all,
> 
> Maybe I'm wrong but the argumentative tone of all of this with
regards
> to my
> question is the pits.
> 
> As far as I'm concerned:
> 1. Contact Shekhar at tcssup at adobe.com and discuss it with him.
> 2. We did what he told us to do.
> 3. No more problems (so far).
> 
> OK?
> 
> -- Ken
> 
> 
> 
> 
> ____________
> From: Kapil Verma 
> 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 Everyone,
> 
> Hope you are well. Well, there has been a flurry of emails on this
topic
> and I
> (as the product manager for FrameMaker) wanted to mention a couple
of
> things
> here to set the record straight J
> 
> ? Network file paths: FrameMaker 11 has been tested to work
with
> network
> file paths. There is absolutely no change in behavior between FM11
and
> the older
> versions. So, you should not have any problems when your files are
> stored on the
> network location. However, in case you are experiencing any crashes
when
> working
> with network files, we will be happy to take a look at your crash
logs

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

2013-02-19 Thread Jeff Coatsworth

When creating a PDF, I?d be looking to eliminate the network part of things by 
generating to a local location (leaving all the source files/resources where 
they are on the network). I seem to remember reading some ?best practice? that 
recommended generating PDFs to a local location first, then copying them to 
their network home after.

From: framers-bounces at lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of rebecca officer
Sent: February-18-13 4:40 PM
To: framers at lists.frameusers.com; Gary Zimmerman
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!

Hi Gary

That's interesting. It sounds very like the problems we've seen: 3000+ page 
docs, lots of conditional text, sometimes can't create a PDF over the network.

We're using a Novell server. Our IS team have checked for choke points, 
overloading etc, and can't find any problems. They reckon it's just Novell. 
We're going to be changing to a Microsoft server anyway, and they reckon 
that'll be happier with Frame. I hope they're right!

Like you, we've "resolved" the issue by copying all the components to a local 
drive before creating the PDF. We're ok with having to do that part of the 
workflow locally, as long as we can keep editing the source files over the 
network.

Cheers
Rebecca

>>> "Zimmerman, Gary" mailto:Gary.Zimmerman at 
>>> Teradata.com>> 19/02/13 07:20 >>>
Hi Rebecca,

Just for the record, we have had instances where very large (2000 page) 
documents with extensive conditionalization have been unable to Save as PDF 
over the network.  I don't believe FM crashed, it just hung indefinitely and 
never finished PDF production.  This was probably due to network timeout 
issues, as relocating all the component book files (chapters, appendices, 
FM-generated TOC/index) to a local computer and saving as PDF there alleviated 
the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an issue for 
us with FM10, however we also removed a LOT of the now-unnecessary conditions 
and conditional text from those books.

Cheers.

-- garyZ

> -Original Message-
> From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at 
> lists.frameusers.com> [mailto:framers-
> bounces at lists.frameusers.com<mailto:bounces at lists.frameusers.com>] On 
> Behalf Of rebecca officer
> Sent: Saturday, February 16, 2013 2:02 PM
> To: isaacs at adobe.com<mailto:isaacs at adobe.com>; kverma at 
> adobe.com<mailto:kverma at adobe.com>; Syed.Hosain at 
> aeris.net<mailto:Syed.Hosain at aeris.net>;
> 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" 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 position as me.
>
> I wasn't feeling negative towards you, or disagreeing that following
> tech support's advice had fixed your problem. I lead a team of writers
> who all work on a single multi-chapter docs set. We can't just change
> our workflow so everyone's working on their local drives. And we're
> still on FM10 but planning to upgrade soon. So I looked at tech
> support's advice that FM11 didn't support networked drive locations, and
> thought "If that's true, we can't upgrade to FM11. If it's a long-term
> decision from Adobe, we'll have to stop using FM. That seems awfully
> unlikely."
>
> So it mattered to me to get things clarified by someone higher in Adobe
> than a tech support engineer. I'm relieved to find that FM11 does still
> support networked drive locations, as I expected.
>
> We don't always find that FM10 talks nicely with our networked servers,
> so sometimes we end up doing part of our workflow on our local drives
> too. I'm not surprised that moving a doc to your local drive would make
> a crashing doc behave. I just wanted people like Dov and Kapil to
> confirm that it's still the exception rather than the rule!
>
> Cheers and have a good day
> Rebecca
>
>
>
> >>> Ken Poshedly mailto:poshedly at 
> >>> bellsouth.net>> 02/17/13 1:55 AM >>>
> To all,
>
> Maybe I'm wrong but the argumentative tone of all of this with regards
> to my
> question is the pits.
>
> As far as I'm concerned:
> 1. Contact Shekhar at tcssup at adobe.com<mailto:tcssup at adobe.com> and 
> discuss it with him.
> 2. We did what

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

2013-02-19 Thread Robert Lauriston

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 problems we've seen: 3000+ page
> docs, lots of conditional text, sometimes can't create a PDF over the
> network.
>
> We're using a Novell server. Our IS team have checked for choke points,
> overloading etc, and can't find any problems. They reckon it's just Novell.
> We're going to be changing to a Microsoft server anyway, and they reckon
> that'll be happier with Frame. I hope they're right!
>
> Like you, we've "resolved" the issue by copying all the components to a
> local drive before creating the PDF. We're ok with having to do that part of
> the workflow locally, as long as we can keep editing the source files over
> the network.

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

2013-02-18 Thread Zimmerman, Gary

Hi Rebecca,

Just for the record, we have had instances where very large (2000 page) 
documents with extensive conditionalization have been unable to Save as PDF 
over the network.  I don't believe FM crashed, it just hung indefinitely and 
never finished PDF production.  This was probably due to network timeout 
issues, as relocating all the component book files (chapters, appendices, 
FM-generated TOC/index) to a local computer and saving as PDF there alleviated 
the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an issue for 
us with FM10, however we also removed a LOT of the now-unnecessary conditions 
and conditional text from those books.

Cheers.

-- garyZ


> -Original Message-
> From: framers-bounces at lists.frameusers.com [mailto:framers-
> bounces at lists.frameusers.com] On Behalf Of rebecca officer
> Sent: Saturday, February 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 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 position as me.
> 
> I wasn't feeling negative towards you, or disagreeing that following
> tech support's advice had fixed your problem. I lead a team of writers
> who all work on a single multi-chapter docs set. We can't just change
> our workflow so everyone's working on their local drives. And we're
> still on FM10 but planning to upgrade soon. So I looked at tech
> support's advice that FM11 didn't support networked drive locations, and
> thought "If that's true, we can't upgrade to FM11. If it's a long-term
> decision from Adobe, we'll have to stop using FM. That seems awfully
> unlikely."
> 
> So it mattered to me to get things clarified by someone higher in Adobe
> than a tech support engineer. I'm relieved to find that FM11 does still
> support networked drive locations, as I expected.
> 
> We don't always find that FM10 talks nicely with our networked servers,
> so sometimes we end up doing part of our workflow on our local drives
> too. I'm not surprised that moving a doc to your local drive would make
> a crashing doc behave. I just wanted people like Dov and Kapil to
> confirm that it's still the exception rather than the rule!
> 
> Cheers and have a good day
> Rebecca
> 
> 
> 
> >>> Ken Poshedly  02/17/13 1:55 AM >>>
> To all,
> 
> Maybe I'm wrong but the argumentative tone of all of this with regards
> to my
> question is the pits.
> 
> As far as I'm concerned:
> 1. Contact Shekhar at tcssup at adobe.com and discuss it with him.
> 2. We did what he told us to do.
> 3. No more problems (so far).
> 
> OK?
> 
> -- Ken
> 
> 
> 
> 
> ________
> From: Kapil Verma 
> 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 Everyone,
> 
> Hope you are well. Well, there has been a flurry of emails on this topic
> and I
> (as the product manager for FrameMaker) wanted to mention a couple of
> things
> here to set the record straight J
> 
> ? Network file paths: FrameMaker 11 has been tested to work with
> network
> file paths. There is absolutely no change in behavior between FM11 and
> the older
> versions. So, you should not have any problems when your files are
> stored on the
> network location. However, in case you are experiencing any crashes when
> working
> with network files, we will be happy to take a look at your crash logs
> and help
> your troubleshoot your specific issue.
> 
> ? FrameMaker Lock file:There is lot of discussion and some
> confusion
> around the purpose of the lock file. Lock file is created by FM to tell
> the user
> that the file is open in another instance of FM. So, if we take the
> scenario of
> multiple users working on the same file set (which is stored on the
> network
> drive) and when a file is opened in FM, it creates a lock file. If
> another user
> tries to open the same file, FM will give the other user a warning that
> the file
> is open in another instance of FM. So, this is a feature, that prevents
> users
> from overwriting each other?s content. Furthermore, If you

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

2013-02-17 Thread rebecca officer

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 position as me.

I wasn't feeling negative towards you, or disagreeing that following
tech support's advice had fixed your problem. I lead a team of writers
who all work on a single multi-chapter docs set. We can't just change
our workflow so everyone's working on their local drives. And we're
still on FM10 but planning to upgrade soon. So I looked at tech
support's advice that FM11 didn't support networked drive locations, and
thought If that's true, we can't upgrade to FM11. If it's a long-term
decision from Adobe, we'll have to stop using FM. That seems awfully
unlikely.

So it mattered to me to get things clarified by someone higher in Adobe
than a tech support engineer. I'm relieved to find that FM11 does still
support networked drive locations, as I expected.

We don't always find that FM10 talks nicely with our networked servers,
so sometimes we end up doing part of our workflow on our local drives
too. I'm not surprised that moving a doc to your local drive would make
a crashing doc behave. I just wanted people like Dov and Kapil to
confirm that it's still the exception rather than the rule!

Cheers and have a good day
Rebecca



 Ken Poshedly poshe...@bellsouth.net 02/17/13 1:55 AM 
To all,

Maybe I'm wrong but the argumentative tone of all of this with regards
to my 
question is the pits.

As far as I'm concerned:
1. Contact Shekhar at tcs...@adobe.com and discuss it with him.
2. We did what he told us to do.
3. No more problems (so far).

OK?

-- Ken





From: Kapil Verma kve...@adobe.com
To: Syed 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?!


Hello Everyone,
 
Hope you are well. Well, there has been a flurry of emails on this topic
and I 
(as the product manager for FrameMaker) wanted to mention a couple of
things 
here to set the record straight J
 
· Network file paths: FrameMaker 11 has been tested to work with
network 
file paths. There is absolutely no change in behavior between FM11 and
the older 
versions. So, you should not have any problems when your files are
stored on the 
network location. However, in case you are experiencing any crashes when
working 
with network files, we will be happy to take a look at your crash logs
and help 
your troubleshoot your specific issue.
 
· FrameMaker Lock file:There is lot of discussion and some
confusion 
around the purpose of the lock file. Lock file is created by FM to tell
the user 
that the file is open in another instance of FM. So, if we take the
scenario of 
multiple users working on the same file set (which is stored on the
network 
drive) and when a file is opened in FM, it creates a lock file. If
another user 
tries to open the same file, FM will give the other user a warning that
the file 
is open in another instance of FM. So, this is a feature, that prevents
users 
from overwriting each other’s content. Furthermore, If you don’t want
lock 
files, you can turn them off as well. Lastly, for more information,
about the 
lock file and its behavior, please read the help page here
 
Hope this information is useful and clarifies things. Have a great
weekend!
 
Thanks,
Kapil Verma
Sr. Product Manager – Adobe Technical Communication Products
 
 
From:framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Syed Zaeem
Hosain 
(syed.hos...@aeris.net)
Sent: Friday, February 15, 2013 5:43 A
M
To: Dov Isaacs; Alan T Litchfield; framers@lists.frameusersWhat 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 much any Windows application today!
 
Thanks for the clarification,
 
Z
 
From:Dov Isaacs [mailto:isa...@adobe.com] 
Sent: 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 is

essentially unaware of the media and location of the file. The provided
file 
path, whether provided explicitly by the user with a file open dialog or

implicitly as a link in a document is used “as is” for operating system
file 
access calls. That having been said, when one accesses files on remote
and/or 
slow links or even with semi-reliable media (such as old and scratched
CD-Rs and 
DVD-Rs), read errors and/or timeouts can and do occur that are much less

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

2013-02-17 Thread rebecca officer

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 position as me.

I wasn't feeling negative towards you, or disagreeing that following
tech support's advice had fixed your problem. I lead a team of writers
who all work on a single multi-chapter docs set. We can't just change
our workflow so everyone's working on their local drives. And we're
still on FM10 but planning to upgrade soon. So I looked at tech
support's advice that FM11 didn't support networked drive locations, and
thought "If that's true, we can't upgrade to FM11. If it's a long-term
decision from Adobe, we'll have to stop using FM. That seems awfully
unlikely."

So it mattered to me to get things clarified by someone higher in Adobe
than a tech support engineer. I'm relieved to find that FM11 does still
support networked drive locations, as I expected.

We don't always find that FM10 talks nicely with our networked servers,
so sometimes we end up doing part of our workflow on our local drives
too. I'm not surprised that moving a doc to your local drive would make
a crashing doc behave. I just wanted people like Dov and Kapil to
confirm that it's still the exception rather than the rule!

Cheers and have a good day
Rebecca



>>> Ken Poshedly  02/17/13 1:55 AM >>>
To all,

Maybe I'm wrong but the argumentative tone of all of this with regards
to my 
question is the pits.

As far as I'm concerned:
1. Contact Shekhar at tcssup at adobe.com and discuss it with him.
2. We did what he told us to do.
3. No more problems (so far).

OK?

-- Ken





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 and must quit" Really?!


Hello Everyone,

Hope you are well. Well, there has been a flurry of emails on this topic
and I 
(as the product manager for FrameMaker) wanted to mention a couple of
things 
here to set the record straight J

? Network file paths: FrameMaker 11 has been tested to work with
network 
file paths. There is absolutely no change in behavior between FM11 and
the older 
versions. So, you should not have any problems when your files are
stored on the 
network location. However, in case you are experiencing any crashes when
working 
with network files, we will be happy to take a look at your crash logs
and help 
your troubleshoot your specific issue.

? FrameMaker Lock file:There is lot of discussion and some
confusion 
around the purpose of the lock file. Lock file is created by FM to tell
the user 
that the file is open in another instance of FM. So, if we take the
scenario of 
multiple users working on the same file set (which is stored on the
network 
drive) and when a file is opened in FM, it creates a lock file. If
another user 
tries to open the same file, FM will give the other user a warning that
the file 
is open in another instance of FM. So, this is a feature, that prevents
users 
from overwriting each other?s content. Furthermore, If you don?t want
lock 
files, you can turn them off as well. Lastly, for more information,
about the 
lock file and its behavior, please read the help page here

Hope this information is useful and clarifies things. Have a great
weekend!

Thanks,
Kapil Verma
Sr. Product Manager ? Adobe Technical Communication Products


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: Friday, February 15, 2013 5:43 A
M
To: Dov Isaacs; Alan T Litchfield; framers at lists.frameusersWhat 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 much any Windows application today!

Thanks for the clarification,

Z

From:Dov Isaacs [mailto:isaacs at adobe.com] 
Sent: 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 in general is

essentially unaware of the media and location of the file. The provided
file 
path, whether provided explicitly by the user with a file open dialog or

implicitly as a link in a document is used ?as is? for operating system
file 
access calls. That having been said, when one accesses files on remote
and/or 
slow links or even with semi-reliable media (such as old and scratched
CD-Rs and 
DVD-Rs), read errors and/or timeouts can and do occur that are

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

2013-02-16 Thread Ken Poshedly

To all,Maybe I'm wrong but the argumentative tone of all of this with regards to my question is the pits.As far as I'm concerned:1. Contact Shekhar at tcs...@adobe.com and discuss it with him.2. We did what he told us to do.3. No more problems (so far).OK?-- KenFrom: Kapil Verma kve...@adobe.comTo: "Syed 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.comSent: Fri, February 15, 2013 7:33:39 AMSubject: RE: "FrameMaker has detected a problem and must quit" Really?!
Hello Everyone, Hope you are well. Well, there has been a flurry of emails on this topic and I (as the product manager for FrameMaker) wanted to mention a couple of things here to set the record straight J · Network file paths: FrameMaker 11 has been tested to work with network file paths. There is absolutely no change in behavior between FM11 and the older versions. So, you should not have any problems when your files are stored on the network location. However, in case you are experiencing any crashes when working with network files, we will be happy to take a look at your crash logs and help your troubleshoot your specific issue. · FrameMaker Lock
file: There is lot of discussion and some confusion around the purpose of the lock file. Lock file is created by FM to tell the user that the file is open in another instance of FM. So, if we take the scenario of multiple users working on the same file set (which is stored on the network drive) and when a file is opened in FM, it creates a lock file. If another user tries to open the same file, FM will give the other user a warning that the file is open in another instance of FM. So, this is a feature, that prevents users from overwriting each other’s content. Furthermore, If you don’t want lock files, you can turn them off as well. Lastly, for more information, about the lock file and its behavior, please read the help page here Hope this information is useful and clarifies things. Have a great weekend! Thanks,Kapil VermaSr. Product Manager – Adobe Technical Communication Products From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Syed Zaeem Hosain (syed.hos...@aeris.net)Sent: Friday, February 15, 2013 5:43 AMTo: Dov Isaacs; 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 much any Windows application today! Thanks for the clarification, Z From: Dov Isaacs [mailto:isa...@adobe.com] Sent: Thursday, February 14, 2013 1:24 PMTo: Syed Zaeem Hosain (syed.hos...@aeris.net); Alan T Litchfield; framers@lists.frameusers.comSubject: RE: "FrameMaker has detected a problem and must quit" Really?!Importance: High With regards to network folders and drives, Adobe software in general is essentially unaware of the media and location of the file. The provided file path, whether provided explicitly by the user with a file open dialog or implicitly as a link in a document is used “as is” for operating system file access calls. That having been said, when one accesses files on remote and/or slow links or even with semi-reliable media (such as old and scratched CD-Rs and DVD-Rs), read errors and/or timeouts
can and do occur that are much less likely than when accessing a file on a “local” drive. The Adobe applications typically don’t attempt any special recovery operations when such read errors and/or timeouts occur. That is likely the source of problems reported. - Dov Dov IsaacsPrincipal ScientistAdobe Systems Incorporated+1 408.536.2896 (tel)+1 408.242.5161 (cell)isa...@adobe.com345 Park AvenueSan Jose, CA 95110-2704 USAhttp://www.adobe.comFeel 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-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Syed Zaeem Hosain (syed.hos...@aeris.net)Sent: Wednesday, February 13, 2013 12:32 PMTo: Alan T Litchfield; framers@lists.frameusers.comSubject: 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 application executables are on my drive C and the data files are
on drive E on the _same_ system. I.e., drive E is _not_ a network-mounted drive ... it is physically installed on my laptop. For this "all local drives" arrangement, there should _never_ be any issue for any modern Windows application. However, if the data files are on a network se

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

2013-02-16 Thread Alan T Litchfield

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  
installation. Kapil has said there is no new bug in FM 11 that would  
prevent it from opening and working with files on a network and that  
FM 11 does the same that earlier versions did. I don't think you can  
justifiably blame FM in this case. That being said, we have no idea of  
what hardware and software comprise your network, nor do we know  
anything about the software or configuration on the PC on which FM is  
installed. Any of those may be contributing factors.

The advice you received is the easy out. It rules out two thirds of  
possible problems and in this case it appears the cause may be  
somewhere in that two thirds.

This same outcome has been observed by listers but with a range of  
causes.

Good luck.

Alan

On 16/02/2013, at 2:54 AM, Ken Poshedly wrote:

> To all,
>
> Maybe I'm wrong but the argumentative tone of all of this with  
> regards to my question is the pits.
>
> As far as I'm concerned:
> 1. Contact Shekhar at tcssup at adobe.com and discuss it with him.
> 2. We did what he told us to do.
> 3. No more problems (so far).
>
> OK?
>
> -- Ken
>

--
AlphaByte
PO Box 1941, Auckland, 1140
New Zealand
http://www.alphabyte.co.nz

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

2013-02-15 Thread Ken Poshedly

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 AtlantaFrom: Dov Isaacs isa...@adobe.comTo: "framers@lists.frameusers.com" framers@lists.frameusers.comCc: "techw...@techwr-l.com" techw...@techwr-l.comSent: Thu, February 14, 2013 4:08:42 PMSubject: 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 where X:\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 IsaacsPrincipal ScientistAdobe Systems Incorporated+1 408.536.2896 (tel)+1 408.242.5161 (cell)isa...@adobe.com345 Park AvenueSan Jose, CA 95110-2704 USAhttp://www.adobe.comFeel 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-boun...@lists.frameusers.com [mailto:framers-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 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,

1 2 >

1 - 100 of 113 matches

Mail list logo