Xref: utzoo comp.dcom.modems:2163 comp.mail.uucp:1532
Path: utzoo!utgpu!attcan!uunet!oddjob!uwvax!rutgers!ucsd!ucbvax!amdcad!rpw3
From: rpw3@amdcad.AMD.COM (Rob Warnock)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: Catatonic TrailBlazer Pluses
Message-ID: <22499@amdcad.AMD.COM>
Date: 31 Jul 88 10:35:59 GMT
References: <1461@pyrnj.uucp>
Reply-To: rpw3@amdcad.UUCP (Rob Warnock)
Distribution: comp
Organization: [Consultant] San Mateo, CA
Lines: 24

Hmmm... maybe this is a new & interesting problem...  but it's not yours alone.

Last weekend, several TB+'s at AMD (amdcad.amd.com) "locked up" exactly as
you described (*NOTHING* until you power-cycle), and when I got home (about
25 miles away) I discovered that the TB+ on "redwood.uucp" had locked up
exactly the same way. Coincidence?

Hasn't happened before or since. These are all new 4.0 units, bought within
the last 3 months.

(By the way, fix this with power cycling, not the paperclip reset, or else
you'll revert to factory settings. While the EEROM settings are not lost,
on some hosts you can't talk to the modem with factory settings! If you
have set S52=2, so that settings revert on DTR-down, you'll also get your
EEROM settings back when you power-cycle out of the "hang". Worked for me...)


Rob Warnock
Systems Architecture Consultant

UUCP:	  {amdcad,fortune,sun}!redwood!rpw3
ATTmail:  !rpw3
DDD:	  (415)572-2607
USPS:	  627 26th Ave, San Mateo, CA  94403