My apologies for using the word "spam" if that offended you. I have
tried to explain that in another post, as has Bruce Barrett.

You argue that I should search the archive, then go to the mailing list
for answers. This is more efficient than a forum?

I have only submitted questions to CTM which do not have answers in the
user's manual. Have you looked at the user's manual? It is pretty
limited in what it covers. So are the FAQs on CTM's web site.

While you may feel that CTM answers questions, my experience is that it
does not. I just went to the ctmdev.com web site and found that they no
longer even mention sending an email to CTM to ask for help. They also
have taken down their notice that they would respond to 80% of help
requests within 2 days. The option to email CTM from the PowerMail Help
menu is still there, however. 

But since CTM doesn't answer, email to CTM works more like the Apple
reporter that appears when a program quits unexpectedly. CTM should note
in PM that they rarely answer. Most people who send in a request for
help would assume they'd get an answer. Setting up a method to send in a
support request when there is little likelihood of an answer is wrong.


Regards,

- Winston




Matthias Schmidt wrote:

>Webforums are not an alternative at all. They are so much more time
>intensive, extremely slow, you always have to login etc.....

>Mr. Weinmann,
>
>calling this list a source of spam is a serious offense to all list members.
>If you can't read the users manual nor search the archive, with all
>respect, go somewhere else.
>CTM never lacked support, but they won't answer you questions if you can
>find the answer in the users manual. That are not support cases that's a
>lack of reading ability.
>
>Matthias

>what's wrong with this list?
>If you have a problem, search first the archives, which can be found here:
><http://tinyurl.com/ypovoh> 
>then you can ask here on the list.
>The list is read by the developers and they will respond if there's a
>real problem.
>
>all the best
>
>Matthias



Reply via email to