Sorry for the previous accidental post.
What I intended to say was ...


If the CBOS image is corrupted while attempting an upgrade,
the router can still be restored using the serial Xmodem
transfer process described in the Cisco documentation.

If you do corrupt the DSL router, see it as an opportunity
as well as a problem.  You can get a free new 678 if you
sound convincing to a Qwest tech support representative.

If you do everything exactly as described by the
upgrade documentation and the upgrade fails and renders
the router inoperable then the only possible cause
is a defecting router or defective upgrade software.
If you are losing thousands or merely hundreds of
dollars/day because of Qwest or Cisco's defective
hardware or software, Qwest will probably be glad
to express ship a brand new 678 for free.
The cost to Qwest is nothing compared to the
potential negative publicity.

Typical scenario:
Cisco 675 locks up 3 or 4 times/day due to CBOS
defects documented at cisco.com, in newsgroups and
websites.  The 675 has to be power cycled to restore
operation.

Someone corrupts the CBOS image while trying to upgrade
the CBOS image with Kermit 7 Xmodem (transfer errors).

Fearing that paying a single cent to the Evil Empire
would cause eternal damnation of one's soul, someone
installs DRDOS and a free "backup" copy of windows
and uses Hyperterminal Xmodem to transfer the CBOS
upgrade image to the 675 running in the monitor mode.

The free new 678 and spare upgraded 675 work flawlessly
after the CBOS upgrades.

To the purist, using windows may be cheating, but
purity may be overrated in some situations.
--
jm


Eric Richardson wrote:

> Patrick Fleming EA wrote:
>
>  > I upgraded mine(678) using minicom. Once the settings were correct
>  > in  minicom as, set by using root, I did #minicom cisco (where
>  > cisco is the name of the configuration file) Hit enter at the
>  > minicom screen and you should get the  cbos> prompt. Follow the
>  > instructions on power cycling the modem then  upload and
>  > configuration from here:
> http://www.infomagic.net/pipermail/luna/2002-March/001335.html
>  >
>
>  >
>  > I did find that if you hold down ctrl+C before powering back up you
>  > are  more likely to get the correct prompt the first time.
>  >
> I tried this on the Mac but since I don't have the correct serial to USB
> adapter it wouldn't work-I could connect and get the prompt and such but
> after that it wouldn't work. I tried using the same file via minicom and
> I get a Communications error but I bet that the file is not recognized
> as it is probably in Macbinary format or something. The download for
> windows is an exe so that is not going to help. Cisco doesn't allow
> secondary customers to download the images so I'm stuck I think for the
> time being. One thing good is when the process fails, the system reboots
> to the old version.
>
> Eric
>
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss