Frame Crashing
Hi Guys, I'm having a strange problem that my IT guys tells me is due to a bad interaction between Windows, FrameMaker and RoboHelp. Im wondering if any of you has seen this and if so, what you've done to correct it. To make a long story short, my Windows Explorer folders are becoming corrupted and crashing FrameMaker when I try to import images by reference. Things generally go okay for a while until I spend a fair amount of time importing several different images. Then all-of-a-sudden, the image folder will decide it just doesn't want to work with FrameMaker any more and it begins crashing (both Explorer windows AND FrameMaker) every time I try to import an image. If I physically move that folder elsewhere, like my desktop for example, it begins working again. But then I've broken all other reference links and I have to start over, which makes this solution unworkable. To date, the only workaround I can come up with is to move the image folder to the desktop, copy the new images in, then move the folder back to its usual spot for archival purposes, should I ever solve this vexing problem. My IT guys blames this on RoboHelp and says FrameMaker, Windows Explorer and RoboHelp don't play nicely together. But I dont' really believe him. My installation of RoboHelp is working just fine - no problems with it at all - just FrameMaker and Explorer. Any thoughts? Suggestions? I'm on FrameMaker 7.1 with RoboHelp X5.0.1 and Windows XP Professional version 2002, Service Pack 2. Karyn ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
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 On 4/7/06, Karyn Hunt [EMAIL PROTECTED] wrote: Hi Guys, I'm having a strange problem that my IT guys tells me is due to a bad interaction between Windows, FrameMaker and RoboHelp. I'm wondering if any of you has seen this and if so, what you've done to correct it. To make a long story short, my Windows Explorer folders are becoming corrupted and crashing FrameMaker when I try to import images by reference. Things generally go okay for a while until I spend a fair amount of time importing several different images. Then all-of-a-sudden, the image folder will decide it just doesn't want to work with FrameMaker any more and it begins crashing (both Explorer windows AND FrameMaker) every time I try to import an image. If I physically move that folder elsewhere, like my desktop for example, it begins working again. But then I've broken all other reference links and I have to start over, which makes this solution unworkable. To date, the only workaround I can come up with is to move the image folder to the desktop, copy the new images in, then move the folder back to its usual spot for archival purposes, should I ever solve this vexing problem. My IT guys blames this on RoboHelp and says FrameMaker, Windows Explorer and RoboHelp don't play nicely together. But I don't' really believe him. My installation of RoboHelp is working just fine - no problems with it at all - just FrameMaker and Explorer. Any thoughts? Suggestions? I'm on FrameMaker 7.1 with RoboHelp X5.0.1 and Windows XP Professional version 2002, Service Pack 2. -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Frame Crashing
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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Frame Crashing
Hi Guys, I'm having a strange problem that my IT guys tells me is due to a bad interaction between Windows, FrameMaker and RoboHelp. I?m wondering if any of you has seen this and if so, what you've done to correct it. To make a long story short, my Windows Explorer folders are becoming corrupted and crashing FrameMaker when I try to import images by reference. Things generally go okay for a while until I spend a fair amount of time importing several different images. Then all-of-a-sudden, the image folder will decide it just doesn't want to work with FrameMaker any more and it begins crashing (both Explorer windows AND FrameMaker) every time I try to import an image. If I physically move that folder elsewhere, like my desktop for example, it begins working again. But then I've broken all other reference links and I have to start over, which makes this solution unworkable. To date, the only workaround I can come up with is to move the image folder to the desktop, copy the new images in, then move the folder back to its usual spot for archival purposes, should I ever solve this vexing problem. My IT guys blames this on RoboHelp and says FrameMaker, Windows Explorer and RoboHelp don't play nicely together. But I don?t' really believe him. My installation of RoboHelp is working just fine - no problems with it at all - just FrameMaker and Explorer. Any thoughts? Suggestions? I'm on FrameMaker 7.1 with RoboHelp X5.0.1 and Windows XP Professional version 2002, Service Pack 2. Karyn
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 On 4/7/06, Karyn Hunt wrote: > Hi Guys, > >I'm having a strange problem that my IT guys tells me is due to a bad > interaction between Windows, FrameMaker and RoboHelp. I'm wondering if any of > you has seen this and if so, what you've done to correct it. > >To make a long story short, my Windows Explorer folders are becoming > corrupted and crashing FrameMaker when I try to import images by reference. > Things generally go okay for a while until I spend a fair amount of time > importing several different images. Then all-of-a-sudden, the image folder > will decide it just doesn't want to work with FrameMaker any more and it > begins crashing (both Explorer windows AND FrameMaker) every time I try to > import an image. > >If I physically move that folder elsewhere, like my desktop for example, > it begins working again. But then I've broken all other reference links and I > have to start over, which makes this solution unworkable. > >To date, the only workaround I can come up with is to move the image > folder to the desktop, copy the new images in, then move the folder back to > its usual spot for archival purposes, should I ever solve this vexing problem. > >My IT guys blames this on RoboHelp and says FrameMaker, Windows Explorer > and RoboHelp don't play nicely together. But I don't' really believe him. My > installation of RoboHelp is working just fine - no problems with it at all - > just FrameMaker and Explorer. > > Any thoughts? Suggestions? > > I'm on FrameMaker 7.1 with RoboHelp X5.0.1 and Windows XP Professional > version 2002, Service Pack 2. -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358
Frame Crashing
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 /Frame files + a subfolder with the images/images. It's the final folder 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.colw...@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@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
Frame Crashing
Karyn, I'd say you're having a hard drive or OS problem. One key is your "Other Oddity" -- that isn't normal behavior for Windows XP. Have you run Norton, checkdisk, or a similar disk utility to check both the media and the operating system (and the file / directory structure) out? And have you backed your files up? Art On 4/7/06, Karyn Hunt wrote: > 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 > /Frame files + a subfolder with the images/images. It's the > final folder 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). > -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358
