Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Anyone\s+using\s+their\s+Omni\s+VI\s+or\s+VI\+\s+with\s+MixW\s+v2\.0\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TenTec\]\s+Anyone\s+using\s+their\s+Omni\s+VI\s+or\s+VI\+\s+with\s+MixW\s+v2\.0\?\s*$/: 2 ]

Total 2 documents matching your query.

1. [TenTec] Anyone using their Omni VI or VI+ with MixW v2.0? (score: 1): Author: johnclif@ix.netcom.com (John Clifford); Date: Thu, 18 Oct 2001 17:16:50 -0700; If anyone is using MixW v2.0 with their Omni VI or VI+, please let me know how you are configured. I've tried the standalone ICOM735 and the IC-735 option under ICOM, and neither support transmit via; /archives//html/TenTec/2001-10/msg00165.html (7,489 bytes)
2. [TenTec] Anyone using their Omni VI or VI+ with MixW v2.0? (score: 1): Author: johnclif@ix.netcom.com (John Clifford); Date: Mon, 22 Oct 2001 09:59:44 -0700; I determined that the problem lies in the software... it is a bug/limitation in MixW 2.0. Evidently, the Omni VI's CAT command set is a superset of the Icom IC-735. Ten-Tec extensions include the com; /archives//html/TenTec/2001-10/msg00180.html (7,909 bytes)

Current List: 1 - 2
Page: [1]