The file actually doesn't have a header at all. The first line was a <CALL:6> just like any other data record. The issue seems to be that D4W expects there to always be a header.
I re-read the spec, and it says: "Optional header information may be included before the actual data in the file" and "If the first character of a file is <, it is presumed to be the first field of the first data record." On 3/14/2011 12:19 AM, Jim Reisert AD1C wrote: > On Sun, Mar 13, 2011 at 6:53 PM, David Kozinn, K2DBK wrote: > >> I've started playing with JT65-HF and wanted to import the ADIF file >> that it creates. Apparently, it does not put a header in front of the >> data which, according to the ADIF spec that I read, is optional. >> However, when I try to import into D4W, it issues an error that the >> header can't be read and aborts the import. I can fix it trivially by >> editing the .ADI file to add a dummy header, but I'm wondering if this >> is a bug in D4W or if I've misread the spec and a header is actually >> required? > > The ADIF specification says: > > http://www.adif.org/adif227.htm > > "The header info must be terminated with <eoh>." > > If the file doesn't have that, contact the software's author and tell > him/her it's a bug. > > 73 - Jim AD1C > > -- 73, David, K2DBK http://k2dbk.blogspot.com http://k2dbk.com twitter: @k2dbk ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
