Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+INTERFACING\s+ICOM\s+7851\s+AND\s+WRITELOG\s+V12\.20D\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+INTERFACING\s+ICOM\s+7851\s+AND\s+WRITELOG\s+V12\.20D\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] INTERFACING ICOM 7851 AND WRITELOG V12.20D (score: 1): Author: "noll amidzich" <namidzich@wi.rr.com>; Date: Tue, 10 Oct 2017 22:48:35 -0500; Trying to control ICOM 7851 radio using Writelog Version 12.20d. Running Windows 10. Attempting set up , get error message after doing the following... Open Writelog log/ set up /ports Select com por; /archives//html/WriteLog/2017-10/msg00013.html (7,137 bytes)
2. Re: [WriteLog] INTERFACING ICOM 7851 AND WRITELOG V12.20D (score: 1): Author: K6UFO Mark Aaker <k6ufo@arrl.net>; Date: Wed, 11 Oct 2017 18:14:34 +0000 (UTC); Hi Noll, This sounds like a problems with Windows thinking the Com port is missing, not setup, or in use by some other previous program. Does Com 3 show in the Device Manager, Ports? Doesn't the 7851; /archives//html/WriteLog/2017-10/msg00014.html (7,464 bytes)
3. Re: [WriteLog] INTERFACING ICOM 7851 AND WRITELOG V12.20D (score: 1): Author: "noll amidzich" <namidzich@wi.rr.com>; Date: Thu, 12 Oct 2017 00:17:25 -0500; Mark, You were spot on.... Windows did not recognize (see) ANY ports , even though it had previously. Windows Device Manager did not even show a "Ports" Icon (and associated Icom driver files which w; /archives//html/WriteLog/2017-10/msg00016.html (8,465 bytes)

Current List: 1 - 3
Page: [1]