Date   

Re: Some assistance please

Tom Wylie
 

That seems to have done the trick thanks, now importing my log.....

Thank you so mucbh

Tom
GM4FDM

On 23/07/2018 09:31, ja1nlx wrote:
Tom
You need to run Logger32.exe and Logger32autoinstaller.exe (in the Logger32 folder)
as administrator.
73
On 2018/07/23 17:24, Tom Wylie wrote:
Having run Logger 32 for some considerable time without difficulties, how do do certain things is a distant memory.

My old trusty Windows XP Pro puter has finally bitten the dust and I am trying to setup in a Used Dell Windows 10 computer.    8 Mbs RAM and 500Gb hd.

I downloaded a fresh copy of version 350 and set it up and it runs OK, but continually tells me there is a new upgrade available, which I tell the machine to download and run,  but it refuses to upgrade saying that I need to have administrator privilages.

I have gone into Logger32 properties and told it to run with administration privilages, but it refuses to budge.

How can I update it to the most recent 358 version?


Tom
GM4FDM





Re: Some assistance please

Tom Wylie
 

OK Thanks I will try that.....

Tom
GM4FDM

On 23/07/2018 09:31, ja1nlx wrote:
Tom
You need to run Logger32.exe and Logger32autoinstaller.exe (in the Logger32 folder)
as administrator.
73
On 2018/07/23 17:24, Tom Wylie wrote:
Having run Logger 32 for some considerable time without difficulties, how do do certain things is a distant memory.

My old trusty Windows XP Pro puter has finally bitten the dust and I am trying to setup in a Used Dell Windows 10 computer.    8 Mbs RAM and 500Gb hd.

I downloaded a fresh copy of version 350 and set it up and it runs OK, but continually tells me there is a new upgrade available, which I tell the machine to download and run,  but it refuses to upgrade saying that I need to have administrator privilages.

I have gone into Logger32 properties and told it to run with administration privilages, but it refuses to budge.

How can I update it to the most recent 358 version?


Tom
GM4FDM





Re: Some assistance please

ja1nlx
 

Tom

You need to run Logger32.exe and Logger32autoinstaller.exe (in the Logger32 folder)

as administrator.

73


On 2018/07/23 17:24, Tom Wylie wrote:
Having run Logger 32 for some considerable time without difficulties, how do do certain things is a distant memory.

My old trusty Windows XP Pro puter has finally bitten the dust and I am trying to setup in a Used Dell Windows 10 computer.    8 Mbs RAM and 500Gb hd.

I downloaded a fresh copy of version 350 and set it up and it runs OK, but continually tells me there is a new upgrade available,  which I tell the machine to download and run,  but it refuses to upgrade saying that I need to have administrator privilages.

I have gone into Logger32 properties and told it to run with administration privilages, but it refuses to budge.

How can I update it to the most recent 358 version?


Tom
GM4FDM






--

73 de aki ja1nlx


Re: Some assistance please

Paul Ormandy
 

Hi Tom,

Close Logger32 if it is open. Go into your C: drive and double-click on the Logger 32 folder on your system using Windows Explorer (short cut hold down the Windows key to the left of the Alt an Space Bar and press 'E'), find logger32.exe application, right click and select "Run As Administrator".

You can also go to the Search tool down beside the State button and type in "User Access Control", and slide the bar down to one of the lower security settings. Mine uses the second lowest setting.

Cheers,

Paul

On 23-Jul-18 20:24, Tom Wylie wrote:
Having run Logger 32 for some considerable time without difficulties, how do do certain things is a distant memory.

My old trusty Windows XP Pro puter has finally bitten the dust and I am trying to setup in a Used Dell Windows 10 computer.    8 Mbs RAM and 500Gb hd.

I downloaded a fresh copy of version 350 and set it up and it runs OK, but continually tells me there is a new upgrade available, which I tell the machine to download and run,  but it refuses to upgrade saying that I need to have administrator privilages.

I have gone into Logger32 properties and told it to run with administration privilages, but it refuses to budge.

How can I update it to the most recent 358 version?


Tom
GM4FDM


--
ZL4TT


Some assistance please

Tom Wylie
 

Having run Logger 32 for some considerable time without difficulties, how do do certain things is a distant memory.

My old trusty Windows XP Pro puter has finally bitten the dust and I am trying to setup in a Used Dell Windows 10 computer. 8 Mbs RAM and 500Gb hd.

I downloaded a fresh copy of version 350 and set it up and it runs OK, but continually tells me there is a new upgrade available, which I tell the machine to download and run, but it refuses to upgrade saying that I need to have administrator privilages.

I have gone into Logger32 properties and told it to run with administration privilages, but it refuses to budge.

How can I update it to the most recent 358 version?


Tom
GM4FDM


Re: Flagging UDP imports for LOTW export?

Steve VE3RX
 

I had it checked for the Import option, but missed the logbook entry setup option, it was not obvious. I've got it checked now, and seems to work with a test QSO from WSJT-X.

Thanks

Steve VE3RX


Re: Flagging UDP imports for LOTW export?

ja1nlx
 

Steve

If you mean "Import Logs" then check "Flag QSOs for LoTW export file" option.

If you mean "Direct logging" via UDP or TCP then check "Flag QSOs for LoTW" in Logbook

entry window Setup menu.

73


On 2018/07/23 4:44, Steve VE3RX wrote:
When one normally imports an ADIF file, it gives options to flag them for export to LOTW, eQSL, etc...  However, there is no such option with UDP packets that are imported from an external source. When operating WSJT-X, I get tons of QSOs, but no easy way to flag them for LOTW export. No one wants to click each one and set a flag when you have hundreds of QSOs from a recent contest...

So, could the developers please consider an option as to what to flag for UDP (and TCP) imports, just like the user interface does? Maybe some program INI setting/option ?

Thanks and 73s
Steve VE3RX

--

73 de aki ja1nlx


Flagging UDP imports for LOTW export?

Steve VE3RX
 

When one normally imports an ADIF file, it gives options to flag them for export to LOTW, eQSL, etc...  However, there is no such option with UDP packets that are imported from an external source. When operating WSJT-X, I get tons of QSOs, but no easy way to flag them for LOTW export. No one wants to click each one and set a flag when you have hundreds of QSOs from a recent contest...

So, could the developers please consider an option as to what to flag for UDP (and TCP) imports, just like the user interface does? Maybe some program INI setting/option ?

Thanks and 73s
Steve VE3RX


Re: bit help L32 and Icom IC7300

Radhames Bonilla
 


Hi all.
I want deeply thank to Aki, JA1NLX, for his very value and great help, for get L32 could be work with my Icom IC7300. Othetwise, I will glad someone that work with N1MM help me get best setting. It is does not recognize my radio after I have testing different baud rates in my Icom 7300 and the com port 3. Feel free e mail me directly to: hi3b@.... Radhames (Rada), HI3B


Re: Switching between more than 2 radios

n5kd
 

I like to simplify stuff, so once I had the multiple configurations working, so I wrote a batch file to enable selection of those config files.
It also ensure all programs associated with L32 are dead before restarting.

 

Then my desktop icon points to my batch file instead of Logger32.exe

 

It looks like this. Works on win7 and win10 at least.

 

73’ Pete, N5KD.

 

 

 

taskkill /F /IM Logger32.exe

taskkill /F /IM ve7cc.exe

taskkill /F /IM L32LogSynch

taskkill /F /IM CheckCallPartial.exe

 

@echo off

cls

 

:RADIO

ECHO Select your option

 

:START

echo.

ECHO 1. Local K3S or Remote K3

ECHO 2. Local K3 or IC7300

ECHO 3. IC7300 to SDRuno bridge

echo.

ECHO 4. Exit

echo.

set choice=

set /p choice=Enter the number to select.

if not '%choice%'=='' set choice=%choice:~0,1%

if '%choice%'=='1' goto CONFIG1

if '%choice%'=='2' goto CONFIG2

if '%choice%'=='3' goto CONFIG3

 

 

if '%choice%'=='4' goto END

 

ECHO

cls

ECHO "%choice%" is not valid please try again

goto START

 

:CONFIG1

cd C:\Logger32\

start Logger32.exe

goto END

 

:CONFIG2

cd C:\logger32

start Logger32.exe CONFIG2

goto END

 

:CONFIG3

cd C:\logger32

start Logger32.exe CONFIG3

goto END

 

:END

exit

 

 

 

 

 

 

Sent from Mail for Windows 10

 

From: John, G4DRS via Groups.Io
Sent: Tuesday, July 17, 2018 21:37
To: hamlogger@groups.io
Subject: [hamlogger] Switching between more than 2 radios

 

Hello,
I am fortunate enough to have 4 HF radios, each of which I connect to Logger32 at times.
I tend to leave Radio 1 set as is and change the settings of radio 2 to whichever of the other 3 I wish to use at the time.
I use a YCCC SO2R+ box, which handles the distribution of mic, key, receive audio and PTT between up to 4 radios.

My question is, am I missing a trick? Is there a way to somehow save the Logger32 settings for Radio 1 and Radio 2 so that I can recall them as and when I want to, rather than adjusting settings in Setup, Radio, Radio 2 piecemeal each time?

I suspect there is probably a nifty way to accomplish this, but that I just haven't worked it out yet.

Any suggestions welcomed.

Cheers,

John
G4DRS

 


Re: Switching between more than 2 radios

Jim Hargrave
 

John,

Logger32 supports 2 radios.

Very simple solution. Establish 2 Logger32.ini files. Configure 1 for your two most used radios.

Configure the alternate for the other 2 radios.

 

 

Jim – w5ifp-AT-gvtc DOT com

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of John, G4DRS via Groups.Io
Sent: Tuesday, July 17, 2018 4:37 PM
To: hamlogger@groups.io
Subject: [hamlogger] Switching between more than 2 radios

 

Hello,
I am fortunate enough to have 4 HF radios, each of which I connect to Logger32 at times.
I tend to leave Radio 1 set as is and change the settings of radio 2 to whichever of the other 3 I wish to use at the time.
I use a YCCC SO2R+ box, which handles the distribution of mic, key, receive audio and PTT between up to 4 radios.

My question is, am I missing a trick? Is there a way to somehow save the Logger32 settings for Radio 1 and Radio 2 so that I can recall them as and when I want to, rather than adjusting settings in Setup, Radio, Radio 2 piecemeal each time?

I suspect there is probably a nifty way to accomplish this, but that I just haven't worked it out yet.

Any suggestions welcomed.

Cheers,

John
G4DRS


Re: Switching between more than 2 radios

John Munton - G7SSE <JOHNG7SSE@...>
 

John

Check the Help File, in the installation section, regarding setting up a second Logger32 ini (config) file.

You could set up three or four for different radio combinations, and even different screen layouts etc.

Only downside is you have to close and restart Logger32 to change to one of the other configurations.

Might be worth a look though.

John
G7SSE


------ Original Message ------
From: "John, G4DRS via Groups.Io" <g4drs@...>
Sent: 17/07/2018 22:37:09
Subject: [hamlogger] Switching between more than 2 radios

Hello,
I am fortunate enough to have 4 HF radios, each of which I connect to Logger32 at times.
I tend to leave Radio 1 set as is and change the settings of radio 2 to whichever of the other 3 I wish to use at the time.
I use a YCCC SO2R+ box, which handles the distribution of mic, key, receive audio and PTT between up to 4 radios.

My question is, am I missing a trick? Is there a way to somehow save the Logger32 settings for Radio 1 and Radio 2 so that I can recall them as and when I want to, rather than adjusting settings in Setup, Radio, Radio 2 piecemeal each time?

I suspect there is probably a nifty way to accomplish this, but that I just haven't worked it out yet.

Any suggestions welcomed.

Cheers,

John
G4DRS


Switching between more than 2 radios

John, G4DRS
 

Hello,
I am fortunate enough to have 4 HF radios, each of which I connect to Logger32 at times.
I tend to leave Radio 1 set as is and change the settings of radio 2 to whichever of the other 3 I wish to use at the time.
I use a YCCC SO2R+ box, which handles the distribution of mic, key, receive audio and PTT between up to 4 radios.

My question is, am I missing a trick? Is there a way to somehow save the Logger32 settings for Radio 1 and Radio 2 so that I can recall them as and when I want to, rather than adjusting settings in Setup, Radio, Radio 2 piecemeal each time?

I suspect there is probably a nifty way to accomplish this, but that I just haven't worked it out yet.

Any suggestions welcomed.

Cheers,

John
G4DRS


Re: bit help

Dave Colliau
 

The best way to run wsjt-x and jtdx is to use the remote port on the 7300 for cat and keying and use the usb port for the on board sound card . If you actually got 2 ports off the usb cable like the 7610 then you wouldnt need the remote connection.

73

Dave N8DC


On July 17, 2018 at 8:43 AM Jim Hargrave <w5ifp@...> wrote:

Hi  Radhames,

I am not familiar with the IC-7300. If you would download the latest Logger32 Help file, you should find adequate setup information. Perhaps Aki, JA1NLX can offer more specific solution to your problem.

 

 

Jim – w5ifp-AT-gvtc DOT com

 

From: HI3B Radhames [mailto:hi3b@...]
Sent: Friday, July 6, 2018 2:23 PM
To: w5ifp@...
Subject: bit help

 

Hi

 

W5IFP USA flag USA

JIMMIE R HARGRAVE
493 SHEPHERDS RANCH RD
BULVERDE, TX 78163
USA

 

 

Jim:

I just read the text copied below, where you talk about Logger32 and JTDX / WSJT-X for get work digital modes.

Think you have plenty experience with both, ICOM IC 7300 and L32, and maybe you could help to similar setting.

I will appreciate it very much...Maybe via TeamViewr.

Com 7 is open, but CAT function does not work.

Let me know anything.

73,

Radhames, HI3B.

//

 

 

 

 

Date    

JTDX / WSJT interface with Logger32

 

 Jim Hargrave

May 5   #74171  

 

Bob / K4CY has added enhancements to the Logger32 interface with these JT digital programs.

We could use a few volunteers to test and critique these changes.

The Logger32 Beta version requires JTDX version 18.1.85_4  and/or WSJT-X version 1.9.0-rc4.

 

If you are a regular operator of JT modes and would be willing to test the changes, please respond by e-mail direct to:  w5ifp@....

 

Jim – w5ifp@...

 


 

 


Re: bit help

Jim Hargrave
 

Hi  Radhames,

I am not familiar with the IC-7300. If you would download the latest Logger32 Help file, you should find adequate setup information. Perhaps Aki, JA1NLX can offer more specific solution to your problem.

 

 

Jim – w5ifp-AT-gvtc DOT com

 

From: HI3B Radhames [mailto:hi3b@...]
Sent: Friday, July 6, 2018 2:23 PM
To: w5ifp@...
Subject: bit help

 

Hi

 

W5IFP USA flag USA

JIMMIE R HARGRAVE
493 SHEPHERDS RANCH RD
BULVERDE, TX 78163
USA

 

 

Jim:

I just read the text copied below, where you talk about Logger32 and JTDX / WSJT-X for get work digital modes.

Think you have plenty experience with both, ICOM IC 7300 and L32, and maybe you could help to similar setting.

I will appreciate it very much...Maybe via TeamViewr.

Com 7 is open, but CAT function does not work.

Let me know anything.

73,

Radhames, HI3B.

//

 

 

 

 

JTDX / WSJT interface with Logger32

 Jim Hargrave

May 5   

 

Bob / K4CY has added enhancements to the Logger32 interface with these JT digital programs.

We could use a few volunteers to test and critique these changes.

The Logger32 Beta version requires JTDX version 18.1.85_4  and/or WSJT-X version 1.9.0-rc4.

 

If you are a regular operator of JT modes and would be willing to test the changes, please respond by e-mail direct to:  w5ifp@....

 

Jim – w5ifp@...

 


Re: Capital letters QTH Field

Gerald Boutin
 

On Fri, Jul 13, 2018 at 08:41 AM, Gary Hinson wrote:

That depends on the entry, Jan.  It is by exception. 

 

Here’s an example:

 

 

WN3LIF emailed me about this QSO, signing his email as “WT”.  To put that into Logger32 as two capitals is more trouble than it’s worth.    

 

The ability for the user manually to overrule automatic case changes (and other automated formatting) is commonplace in other programs: Logger32 makes it awkward by requiring us to turn off the automation, make the change, then turn on the automation again. 

 

Without finding and temporarily deselecting the “Name field in proper case” option, I’d prefer to click the “Wt” entry in my log, change it to “WT”, and save it like that, please.

 

73

Gary  ZL2iFB

 

 

 

My preference is to turn off all of the automatic formatting and leave it off. It works great. I get what I type and I can edit things as I like.
 
--
Gerald, VE1DT


Re: Capital letters QTH Field

Gary Hinson
 

That depends on the entry, Jan.  It is by exception. 

 

Here’s an example:

 

 

WN3LIF emailed me about this QSO, signing his email as “WT”.  To put that into Logger32 as two capitals is more trouble than it’s worth.    

 

The ability for the user manually to overrule automatic case changes (and other automated formatting) is commonplace in other programs: Logger32 makes it awkward by requiring us to turn off the automation, make the change, then turn on the automation again. 

 

Without finding and temporarily deselecting the “Name field in proper case” option, I’d prefer to click the “Wt” entry in my log, change it to “WT”, and save it like that, please.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jan
Sent: Thursday, 12 July 2018 10:34 p.m.
To: hamlogger@groups.io
Subject: Re: [hamlogger] Capital letters QTH Field

 

Hy Gary

What is the purpose of this editing?

73
Jan
PA4JJ

Op 12-7-2018 om 11:29 schreef Gary Hinson:

Hi Aki,

 

If you get the chance to talk to Bob about this, it would be nice if L32 would let us manually edit an existing log entry WITHOUT applying the automatic case-correction.

 

So, for example, we might enter “ft. lauderdale” or whatever in the QTH field as we log a QSO and have Logger32 automatically “correct” it to read “Ft. Lauderdale” (nice, thanks!) … but later, if we so choose, we can edit it to read, say “FT. Lauderdale” or “fort Lauderdale” or whatever without having to mess around with unsetting and later re-setting the capitalization rules.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Thursday, 12 July 2018 5:58 p.m.
To: hamlogger@groups.io
Subject: Re: [hamlogger] Capital letters QTH Field

 

Dino

It is very simple.

1. Right click on Logbook entry window.

2. Click Setup.

3. Uncheck "QTH field in proper case"

4. While holding Shift key type "arrl"  "ARRL" is written there.

73

 

On 2018/07/12 14:10, Dino wrote:

Hello!
Is there any option to write in Capital letters
in QTH Field, Logbook. It would bo good for
abreviations, like ARRL, RSGB but without spacebar.
If I write ARRL now I see Arrl. It can be writen with
spacebar A R R L, but if you have more then one
it looks silly.
73 Dino, 9a2no




 

--


73 de aki ja1nlx



-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: Capital letters QTH Field

Jan
 

Hy Gary

What is the purpose of this editing?

73
Jan
PA4JJ

Op 12-7-2018 om 11:29 schreef Gary Hinson:

Hi Aki,

 

If you get the chance to talk to Bob about this, it would be nice if L32 would let us manually edit an existing log entry WITHOUT applying the automatic case-correction.

 

So, for example, we might enter “ft. lauderdale” or whatever in the QTH field as we log a QSO and have Logger32 automatically “correct” it to read “Ft. Lauderdale” (nice, thanks!) … but later, if we so choose, we can edit it to read, say “FT. Lauderdale” or “fort Lauderdale” or whatever without having to mess around with unsetting and later re-setting the capitalization rules.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Thursday, 12 July 2018 5:58 p.m.
To: hamlogger@groups.io
Subject: Re: [hamlogger] Capital letters QTH Field

 

Dino

It is very simple.

1. Right click on Logbook entry window.

2. Click Setup.

3. Uncheck "QTH field in proper case"

4. While holding Shift key type "arrl"  "ARRL" is written there.

73

 

On 2018/07/12 14:10, Dino wrote:

Hello!
Is there any option to write in Capital letters
in QTH Field, Logbook. It would bo good for
abreviations, like ARRL, RSGB but without spacebar.
If I write ARRL now I see Arrl. It can be writen with
spacebar A R R L, but if you have more then one
it looks silly.
73 Dino, 9a2no



 

--

73 de aki ja1nlx


-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: Capital letters QTH Field

Gary Hinson
 

Hi Aki,

 

If you get the chance to talk to Bob about this, it would be nice if L32 would let us manually edit an existing log entry WITHOUT applying the automatic case-correction.

 

So, for example, we might enter “ft. lauderdale” or whatever in the QTH field as we log a QSO and have Logger32 automatically “correct” it to read “Ft. Lauderdale” (nice, thanks!) … but later, if we so choose, we can edit it to read, say “FT. Lauderdale” or “fort Lauderdale” or whatever without having to mess around with unsetting and later re-setting the capitalization rules.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Thursday, 12 July 2018 5:58 p.m.
To: hamlogger@groups.io
Subject: Re: [hamlogger] Capital letters QTH Field

 

Dino

It is very simple.

1. Right click on Logbook entry window.

2. Click Setup.

3. Uncheck "QTH field in proper case"

4. While holding Shift key type "arrl"  "ARRL" is written there.

73

 

On 2018/07/12 14:10, Dino wrote:

Hello!
Is there any option to write in Capital letters
in QTH Field, Logbook. It would bo good for
abreviations, like ARRL, RSGB but without spacebar.
If I write ARRL now I see Arrl. It can be writen with
spacebar A R R L, but if you have more then one
it looks silly.
73 Dino, 9a2no



 

--

73 de aki ja1nlx


Re: Capital letters QTH Field

Dino
 

Hello!
Thanks for answer.
To uncheck QTH field is possible only in Operator window but it works.

73 Dino

On 12.07.18. 07:58, ja1nlx wrote:
Dino

It is very simple.

1. Right click on Logbook entry window.

2. Click Setup.

3. Uncheck "QTH field in proper case"

4. While holding Shift key type "arrl"  "ARRL" is written there.

73


On 2018/07/12 14:10, Dino wrote:
Hello!
Is there any option to write in Capital letters
in QTH Field, Logbook. It would bo good for
abreviations, like ARRL, RSGB but without spacebar.
If I write ARRL now I see Arrl. It can be writen with
spacebar A R R L, but if you have more then one
it looks silly.
73 Dino, 9a2no



7621 - 7640 of 82051