Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Embedded\s+Hex\s+Codes\s+\-\s+a\s+partial\s+solution\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Embedded\s+Hex\s+Codes\s+\-\s+a\s+partial\s+solution\s*$/: 2 ]

Total 2 documents matching your query.

1. [TRLog] Embedded Hex Codes - a partial solution (score: 1): Author: 00tlzivney@bsuvc.bsu.edu (00tlzivney@bsuvc.bsu.edu); Date: Sat, 22 Sep 2001 08:30:49 -0500 (EST); Thanks to Pete, N4ZR, I found a partial solution to my dilemna about the embedded hex code feature of 6.59. In my example posted earlier, Pete noted that the code <04> was used twice - once by TR to; /archives//html/TRLog/2001-09/msg00060.html (7,658 bytes)
2. [TRLog] Embedded Hex Codes - a partial solution (score: 1): Author: k2av@contesting.com (Guy Olinger); Date: Mon, 24 Sep 2001 10:38:46 -0700 (PDT); Is there a code that TR could (or already does) use as an "escape" to send in front of it's own control codes (including the escape code)? 73, Guy. == 73 & GL -- Guy Olinger, K2AV k2av@contesting.com; /archives//html/TRLog/2001-09/msg00061.html (9,011 bytes)

Current List: 1 - 2
Page: [1]