[TRLog] Using TRLog with the Elecraft K2 & KIO2
Tom Hammond NěSS
Tue, 28 Aug 2001 09:20:06 -0500
No flames inferred... and please understand that I wasn't on a 'quest' for
Basically, I was attempting to remind folks (including myself) that
sometimes we tend to forget about things we do so naturally (e.g. drop to a
DOS window), and then can't figure out why some softwares don't work as we
expected them to.
I was certainly NOT trying to malign Tree for his efforts... I still think
the TRLog is the best logger around, othrwise I'd have jumped ship by now.
The message was originally prepared for the Elecraft reflector, where many
users there are just now beginning to find out about logging programs and
that they CAN use them with their Elecraft K2 QRP rigs now that Elecraft
has released the serial interface for the K2. And I'm fairly sure that a
number of them do not subscribe to the TRLog reflector, even though they
probably should. It just happened that I dumped a copy of the message here
I appreciate your reminder to check the archives first as well.
73 - Tom Hammond N0SS
At 08:05 AM 8/28/01, you wrote:
>None of this is new, Tom... (no flame intended)
>TRLOG was designed to run from DOS, not from an time sliced, redirected
>bios, aliased interrupts, simulated DOS screen, from inside of Windows...
>I'm not trying to be difficult here, but Tree has been right up front from
>the early days that TRLOG will not run reliably from inside of a windows,
>multitasking environment.... That new users don't take the time to simply
>scan the archives before they begin on a unicorn hunt is puzzling....
>Cheers ... Denny
>----- Original Message -----
>From: "Tom Hammond NěSS" <firstname.lastname@example.org>
>To: <email@example.com>; <firstname.lastname@example.org>
>Sent: Monday, August 27, 2001 7:26 PM
>Subject: [TRLog] Using TRLog with the Elecraft K2 & KIO2
> > Greetings:
> > I just spent way too much time with Wayne (N6KR, of Elecraft) trying to
> > figure out why my K2 w/KIO2 serial interface wasn't polling or updating
> > data properly when used with TRLog v6.58 or v6.95 (probably others as
> > Turns out that TRLog will not poll the K2 properly if TRLog is run from a
> > DOS window.
> > It functions properly(!) if TRLog is run from a DOS boot, either directly
> > from power-up or if Rebooted to DOS from within Windows.
> > When attempting to run TRLog from a DOS Window, the symptoms I was getting
> > were:
> > 1) Failure to routinely update the displayed
> > frequency while tuning the VFO
> > 2) Blanking of the frequency display as the
> > VFO was being tuned, and then lengthy (up
> > 1:30) pauses before the new frequency was
> > displayed
> > 3) Periodic failure to update band changes when made
> > from the K2
> > 4) Display of the wrong band when changed from
> > within TRLog
> > All of these symptoms dieappeared as soon as I rebooted directly to DOS.
> > Just a note of caution to Elecraft K2 owners, and for the information of
> > Tree (N6TR).
> > 73 - Tom Hammond N0SS
> > --
> > FAQ on WWW: http://www.contesting.com/FAQ/trlog
> > Submissions: email@example.com
> > Administrative requests: trlog-REQUEST@contesting.com
> > Problems: firstname.lastname@example.org
> > Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Administrative requests: trlog-REQUEST@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html