Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Interfacing\s+the\s+Omni\s+VI\s+to\s+CT\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Interfacing\s+the\s+Omni\s+VI\s+to\s+CT\s*$/: 2 ]

Total 2 documents matching your query.

1. [TenTec] Interfacing the Omni VI to CT (score: 1): Author: np3g@coqui.net (Karen Whall/Terry Burkholder); Date: Sun, 16 Aug 1998 14:02:03 -0300 (ADT); I have a new Omni VI+ and so far have been unable to get it to talk to CT. I do have it talking to my DXbase logging program OK. Any suggestions? I have loaded the TSR for the proper comm port and se; /archives//html/TenTec/1998-08/msg00114.html (7,259 bytes)
2. [TenTec] Interfacing the Omni VI to CT (score: 1): Author: seay@alaska.net (Del Seay); Date: Mon, 17 Aug 1998 06:09:08 -0800; Hi Terry: I use CT with mine all of the time. First thing to look at is the cable. Make sure it is a straight thru job, not a "Null-Modem" cable. ( 1 to 1, 2 to 2. etc.) Then, the address of the devi; /archives//html/TenTec/1998-08/msg00138.html (8,887 bytes)

Current List: 1 - 2
Page: [1]