NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/biz/comp/telebit/1101

Internet Message Format | 1992-12-30 | 3.4 KB

Xref: sparky biz.comp.telebit:1101 comp.dcom.modems:18691
Newsgroups: biz.comp.telebit,comp.dcom.modems
Path: sparky!uunet!pgroup!lfm
From: [e-mail] (Larry Meadows)
Subject: Re: Kudos to Telebit. (was: Complaint about telebit)
Message-ID: <[e-mail]>
Date: Wed, 30 Dec 1992 16:14:59 GMT
Distribution: na
References: <[e-mail]> <[e-mail]>
Organization: The Portland Group, Portland, OR
Lines: 70

>Karl Denninger ([e-mail]) wrote:
>:[ lots of nice stuff about telebit ]
>: I've been nothing but happy with Telebit's responsiveness and performance,
>: and have been a loyal customer for many years -- dating back to their early
>: Trailblazer days.
>:
>
In article <[e-mail]> [e-mail] writes:
>
>[Lots more nice stuff about telebit]
>Nothing but rave reviews from this happy camper..
>
>Bret Marquis
>
>Customer support has been superb

Well, I'm in between these two happy campers and the original unhappy
camper.  I've got several T1000, Trailblazer+, T3000, Worldblazer,
Netblazer, and Qblazer, and a Dowty Trailblazer.

The netblazer went DOA after 3 weeks, they sent a new one no questions
asked & it has worked fine now for over 1 year.

The modems all work fine, except... now for the story.

I purchased 2 T3000 with the worldblazer upgrade.  The upgrade was a modem
swap, all went as expected.  One of the T3000s is used for a full-time
SLIP link.  It had worked flawlessly for several months.  When I exchanged
it for the Worldblazer (mind you, there was no need to do this, I just thought
I would go ahead & upgrade), I plugged it in, upgraded my modemcap.txt, and
rebooted.

Worldblazer worked fine for a few hours, then locked up.  This went on
for a few days, sometimes I could reset the worldblazer from the netblazer,
but more often I'd have to power-cycle it.  Telebit entered a MR (whatever
that is) on the problem, and finally (after 4-8 days) agreed to swap me
BACK for a T3000.  They also said they figured out what the problem was
and would upgrade me back to a Worldblazer (new Roms, I guess) after they
had the problem fixed.

Well, I never heard anything else.  To be truthful, I haven't tried to
follow up on it, since I don't really need the additional TurboPEP for
that modem.

However, I do still have another Worldblazer.  For a while, I had it at
home, and it worked fine connected to a PC.  Even talked to it at 100+
Kbps (and I don't even have a 16550 Uart).  Then, I bought a Qblazer, and
connected the Worldblazer to the Netblazer at work.  I've had lots of
problems since then --

1. Talk to the modem line will sometimes just exit with no apparent
reason, then the modem will lock up and need to be reset.

2. The first time I call the modem, it answers, but I can't get a prompt
from the netblazer.  If I call back, it works fine.  It will then work
for a while, but after a few hours, gets back into the state where it
has to be called twice.

3. Occasionally it has locked up completely and required power cycling.

Now, I'll admit that I haven't chased these problems down with Telebit,
for a couple of reasons:  I have other modems, I don't have time right
now, and I'm hoping someone on the net will do the work for me.  But, I've
been considering replacing all my modems with rack-mount worldblazers; I
will definitely make sure these problems are resolved before I spend that
much money & time.

--
Larry Meadows        The Portland Group
[e-mail]