Re: Must change from 5770-BR1 to 5770-BR2 (BRMS) -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Must change from 5770-BR1 to 5770-BR2 (BRMS)
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 27 Aug 2024 11:07:45 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 8/27/2024 10:43 AM, Rob Berendt wrote:

It can be read another if you're concerned that some environmental change
(ptf, media firmware update, etc) could break something and that be
considered a new defect and thus not covered.
Basically the same conversation we had about SDA, etc.

I don't feel it's the same because if I find a new defect in SDA, I can use SEU (shudder) and edit the DDS. If I find a new defect in BRMS, how bad is my recovery posture?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.