RE: [smartBridges] Why not just do a recall?

[Jerry Fisher]

Title: Message

But now sB has to keep 2 developement and testing lines going.  Any future release of firmware and/or software has to be tested on both the good units and bad units.  As you said "The downside was the "unforseen" problem with the firmware patch . . .   Jerry Fisher -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Haynes Sent: Tuesday, July 22, 2003 4:34 PM To: [EMAIL PROTECTED] Subject: RE: [smartBridges] Why not just do a recall? A firmware upgrade would be a much easier and less time consuming fix. The downside was the unforseen problem with the firmware patch. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Fisher Sent: Tuesday, July 22, 2003 3:06 PM To: [EMAIL PROTECTED] Subject: [smartBridges] Why not just do a recall? I'm wondering why sB didn't just do a recall and replace the units that were affected.  If there were only 2,000 units, it seems that this would have been a much better solution instead of taking the PR hit that this is causing.  I would think that this would only take a couple of days of manufacturing to accomplish.  This would have also saved the time and effort involved in trying to "fix" a batch of bad units in the field.  The affected units are still going to be in the field and will always be susceptible to any new "fixes" designed for the "good" units.   Jerry Fisher