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.
> ----------
> From: Huber, Mike[SMTP:mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM]
> Reply To: Huber, Mike
> Sent: Thursday, June 04, 1998 9:08 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: p.c. way to say "crashing"
>
> I don't like the term "crash" in documentation, and my dislike of the
> term has nothing to do with the unpleasantness of the event.
>
> "Crash" does not provide enough information for any purpose other than
> a
> "don't do this or Bad Things will happen" warning.
>
> What does "crash" mean? Lock up the program? Program disappearance?
> Blue
> Screen of Death? Lock up the system? Corrupt the files? Auto-reboot
> the
> system? Corrupt the system so some innocent program locks up? Burn
> hardware?
>
> What should I do when it crashes? Shut down the application? Reboot?
> Power-cycle? Re-install the program? Restore data files from backup?
> Hack the executable? Re-install the operating system? Junk the
> hardware?
>
> If I'm reading a notice that a program has been fixed so a particular
> crash doesn't happen, I want enough information to know if it's the
> crash that's been happening to me. And "crash" is too ambiguous in
> most
> cases.
>
> ---
> Office:mike -dot- huber -at- software -dot- rockwell -dot- com
> Home:nax -at- execpc -dot- com
>
> >-----Original Message-----
> >From: Lizak Kristin [SMTP:LizakKristin -at- JDCORP -dot- DEERE -dot- COM]
> >
> >I am looking for ideas. Marketing wants me to rewrite a sentence that
> refers
> >to your software program crashing. Obviously "crashing" is not a good
> word,
> >and they don't like "program quits responding."
> >
> >This is for an addendum to the Users Guide. A part of the program was
> fixed,
> >and we are looking for a tactful (i.e. "flowery") way to refer to
> when their
> >program fizzles out. Any suggestions would be welcome. THANKS.
> >
>
> &^~~~
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
> TECHWR-L)
>
>
