Hi Bill, This is one of the reasons I prefer signing ADIF logs rather than Cabrillo. ADIF has a well-defined enumeration of modes. Cabrillo does not.
73 - Jim AD1C On 2/1/2008 2:27 PM, AC0W wrote: > I had this problem and discovered the problem was with my file that I sent in > and not LOTW. > > I used a cabrillo file from a contest to generate the file to upload. Well > the cabrillo file had as mode PHONE. So this followed all the way through and > was accepted by LOTW. When I did the report of course it came back as PHONE > versus in DX4WIN I had those QSO properly identified as SSB. > > I had to export that group of Q's from DX4WIN, do the TQSL thing and then > upload to LOTW server. > > Now maybe LOTW should not accept contacts sent in that list the mode as > PHONE. For now LOTW considers PHONE any of the possible PHONE modes and it > will match to contacts from other people listing SSB, FM, AM, etc at the mode. > > Bill > AC0W -- Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Feb 7 10:35:19 2008 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Thu Feb 7 10:39:24 2008 Subject: [Dx4win] Telenet In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> There are some tips at the bottom of this page: http://dx4win.ad1c.us/cluster.htm 73 - Jim AD1C On 2/4/2008 2:27 PM, [EMAIL PROTECTED] wrote: > When I sign on to the local telnet (W9ODD), I have to scroll down to > the w9odd entry , highlight it, then hit enter. > Has anyone successfully put one of these telnet entries on a hot key, > so all you had to do was click on one key (button). > I've tried putting all the information on the line into a key but it > didn't work. > This is not a complaint, just trying to streamline things. -- Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Feb 7 12:44:25 2008 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Thu Feb 7 12:48:31 2008 Subject: [Dx4win] Error Message In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 2/2/2008 10:53 AM, [EMAIL PROTECTED] wrote: > I just imported my ADIF log file into the latest DX4WIN and notice > that some of my contacts contain the following error message in the > notes column. > Error:Prefix=291 Your ADIF.PMP file is out-of-date. See http://dx4win.ad1c.us and follow the Country Files link. 73 - Jim AD1C -- Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Feb 7 12:49:09 2008 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Thu Feb 7 12:53:15 2008 Subject: [Dx4win] DX spot color FJ/G3TXF In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 2/4/2008 3:25 PM, Siegfried Methner wrote: > The DX spot color for FJ/G3TXF must be yellow because it's a new country > for me. But it's here on 17m CW gray (confirmed QSO with the same > callsign in 1998 in my log). If the spot is indicated as PHONE (Remarks: > up 81,7 ; QSX: 18161,7) the color is yellow (as expected). Spots on > other bands are okay as yellow. I think DX4WIN will always set the call to gray if it matches exactly a previous QSO in your log (call, band, mode). I don't think the actual country matters. I just tried this with an old FJ call and the spot was gray, not yellow. I think there may be a way for Paul to fix this. I'll ask. 73 - Jim AD1C -- Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Feb 7 22:19:55 2008 From: [EMAIL PROTECTED] (Joe Stepansky) Date: Thu Feb 7 22:24:03 2008 Subject: [Dx4win] Error message relating to DX4Win Message-ID: <[EMAIL PROTECTED]> Hello all! My brother Steve, KC3WX, has asked me to post this message as he's not yet registered on this reflector. He's been running DX4Win under Vista for a few months now (latest version) and decided to load N1MM for contesting. After loading N1MM he discovered that his DX4Win packet access disappeared. He then decided to remove N1MM to try and go back to square 1. However, after removing N1MM, he now gets the following message when trying to open DX4Win: portdriverc:\windows\system32\vichwll.sys cannot be used continue without access to LPT ports? Any ideas what this might be? Packet was working fine before he installed N1MM, though I have no idea why that might make a difference. Steve's email is [EMAIL PROTECTED], and I'm copying him on this message. Thanks! 73, Joe KQ3F
