Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Jupiter\s+firmware\s+problems\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Jupiter\s+firmware\s+problems\.\s*$/: 6 ]

Total 6 documents matching your query.

1. [TenTec] Jupiter firmware problems. (score: 1): Author: wa3fiy@radioadv.com (WA3FIY); Date: Mon, 26 Aug 2002 15:39:34 -0400; What am I missing here? I see a company that is dedicated to delivering exceptional radios at a fair price and then, for no additional charge, improving the product and delivering the result over the; /archives//html/TenTec/2002-08/msg00490.html (10,223 bytes)
2. [TenTec] Jupiter firmware problems. (score: 1): Author: w9ac@arrl.net (Paul Christensen); Date: Mon, 26 Aug 2002 15:54:28 -0400; One solution is to post new software/firmware as "BETA TEST ONLY." If you're up to it, download the software and be part of a group who is willing to test drive it and record and report any imperfect; /archives//html/TenTec/2002-08/msg00492.html (11,529 bytes)
3. [TenTec] Jupiter firmware problems. (score: 1): Author: wa3fiy@radioadv.com (WA3FIY); Date: Mon, 26 Aug 2002 16:02:05 -0400; Yes Paul, that sounds like an interesting and effective way of upgrading the firmware. Of course, the big question is, how does it sound to the guys at Ten Tec? :-) Anyway, I don't mind trying out th; /archives//html/TenTec/2002-08/msg00495.html (7,738 bytes)
4. [TenTec] Jupiter firmware problems. (score: 1): Author: RMcGraw@Blomand.Net (Robert & Linda McGraw K4TAX); Date: Mon, 26 Aug 2002 15:15:09 -0500; All this reminds me of a story of a group of folks that were touring a bronze foundry. This location made very large bronze doors like one would find on court houses, federal buildings and the like.; /archives//html/TenTec/2002-08/msg00497.html (12,155 bytes)
5. [TenTec] Jupiter firmware problems. (score: 1): Author: n9dg@yahoo.com (Duane Grotophorst); Date: Mon, 26 Aug 2002 14:34:17 -0700 (PDT); I too agree that this would be an excellent way to handle these kinds of firmware releases. Those of us who aren't squeamish about alpha and beta code can go ahead play, and the more conservative typ; /archives//html/TenTec/2002-08/msg00501.html (9,345 bytes)
6. [TenTec] Jupiter firmware problems. (score: 1): Author: attorney@broadcast.net (Paul Christensen); Date: Mon, 26 Aug 2002 15:53:33 -0400; One solution is to post new software/firmware as "BETA TEST ONLY." If you're up to it, download the software and be part of a group who is willing to test drive it and record and report any imperfect; /archives//html/TenTec/2002-08/msg00598.html (12,202 bytes)

Current List: 1 - 6
Page: [1]