FA: Some nice HP gear from my home lab....

Jan 21, 2006 22 Replies

The broken version was 1.05, but I "slipstreamed" the fix into the same release without updating the version stamp.

I really should've bumped the version number when I posted the fix, but it'll be pretty obvious if your copy has the bug. It will appear to work, but it will always start the PN sweep at 0 Hz rather than the minimum offset you specify. That makes the sweep take much longer than necessary, and the trace information at offsets below 10x the analyzer's minimum RBW is meaningless.

Basically, if you downloaded it around the time I posted all those auctions, you probably got the bad version.

Heh... I've wondered where Microsoft came up with that; it might have come from the Unix world. There's a lot of weirdness in the calendar business, and it's usually less arbitrary, but more obscure, than it seems at first.

-- john, KE5FX

Do you take into account the days lost in the change from the Julian to the Gregorian calendars?

Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin

That's not my code, I should (hastily) note -- it's a comment that reflects the fact that the Win32 GetFileTime() API returns the number of 100-ns intervals since 1-Jan-1601, and I multiply the result by 10 to obtain a 64-bit microsecond counter. I'd assume that MS is doing the right thing.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required