subject:"RE\: 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
 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.

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.

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" 
>>> mailto: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>
>  [mailto:framers-
> boun...@lists.frameusers.com<mailto:boun...@lists.frameusers.com>] On Behalf 
> Of rebecca officer
> Sent: Saturday, February 16, 2013 2:02 PM
> To: isa...@adobe.com<mailto:isa...@adobe.com>; 
> kve...@adobe.com<mailto:kve...@adobe.com>; 
> syed.hos...@aeris.net<mailto:syed.hos...@aeris.net>;
> a...@alphabyte.co.nz<mailto:a...@alphabyte.co.nz>; 
> poshe...@bellsouth.net<mailto:poshe...@bellsouth.net>; 
> framers@lists.frameusers.com<mailto: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 mailto: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 Shek

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"  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  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 
> To: "Syed Zaeem Hosain (syed.hos...@aeris.net)"
;
> Dov
> Isaacs ; Alan T Litchfield ;
> "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 ca

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

2013-02-19 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-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  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 
> To: "Syed Zaeem Hosain (syed.hos...@aeris.net)" ;
> Dov
> Isaacs ; Alan T Litchfield ;
> "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
> f

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  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 
To: "Syed Zaeem Hosain (syed.hos...@aeris.net)" ;
Dov 
Isaacs ; Alan T Litchfield ; 
"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), re

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 To: "Syed Zaeem Hosain (syed.hos...@aeris.net)" ; Dov Isaacs ; Alan T Litchfield
; "framers@lists.frameusers.com" Sent: 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.com Feel free to print this e-mail if your needs dictate hard copy.There is no need to feel guilty about printing!Paper is renewable and recyclable.
ISAACS-OFFICE.corp.adobe.com From: framers-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 server, even if that folder/dr

59 matches

Mail list logo