<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: HELP ME! in AutoCAD Forum</title>
    <link>https://forums.autodesk.com/t5/autocad-forum/autocad-installer-freezes/m-p/5441444#M346024</link>
    <description>&lt;P&gt;I don't have anything to offer that hasn't already been said.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But for future knowledge, you'd be better served by giving a short, informative and concise description of the issue in the subject line.&lt;BR /&gt;&lt;BR /&gt;If I have a few minutes to spare (such as waiting for someone in my office and I don't want to start a new task, I will browse the forums looking for a message that I can read and provide assistance with quickly. The subject lines are what I use to decide what to read in that case. But a subject line of "Help" or other similarly uninformative subject line doesn't tell me anything about the issue so I skim past it. I'm sure there are others who do the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In this case, a subject line of "Acad 2015 Installer Freezes" would have been a lot better than "Help Me".&lt;/P&gt;</description>
    <pubDate>Fri, 12 Dec 2014 15:07:34 GMT</pubDate>
    <dc:creator>doni49</dc:creator>
    <dc:date>2014-12-12T15:07:34Z</dc:date>
  </channel>
</rss>

