TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: RoboHelp For Word Crash/Reboot Problem From:"Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 8 Apr 2005 11:33:11 -0400
Opening, editing, or saving documents directly on a network drive using
Word is a known potential cause of Windows crashes and Word corruption.
Throwing RoboHelp into the mix only increases the potential for trouble.
When working on a Word document that's on a network, it's always
preferable to use Windows to create a local copy. That way, you can
open, edit, and save locally. When you're done, you can use Windows to
copy the new version back to the network.
Dan Goldstein
-----Original Message-----
From: Steven Oppenheimer
Sent: Friday, April 08, 2005 11:24 AM
To: TECHWR-L
Subject: RoboHelp For Word Crash/Reboot Problem
On my current contract I have been using RoboHelp for MS Word.
Recently, we upgraded the PC to Windows XP, and Office XP to Office
2003. Now I am having a problem where, when I am saving my files under
RoboHelp, the computer will spontaneously reboot. (No crash, really, or
blue screen of death, just a cold reboot.) The problem is intermittent,
but always happens when the .rtf file is being saved, and when the
progress indicator shows it is about 80% to 90% saved.
I checked on Macromedia's forums. Apparently, at least a few other
people have had this problem. One suggestion that I came across was
that the problem can occur if the files are being edited on a network
drive -- the solution is to edit files locally, and then (at the end of
the work day) copy them to the desired network location.
Since we have, in fact, been editing the files on a network drive, I
intend to try this next week (next time I'm at the client site), editing
the files on the PC's local drive...
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
