I just read Scott's email about potential file loss and the backup function within ACLog. I thought I would mention the solution I use on all computers here at my house. Scott is right in that there are many perils to data that exist and the biggest one is that it isn't IF a hard drive will fail it is WHEN will it fail. Some last for many years and some don't but the truth is that all hard drives will fail at some point and that includes SSDs as they have a finite number of read/write cycles until they too are prone to failure. I've been using Acronis True Image to backup my important drives for many years. I make an image of my drives which makes recovery hast and pretty painless. There are also other programs that will backup drives on a scheduled basis. There's even a backup option within Windows itself (not a particularly full featured one but it's there). There are cloud options but I like having a local solution as it makes recovery a lot faster. Both together would make losing data close to impossible! When the first drive I've had fail I was lucky in that I didn't loose a lot of irreplaceable stuff. But it still was a pain. As the years have gone by I've accumulated many gigs of photos and music files. Since we live in a digital world where you don't have negatives sitting in a drawer when you lose data it's gone forever. So think about backing up your computer regularly as you certainly don't want to lose the records of all your QSOs nor anything else you really treasure.


Steve KS4KJ


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Bain,

After the import, select all of the K1USN QSO records from the Recent Contacts main list, Click Edit from the top menu bar, click Fill Fields Determined by Call, click Selected Records.  That will populate missing fields such as state.  

You have to have a CallBook lookup source like QRZ, free AC Log Calldata, etc. for this to work.

73, Mitch
NWØM

Could be.  In any case, it's over my head :-)  I've got a geeky friend coming to my rescue later this week.  All the best! / Woody / WD9F

Interestingly, Ham Radio Deluxe recently posted a note about 64-bit Microsoft Office Updates  interfering with the HRD LogBook database.

No idea if there is a relationship here or not.

Ron, AC2C

Hi Scott and crew
If you backup files how big file size wise would the back normally be?

Hi Scott.  Thanks for this.  I have already tried this.  I think my problem is a computer problem of some kind.  Not a problem with the logger.  For some reason, my comports don't even show up in Device Manager.  Not even hidden... and I can't even find them in Bios to make sure they are enabled.  I used to run this particular computer with a Flex rig with some third party add ons.  I fear I inadvertently did something to make my comports invisible??  Any suggestions welcome from you or others, but I'm sure this is not a problem with you logger.  Thanks!! / Woody / WD9F

Following up... did some more testing... and no surprises.

I made up a command using <RST> even though that is not part of the Sweepstakes exchange.
The default "5NN" was inserted.

Then I intentionally entered WD5CMA as the callsign so that, with<SERIAL> = 68 and <RST> appended,
it would overflow the 24 character command buffer in the K2.

RI:KY <CALL> <SERIAL> N5IB 63 LA <RST>;

totals 24 CW characters counting the spaces, so the terminating semicolon is truncated
We can call the K2's behavior an "Elecraft feature" ... without receiving a valid terminator the command is ignored.
The rig doesn't transmit a partial, it does nothing, which is a good thing.

I'd say it's ready for Prime Time

Jim, N5IB

When you edit a qso and click More to add info to qso how do you get it to show up in the log of all the contacts

Lawrence,

I'm glad my suggestion worked for you, too.

Even a blind pig finds a truffle once and a while.

Bob, N3BD

Hi Scott,

Works like a champ!
Just tried it out with the K2.
Set it up as: F2 -> RI:KY <CALL> <SERIAL> N5IB 63 LA;

Running with the rig interface over my Bluetooth adapter.

It inserted the callsign and grabbed the next serial number just as intended.
In fact I let the program fetch my results from last year as a starting point
Would you believe the next available serial was 67 ??

Actually not as bad as it seems - I'd set out to run QRP and resolved to work only one station per section in quest of a sweep.
Managed 66 QSOs in 66 sections.

I'll go exercise it some more later this evening, and make up some commands that use <RST> as well.

Only thing I notice is that in the cheat sheet window all that showed was "RI: KY"
It would be a memory aid if however many characters of the command string that would fit could be displayed.

I'm getting psyched for Sweepstakes already!

Many ,many thanks,
Jim, N5IB