[WriteLog] Re:Damaged log problem

n9qqk at urbancom.net n9qqk at urbancom.net
Sun Jul 18 19:13:42 EDT 2004


Hi John.

I'm the one who was trying to reconstruct a corrupted WL log file.
Mine got screwed up during the 2003 ARRL DX CW test.  Recovering the text
portions isn't difficult.  It's the date-time field that was my main problem.
Search the WL reflector archives for "corrupt log file" to see the discussion.

I'm including below Wayne's off list reply that gave me the info I needed
to complete the reconstruction.  I never would have thought that date-time
would be recorded as "100 nanosecond intervals since 01-Jan-1601".
I think that Microsoft (or some other computer concern) coined this standard.

I'd be happy to help with the log if you'd like.  Hope this info helps.

73, Ron - N9QQK 

------- Forwarded message follows -------
Date sent:      	Fri, 21 Feb 2003 11:58:44 -0600 (CST)
Subject:        	Re: email received?
From:           	"Wayne Wright, W5XD" <w5xd at writelog.com>
To:             	<n9qqk at urbancom.net>
Send reply to:  	w5xd at writelog.com

> Wayne,
>
> Did you receive my email regarding a corrupted .WL file during the  ARRL
> DX cw?
>
> Ron - N9QQK

Yes. I looked at it. I wasn't able to recover it.

I did see your requests for the time and frequency format.
Here's all the info I can provide:

Somewhere near the CALL field you found (within 20 or 30 bytes), there is
an 8 byte sequence containing the time, coded this way:

The FILETIME structure is a 64-bit value representing the number of
100-nanosecond intervals since January 1, 1601.


Also in the same vicinity there are two consectutive four byte fields that
have the transmit and receive frequences. The frequency coding is an
integer in multiples of 10 Hz. (where 3.5MHz, for example appears as
350000). (If you were not operating split, they will match, so you should
see the same four bytes twice in a row).

Wayne




------- End of forwarded message -------


More information about the WriteLog mailing list