Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Re\:\s+Marking\s+Mods\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Re\:\s+Marking\s+Mods\s*$/: 3 ]

Total 3 documents matching your query.

1. [TenTec] Re: Marking Mods (score: 1): Author: k4to@meginc.com (Dave Sublette); Date: Thu, 08 Oct 1998 16:47:25 -0400; I think the label on the back panel is a poor idea because over time, labels become soiled. Some even deteriorate until they look bad and as an added bonus, won't come off, short of using toxic chemi; /archives//html/TenTec/1998-10/msg00069.html (7,092 bytes)
2. [TenTec] Re: Marking Mods (score: 1): Author: paulc@mediaone.net (Paul Christensen); Date: Thu, 8 Oct 1998 17:00:20 -0400; Placing the unit's serial number in the owner's manual along with the modification & maintenance documentation will also help to match the mods to a specific piece of equipment. On schematics, I gene; /archives//html/TenTec/1998-10/msg00070.html (8,445 bytes)
3. [TenTec] Re: Marking Mods (score: 1): Author: dacalvin@us.ibm.com (Duane Calvin); Date: Thu, 8 Oct 1998 17:29:54 -0400; I put a dated description label inside the rig on the chassis near where a mod is made to identify it (if visible) and to flag its presence. Then I make notes in the manual about when a mod was made,; /archives//html/TenTec/1998-10/msg00072.html (7,386 bytes)

Current List: 1 - 3
Page: [1]