Hi Barry,
Glad I could help you.
73 de Preben OZ5UR
It runs, thank you very much Preben! Amazing someone like you still had this kicking around!
?
very 73
de VE6BMX/VE6UM
Barry
|
Some of the ones I have seen don't allow "offline" use and then a way to sync the logs when you are back in mobile coverage. I don't want to have copy the loggings from one to the other, I want them to just appear in both versions. maybe a shared DB with some offline function?
|
Re: Teething pains transferring to Win 11 on a new computer
You said Have multiple copies of backups & complete Logger 32 folder
?
Good thinking Batman!
On 03/06/2025 6:57 PM EST Michael Mustachio via groups.io <mamustac372@...> wrote:
?
?
New computer, new SSD, with my old HDD installed as G: drive.
Got Logger up and running, everything transferred over, (Have multiple copies of backups & complete Logger 32 folder squirreled away on various devices.)
Got TQsl installed and transferred onto the new SSD.
Problem is now regarding LogSync. I can't swear 100% that it was working, but I'm pretty sure it was, although i didn't upload or download anything, at least it seemed to be OK.
Now, when i start Logger32, it starts, (is still loading), then starts Logsync, then Logsync freezes, then about 2 or 3 seconds later, Logger32 disappears from the screen, leaving me with a frozen Logsync screen.
I assume I should uninstall Logsync, and see what happens then.
Any advice on anything to try before I uninstall Logsync?
?
73? de? N2TBP? Mike
?
?
|
Teething pains transferring to Win 11 on a new computer
New computer, new SSD, with my old HDD installed as G: drive.
Got Logger up and running, everything transferred over, (Have multiple copies of backups & complete Logger 32 folder squirreled away on various devices.)
Got TQsl installed and transferred onto the new SSD.
Problem is now regarding LogSync. I can't swear 100% that it was working, but I'm pretty sure it was, although i didn't upload or download anything, at least it seemed to be OK.
Now, when i start Logger32, it starts, (is still loading), then starts Logsync, then Logsync freezes, then about 2 or 3 seconds later, Logger32 disappears from the screen, leaving me with a frozen Logsync screen.
I assume I should uninstall Logsync, and see what happens then.
Any advice on anything to try before I uninstall Logsync?
?
73? de? N2TBP? Mike
?
?
|
1. Depends on what you mean by offline, they all work "offline"
2. HAMRS pro (only the pro version) has snyc for 20 dollars a year. There is LOG4OM does cloud sync but i don't think it has and android app
3. They all should
4. good luck, but adif is text format. ?
?
?
|
It runs, thank you very much Preben! Amazing someone like you still had this kicking around!
?
very 73
de VE6BMX/VE6UM
Barry
|
Hello Barry,
I hope you can use the enclosed files.
Well, Google don't allow ZIP/EXE-files as attachment, so I have unzipped the file and renamed the EXE file to: C2A.bak (rename it back to C2A.exe)
If needed I have some older versions of the C2A.
Good luck.
vy 73 de Preben OZ5UR
well, here it is, 20+ years later and im looking for those expired links and hoping someone still has a copy kicking around to email me or send me to a valid site.? Am looking for C2A or LOGCONV.
?
Thanks everyone and anyone.
?
Barry
VE6BMX
|
Windows emulator on android and run Logger32. Problem solved.
|
Does anybody know of a good cross platform (Windows and Android) app that allows for logging contacts?
1. Must work "offline", so not web based
2. Must allow syncing between platforms (when in mobile coverage)
3. Must have a search function
4. Must allow export in CSV or text formats.
|
well, here it is, 20+ years later and im looking for those expired links and hoping someone still has a copy kicking around to email me or send me to a valid site.? Am looking for C2A or LOGCONV.
?
Thanks everyone and anyone.
?
Barry
VE6BMX
|
Re: Azimuth's problems...
Thank you Bob and Andrea,
I did as Bob said and it works again.
73 de Steph, F5NZY.
|
Re: Azimuth's problems...
QRZ lookup suck W4CK locator for za/w4ck.
Mike
|
Re: Azimuth's problems...
Here is working fine. w4ck.? ----> 297 za/w4ck ------> 115
73s
Andrea iz2lsc
... or maybe you have ZA/W4CK (or W4CK) logged with an incorrect gridsquare? What have you actually done to try to analyze the cause of your problem yourself? SeventyThree(s).
On 03/05/2025 8:27 AM EST Bob < k4cy@...> wrote:
?
?
Oh no, you've broken it again! Did you try reloading the Club Log exceptions and the Club Log LoTW/OQRS users databases again? SeventyThree(s).
?
?
Hi,
?
I don't know since when, but when I enter a callsign, the Azimuth indicated by logger is the right one, but if I precede the callsign with a prefix, followed by slash and the station code, instead of telling me the direction of the prefix that precedes, it always tells me the station direction.
?
Example:?
?
? ? ? W4CK: 293¡ã/113¡ã
ZA/W4CK: 293¡ã/113¡ã (the same)
?
When I enter ZA/W4C, it gives me the correct direction for ZA, 114¡ã/294¡ã, but when I enter the final K in the callsign, it changes back to 293¡ã (USA).?
?
73 de Steph, F5NZY.
|
Re: Azimuth's problems...
... or maybe you have ZA/W4CK (or W4CK) logged with an incorrect gridsquare? What have you actually done to try to analyze the cause of your problem yourself? SeventyThree(s).
On 03/05/2025 8:27 AM EST Bob <k4cy@...> wrote:
?
?
Oh no, you've broken it again! Did you try reloading the Club Log exceptions and the Club Log LoTW/OQRS users databases again? SeventyThree(s).
On 03/05/2025 8:17 AM EST Steph, F5NZY via groups.io <f5nzy@...> wrote:
?
?
Hi,
?
I don't know since when, but when I enter a callsign, the Azimuth indicated by logger is the right one, but if I precede the callsign with a prefix, followed by slash and the station code, instead of telling me the direction of the prefix that precedes, it always tells me the station direction.
?
Example:?
?
? ? ? W4CK: 293¡ã/113¡ã
ZA/W4CK: 293¡ã/113¡ã (the same)
?
When I enter ZA/W4C, it gives me the correct direction for ZA, 114¡ã/294¡ã, but when I enter the final K in the callsign, it changes back to 293¡ã (USA).?
?
73 de Steph, F5NZY.
|
Re: Azimuth's problems...
Oh no, you've broken it again! Did you try reloading the Club Log exceptions and the Club Log LoTW/OQRS users databases again? SeventyThree(s).
On 03/05/2025 8:17 AM EST Steph, F5NZY via groups.io <f5nzy@...> wrote:
?
?
Hi,
?
I don't know since when, but when I enter a callsign, the Azimuth indicated by logger is the right one, but if I precede the callsign with a prefix, followed by slash and the station code, instead of telling me the direction of the prefix that precedes, it always tells me the station direction.
?
Example:?
?
? ? ? W4CK: 293¡ã/113¡ã
ZA/W4CK: 293¡ã/113¡ã (the same)
?
When I enter ZA/W4C, it gives me the correct direction for ZA, 114¡ã/294¡ã, but when I enter the final K in the callsign, it changes back to 293¡ã (USA).?
?
73 de Steph, F5NZY.
|
Hi,
?
I don't know since when, but when I enter a callsign, the Azimuth indicated by logger is the right one, but if I precede the callsign with a prefix, followed by slash and the station callsign, instead of telling me the direction of the prefix that precedes, it always tells me the station direction.
?
Example:?
?
? ? ? W4CK: 293¡ã/113¡ã
ZA/W4CK: 293¡ã/113¡ã (the same)
?
When I enter ZA/W4C, it gives me the correct direction for ZA, 114¡ã/294¡ã, but when I enter the final K in the callsign, it changes back to 293¡ã (USA).?
?
73 de Steph, F5NZY.
|
Lorenzo What do you expect CheckSpot ? It only displays your interested DX spot. Yes, clicking does nothing. This is by design.
On 2025-03-05 Ë® 20:09:31, Lorenzo IK0HFO via groups.io <l.locicero@...> wrote: hi Aki
i click every where but nothing...
of course i make a wrong setup....but i put in a new forder the application ...i see Connected to logger32, i see the spot into? down bar (pse see the screen that i saved) but nothing
ciao
Lorenzo ik0hfo
|
hi Aki
i click every where but nothing...
of course i make a wrong setup....but i put in a new forder the application ...i see Connected to logger32, i see the spot into? down bar (pse see the screen that i saved) but nothing
ciao
Lorenzo ik0hfo
|
Rick the reason I said it didn't upload is because one, I received an error message telling me to check the error log which I cannot find, two, normally after it says successful I see the QSO's in the lower right corner being processed which I didn't this time, and third I have been unable to reach LOTW on my network for the past two days and am trying to troubleshoot that. The last time something like this happened I exported a partial log and manually signed it with TQSL then uploaded it and it didn't report any duplicate QSO's that I can recall so that tells me they were never uploaded, unless as you stated it might take a day or two for the original upload to appear.
?
Jim K2QB
|
Dear all ... the uploaded file if it is uploaded on LoTW will no longer be on your computer you just have to give the time for the server to manage and at the same time there is actually the crossing of data that's all ... if you have any doubts just manually
flag any suspicious qsos when at the next sending these will be added again if missing otherwise if they are already present you will be notified by the system.
73's Steve
"The utility removes all the Flag to Upload to LOTW before it actually uploads the file. "
This is not the case. This question is being asked by Logger32 and has not passed any Data off to the utility at this point.
"Today I attempted to upload almost 800 QSO'S to LOTW and the utility indicated the ADIF file was signed and uploaded and asked if I wanted to remove the QSL upload flag to which I said yes. When I attempted to download from LOTW I was told there was an
error and to try again later. Well, the server was not available so now I have almost 800 QSO's that should still be flagged as Send LOTW QSL."
How do you know your qso's are not uploaded to LOTW? If you received a return from TQSL that says the upload was complete. 9 out of 10 times your qso's are located on LOTW and you just need to wait for them to show up. Over the past week I have been checking
LOTW a couple times a day for a qso to show up for another project I am working on and after 2 days it finally showed up for the other station I worked but I have yet seen no confirmation from the other station yet to show in my qso's.
"Isn't there a way that the Send LOTW QSL flag wouldn't get removed until there is an actual confirmation of a successful upload, not just the signing of the ADIF file by TQSL?"
On the utility on the LOTW tab there is a checkbox that tells the utility to update the qso flags in Logger32 as each qso is uploaded. This takes QUITE a bit of time (With 800 qso's I estimate about 20 minutes.) and a lot of people do not want to wait
that long. So the checkbox was put in place.
73 Rick N2AMG
On 3/3/2025 1:24 PM, Jim K2QB via groups.io wrote:
First thanks to Rick for the QSL utility and his other add-ins that work great. One issue with the QSL utility that I wish could be addressed is the following. The utility removes all the Flag to Upload to LOTW before it actually uploads the file. Today
I attempted to upload almost 800 QSO'S to LOTW and the utility indicated the ADIF file was signed and uploaded and asked if I wanted to remove the QSL upload flag to which I said yes. When I attempted to download from LOTW I was told there was an error and
to try again later. Well, the server was not available so now I have almost 800 QSO's that should still be flagged as Send LOTW QSL.
Isn't there a way that the Send LOTW QSL flag wouldn't get removed until there is an actual confirmation of a successful upload, not just the signing of the ADIF file by TQSL?
?
Thanks...K2QB
|
Joe N3XLS
Mike
Lorenzo IK0HFO
Jim K2QB
Stefano Zoli