Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+CW\s+Serial\s+Interface\s+\-\s+SOLVED\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+CW\s+Serial\s+Interface\s+\-\s+SOLVED\s*$/: 2 ]

Total 2 documents matching your query.

1. [TRLog] CW Serial Interface - SOLVED (score: 1): Author: jsroux@msn.com (Sheryl Roux); Date: Mon, 22 Jul 2002 09:55:27 -0400; First, thanks to all who responded to my request for help. =20 My problem was that the parallel interface keyed the rig but the serial p= ort did not work. All I got at pin 4 of the COM1 port was a c; /archives//html/TRLog/2002-07/msg00098.html (6,773 bytes)
2. [TRLog] CW Serial Interface - SOLVED (score: 1): Author: rrossi@btv.ibm.com (Ron D. Rossi); Date: Mon, 22 Jul 2002 11:23:13 -0400; Sheryl, The COM# in windows is just a label and does not always equate the prot address you think it does. It is also subject to change if you add or change your hardware UNLESS you turn that feature; /archives//html/TRLog/2002-07/msg00099.html (8,547 bytes)

Current List: 1 - 2
Page: [1]