Also check that your Windows UAC (User account control) has the slider set to the lowest setting
Perhaps uninstal AVG - Instal Log4om - Reinstall AVG (If you must ) AVG quiet often returns false positives that why I just use the Windows protection
Search found 10309 matches
- 21 Mar 2015, 09:15
- Forum: User Support
- Topic: v1.20 problems
- Replies: 13
- Views: 8673
- 20 Mar 2015, 17:18
- Forum: User Support
- Topic: installation 1.20
- Replies: 3
- Views: 2299
Re: installation 1.20
dk2lo wrote:Does this release still requires the old version to be uninstalled before the new one is installed?
Depends which old version you have
Older than 1.19 remove the old one before installing 1.20
1.19 you can instal 1.20 without removing 1.19
- 20 Mar 2015, 15:21
- Forum: User Support
- Topic: database maintenance
- Replies: 2
- Views: 2284
Re: database maintenance
No need just set the auto backups
- 20 Mar 2015, 06:59
- Forum: User Support
- Topic: Massive Change G to V
- Replies: 6
- Views: 3550
Re: Massive Change G to V
Use the QSO archive manager
Sort for all of the QSO with granted then select the and bulk edit the field to Y
I did a YouTube video tutorial about the bulk editor, search on Google for it
Sort for all of the QSO with granted then select the and bulk edit the field to Y
I did a YouTube video tutorial about the bulk editor, search on Google for it
- 19 Mar 2015, 19:15
- Forum: User Support
- Topic: DX Call 7QAA
- Replies: 9
- Views: 5994
Re: DX Call 7QAA
I just manually logged it as Malawi from the drop down menu. ON another note, would be good if one could filter out unrecognised DXCCs on the Cluster spots, to stop the Z6's clogging up my Cluster timeline! We thought about that but when someone mistypes an O for a zero like GOOFE or KOOK although ...
- 19 Mar 2015, 15:35
- Forum: Error Reports
- Topic: QSO information missing-invalid call
- Replies: 10
- Views: 8179
Re: QSO information missing-invalid call
OK we found the problem when Don sent me his logbook Our special call list had the wrong DXCC for the dates of Don's QSO’s with 9Q50OM back in 2010, this is why the old QSO’s updated with 412 but new QSO's were OK Chuck has updated the two files and I have attached them to this post, copy them to th...
- 18 Mar 2015, 12:25
- Forum: Error Reports
- Topic: QSO information missing-invalid call
- Replies: 10
- Views: 8179
Re: QSO information missing-invalid call
Hi Terry thanks for the test it depends on the recorded data If I insert today a qso with 9q50on I have the same behaviuor you have (correct) if I work with existing data (old qsos) the wrong behaviior is reproduced (incorrect) I will do some more investigation ; it is not a big issue, just to full...
- 18 Mar 2015, 12:23
- Forum: User Support
- Topic: Label Design/printing
- Replies: 5
- Views: 5447
Re: Label Design/printing
One thing I still seem to have a problem with is getting "PSE QSL" and "TNX QSL" to come out right on label but I will get it figured out. Later.... In Log4om Options - QSL and Labels tab set the response as required then if a QSO is marked as QSL received your outgoing card wil...
- 18 Mar 2015, 08:33
- Forum: Error Reports
- Topic: Incorrect Solar Data
- Replies: 7
- Views: 5770
Re: Incorrect Solar Data
confirmed I am now seeing the same thing so your probably both correct in saying that we probably only display 2 digits for A & K index, only Lele could confirm that
- 18 Mar 2015, 07:47
- Forum: Error Reports
- Topic: QSO information missing-invalid call
- Replies: 10
- Views: 8179
Re: QSO information missing-invalid call
Don, I entered a QSO with 9Q50ON and edited the country to "Republic of the Congo DXCC 412" and saved it as in the archive manager screen shot below Then I highlighted the entry and clicked the "Update QSO" button on the QSO Archive manager tool bar - The entry was updated to &qu...