RE: Where do you shoot trouble?

[bryan -dot- westbrook -at- amd -dot- com]

Its own chapter or an appendix, with references to any appropriate sections that are needed for fixing the problem.  Most people are only going to refer to the manual for only two reasons, and if the setup is self-explanatory only one: when something goes wrong.  Don't make someone who is probably already frustrated have to go hunting for the troubleshooting mixed into the other text.  If they knew where to look for the fix already they wouldn't be using the T/S section anyway.  They would just go to the procedure.


-----Original Message-----
From: Lin Sims [mailto:linda -dot- sims -at- verizon -dot- net]
Sent: Tuesday, February 12, 2002 3:38 PM
To: TECHWR-L
Subject: Where do you shoot trouble?


For my own peace of mind, I want to make a decision I can stick to. 
Where should troubleshooting information go, in a chapter all of its 
own, or scattered through the chapters covering the individual areas 
where trouble may arise? There are reasons for going either way, and 
I've been dithering between them for too long.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.