Dave

LOL

Been doing it for 8 years and have never made a mistake and created a zombie. To be honest I am much more likely to make a mistake now since the application fixes a location rather than asking me??

The blank selection is still there why not continue to have a selection when it is set and label the upload selection as (user selection) rather than having to do 2 menus down to reset it?

More interesting is that last night in trying to upload a Maine contact and figure out the change, I somehow got the selection menu to come up (guess its still there) but could not reproduce what I did to make it happen.

Not a big issue. I just am amazed that alot of folks (mobile, multiple QTHs, etc) aren't doing the same thing.

As alway one of the hardest thing to modifiy is the user interface...

All the best

Bob KB1JZU

So are two extra mouse clicks each month not worth a higher probability

of accurate LotW uploads, especially given that a busted upload creates a
Zombie that can't be repaired?

73,

Dave, AA6YQ

I've read about the SSD's failing after a certain amount of read/writes...
is this an issue?

73 de Chuck, WS1L

On Mon, Aug 6, 2012 at 5:18 AM, Rich - W3ZJ <rich@w3zj.com> wrote:

**


Solid State Drives (SSD) are indeed now appearing in the mainstream.
They are still a bit more expensive per megabyte than rotating electro
mechanical hard drives. But they are fast, reliable and finally
available in usable capacities (128, 256 and 512 GB). My wife has a
128GB SSD in her new Toshiba Ultabook, an amazingly small and light full
featured Laptop, and as Dave said, it "Screams".

73, Rich - W3ZJ

Chuck Chandler wrote:

A complete check disk found and replaced some bad sectors. All now works
as it should.

A review of Event Viewer shows no 1005 errors in the Application Log

until

today.

DXKeeper had no errorlog.txt, and Launcher had one with a single entry

from

back in 2011.

I'll keep a careful eye on the hard drive, and start checking into
replacing it.

73 de Chuck, WS1L

A complete check disk found and replaced some bad sectors. All now works
as it should.

A review of Event Viewer shows no 1005 errors in the Application Log until
today.

DXKeeper had no errorlog.txt, and Launcher had one with a single entry from
back in 2011.

I'll keep a careful eye on the hard drive, and start checking into
replacing it.

73 de Chuck, WS1L

Hi Pat,

Then I think you just need to reduce your "Tail" setting, and increase
"Paddle Hang".

GL/73,

~iain / N6ML


On Sun, Aug 5, 2012 at 1:48 PM, f6gcp <f6gcp@...> wrote:

Hi Ian,

thanks on information. I have checked running Winkey2 software, and it
shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't
know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@yahoogroups.com, iain macdonnell - N6ML <ar@> wrote:

On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@> wrote:

Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is
quite
ok for CW operation using the keyer, and to avoid trcv to go to
receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as
set
to 500ms is a too long (the pile_up "TU" to confirm qso could be
missed!).

Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.

Using the opcode "stop" (while running the winkey test software), the
PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to
immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML

AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 5:45 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Winkey and <stop>


Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is
immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

What commands are sent to the WinKey when the "WinKey Test Software" is

directed to "stop"?

73,

Dave, AA6YQ

AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
alanswinger
Sent: Sunday, August 05, 2012 12:00 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: LOTW/DXKeeper Station Location match


Dave - I did follow the LoTW Certif transfer insts, and had TQSL and TQSL
Cert saved on a DVD after I renewed them last yr. I also checked the
station_data files on both PCs and they were the same except for unique
computer user names. So, I Edited the Station Location file in TQSL Cert on
the new PC to make it is the same as the Old PC and the Station File, and
also made sure Keeper reflected the edit.
I uploaded all QSOs in Keeper since I put the new PC on line (7/5-8/5/12) to
LoTW this morning. LoTW confirmed receipt so I snch'd QSOs and QSLs, and got
the following message:
- LOTW OPerations: 4 QSLs processed; 4 Log entries updated, 0 errors. No new
confirmations of previously unconfirmed entity-bands or entity-modes.

I expected nothing new, so the message is correct from that aspect, and
appears that the upload and responses are correct. Also checked the LoTW
Sent Boxes and all show a Y and today's date.

Therefore, it appears that all is working properly. Other than receiving a
LoTW QSO confirmation, is there anything else to check?

That all sounds good, Alan, but the proof of the pudding will be when one

of the QSOs logged and uploaded from your new laptop gets confirmed via
LotW.

73,

Dave, AA6YQ