Thanks to all (2 Steves, Martin, RW, Mel, Robert) who responded about my problem with CT import. Apparently there is/was a problem with the CT b9r conversion utility that DX4WIN uses for import. The answer was to use the c2a utility from CT which converts to .bin to ADIF. ADIF import then worked perfectly.
Pete, K2PS -----Original Message----- From: Steve Bookout [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 7:14 PM To: Pete Stafford Subject: Re: [Dx4win] Imported Time Offset Hello Pete, You have a problem with your CT b2r9.exe utility. When it converts to ASCII it makes this time error. You can either get a new file from the CT home page or send it to me and I'll do it for you. I'll send it back and you can do a merge with your main log. 73 de Steve, NR4M At 03:56 PM 5/22/02 -0400, you wrote: >This has undoubtedly been covered earlier, but I found an old CT9 bin file >that I had never imported into DX4WIN. This dates from Oct 2000. When I >attempt to import into v5.03, it subtracts 7 hours from each QSO. >Fortunately I had saved the log before importing (I feel so smart...) so I >could un-import. > >Anyone know how to resolve this? > >Pete, K2PS >_______________________________________________ >Dx4win mailing list >[email protected] >http://mailman.qth.net/mailman/listinfo/dx4win 73 de Steve, NR4M -No goats were harmed in the making of this 'cheese'.
