I welcome mail about analog, both praise and bug reports! I and others are
also usually happy to help people who have trouble with analog: it helps me
to find bugs, and know where the documentation is unclear.
If your statistics are provided by someone else, for example your web hosting
company, you should normally get support from them. They're the only ones who
can configure analog to your specifications.
Getting help with analog from experienced users. This is the place to go
if you have trouble setting up or configuring the program. Usually you will
get a swift reply. You have to subscribe to the list before you can send a
message. This is necessary to deter spammers. You can subscribe at http://lists.meer.net/mailman/listinfo/analog-help
This just goes to me. Use for private comments, or other things that would
not be suitable for the analog-help list. I'm pretty bad at
answering my mail, so don't expect a swift reply. Don't use this address
for user support questions: they will be ignored.
Read the FAQ. Maybe I've answered your question
already. If I have, I'll just direct you to the FAQ, not answer it
If analog produced some error messages when it ran, they probably
indicate what went wrong. Read the section on
Errors and warnings.
If your question is "Will this command have that effect?", why
not try it and see!
If you think you've found a bug, read the
known bugs at my site, to see if your bug is already known about.
Read the other relevant pages of the Readme, particularly the sections
on Starting to use analog and
Customising analog. You may also
find the index useful. We don't appreciate people
who are too lazy to read the documentation. (If the documentation is
unclear, or the relevant paragraph is too well hidden, then that's a
different matter. Of course I want to know about that.)
Have a look in the web archives of the
mailing list to see if your question has already been answered there.
If analog isn't doing what you thought you asked it to, then run it with
the SETTINGS ON
command, and see what options it thinks it's meant to be using.
I'm sorry to be so fussy, but a lot of the mail on the list really needn't
have been sent at all, and just wastes the time of everybody on the list. As
I say, I really do welcome genuine mail.
If you still need help, subscribe to the to the analog-help mailing list using
the form at
and then send your mail to firstname.lastname@example.org.
Please do the following when you send mail to the list.
Describe exactly what you did, what you expected, and what the computer
did. Include the exact text of any error messages, not a
Mention which version of analog you are using, on which operating
Although you should obey the first two points, you should also try and
send a short message. Most people don't bother to read long messages.
Give your mail a subject line which indicates immediately what aspect of
analog it is about. (This is useful for the archives).
Do not send long files or attachments unless you're
asked to. We do not want to see your configuration file, your header
file, your output file, or any logfile over 10 lines long. They are
almost always useless to us. And anyway, excessively long messages will
be rejected by the mailing list server.
If you want to send a private message to me, you can send it to me at
Please don't use this address for user support questions: I don't have
time to answer them, and I'll just ignore them.There are several web archives of
the analog-help list. You can find them at these places: