Hi,
        I saw this in comp.dcom.modems and have already reported on some
Motorola Codex 3265 to Multi-Tech MT2834ZDX problems:


Date: Mon, 15 Jul 1996 18:25:23 -0700
From: satchell{at}accutek.com (Stephen Satchell)
Newsgroups: comp.dcom.modems
Subject: Be a REPORTER, not a WHINER
Message-ID: 
Organization: Satchell Evaluations
NNTP-Posting-Host: ppp56.accutek.com
Lines: 43

A magazine modem reviewer needs your help.  I need for people to start
gathering enough information about problems so those problems can be
reproduced by me, and perhaps new testing scenerios written into the modem
testing standards.

When you encounter a problem:

1)  Record the initialization string used to configure each modem
involved.  Each of these strings should start with the &F (or &F1, or
whatever) command.  Failing that, provide a complete record of all
S-register settings.  The usual &V is insufficient because many modems
have settings which aren't displayed by &V.

2)  Record the make and model (and ROM version if you can get it) of each
modem involved.  The complete information is available by issuing ATI,
ATI1, ATI2,... ATI8, and ATI9.  Don't record OK and ERROR reports.

3)  Make a time line describing exactly what happens when.  Many modem
failures happen after some repeatable time; others fail at varying
intervals; still others fail at completely random times.  For example, the
spirialing-death syndrome takes a while to get going because the modems
have to "drift" far enough apart for them to start wanting to reset their
equalizers.  Note if the error suffers from "second-call" syndrome, where
it occurs only on the second or third or whatever call after an event such
as power-up.

4)  Note the country code, area code, and exchange for each modem
involved.  Also note which long-distance carrier was used if one is
involved. Full phone numbers may be provided, but is not necessary to
determine the most probable path of a call.  This information is used to
determine the exact type of telephone equipment used to carry the call.

5)  Include the names of anyone at telephone companies you've talked to
about the problem.  Don't bother with names of tech support people at the
modem companies -- I tend to bypass tech support and talk to the QA people
directly.

6)  If any modems have been swapped, upgraded, or repaired, note that as
well.  This is especially important if these sorts of events caused *any*
change, for better or for worse.

With this information, I have a chance of being able to reproduce the
problems, getting to a root source, and getting the problems fixed.  With
enough information, I can also *write* about what I find, because I will
have enough support for what I say to satisfy the libel lawyers.

No reason to keep these secret.  In fact, make sure these reports stick
out by putting the word REPORT in your subject line in your post.
-- 
Stephen Satchell, Satchell Evaluations
http://www.accutek.com/~satchell
Fanaticism consists of redoubling your effort when you have forgotten your
aim -- George Santayana

--- msgedsq 2.1