Frame Crashing

[Karyn Hunt]

In this case, I'm certain it's not the network b/c everything is on my local hard drive. FrameMaker and RoboHelp are installed on my C drive under Program Files. The image folders are under "My Documents." (The path is roughly <project name>/Frame files + a subfolder with the images/images. It's the final folder <images> that keeps corrupting. 

Another oddity is that even if FrameMaker isn't open, once that folder decides not to cooperate, I can't even open it in Windows Explorer. We can, however, get images out if we go into it in a command window (DOS).

k

-----Original Message-----
From: Bob Colwell [mailto:bob.colwell at comcast.net] 
Sent: Friday, April 07, 2006 10:41 AM
To: Art Campbell; Karyn Hunt
Cc: framers
Subject: RE: Frame Crashing

Back in 1987 I had been using Framemaker for a couple of years, when
a new version came out that included a networking feature. I tried 
using it, and found that everything had slowed to a crawl. I sent off
a blistering review of the new product to Framemaker, and got an email
back a few days later from the president of the company, apologizing
for our troubles, expressing surprise, and suggesting some experiments
to try to pinpoint the problem. The first experiment showed that it was
our own (new) network causing the problem. I sent a contrite "whoops,
never mind" to Framemaker. Had this been a Windows network (impossible
in 1987, yeah I know) I would have suspected that right away...-BobC

-----Original Message-----
From: framers-bounces+bob.colwell=comcast.net at lists.frameusers.com
[mailto:framers-bounces+bob.colwell=comcast.net at lists.frameusers.com]On
Behalf Of Art Campbell
Sent: Friday, April 07, 2006 10:22 AM
To: Karyn Hunt
Cc: framers
Subject: Re: Frame Crashing


Are the FM and graphics files local, on a network drive, or mixed?

If the network is involved, hiccups there and in the way Windows is
reading the network file system would be my first guess.

Art