Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+T\s+Match\s+Design\s+Using\s+YO\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+T\s+Match\s+Design\s+Using\s+YO\s*$/: 3 ]

Total 3 documents matching your query.

1. [TowerTalk] T Match Design Using YO (score: 1): Author: dickrts@texoma.net (Dick Weber); Date: Thu, 11 Sep 1997 18:31:18 -0500; Recently I saw a posting about T-matches which said that setting them up is done by trail and error and that they can't be designed using models. My experience is totally opposite. To date, I have su; /archives//html/Towertalk/1997-09/msg00292.html (11,397 bytes)
2. [TowerTalk] T Match Design Using YO (score: 1): Author: dickrts@texoma.net (Dick Weber); Date: Fri, 12 Sep 1997 18:40:47 -0500; (I'll try this again ...) Recently I saw a posting about T-matches which said that setting them up is done by trail and error and that they can't be designed using models. My experience is totally op; /archives//html/Towertalk/1997-09/msg00318.html (11,441 bytes)
3. [TowerTalk] T Match Design Using YO (score: 1): Author: dickrts@texoma.net (Dick Weber); Date: Sat, 13 Sep 1997 07:38:22 -0500; (one last try) Recently I saw a posting about T matches which said that setting them up is done by trial an error and that they can't be setup using models. My experience is totally opposite. To date; /archives//html/Towertalk/1997-09/msg00326.html (11,512 bytes)

Current List: 1 - 3
Page: [1]