Date   
Re: UDP

Jim Altman
 

I think he means the interval between the time wsjt and jtdx say ‘log it’ and the time logger32 actually logs it.  It is longer from jtdx, but I always thought it to be of no consequence.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Valery Prodanov
Sent: Thursday, August 8, 2019 11:56 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] UDP

 

in 379 versions Logger32  was all ok

 

чт, 8 авг. 2019 г. в 18:37, Bob <k4cy@...>:

Do you mean the QSO start time is different between WSJT-X and JTDX? You will have to ask the authors of those programs. Logger32 simply uses the start/end in it receives. SeventyThree(s).

On August 8, 2019 at 10:29 AM Valery Prodanov <ur5wca@...> wrote:

QSO from WSJT-X logged on the first second,

but QSO from JTDX logged on a fifth second.

Why?


--

Best regards!
Valery P. Prodanov
UR5WCA
73!



--

Best regards!
Valery P. Prodanov
UR5WCA
73!

Re: UDP

Valery Prodanov
 

in 379 versions Logger32  was all ok

чт, 8 авг. 2019 г. в 18:37, Bob <k4cy@...>:

Do you mean the QSO start time is different between WSJT-X and JTDX? You will have to ask the authors of those programs. Logger32 simply uses the start/end in it receives. SeventyThree(s).

On August 8, 2019 at 10:29 AM Valery Prodanov <ur5wca@...> wrote:

QSO from WSJT-X logged on the first second,

but QSO from JTDX logged on a fifth second.

Why?


--
Best regards!
Valery P. Prodanov
UR5WCA
73!



--
Best regards!
Valery P. Prodanov
UR5WCA
73!

Re: UDP

Bob <k4cy@...>
 

Do you mean the QSO start time is different between WSJT-X and JTDX? You will have to ask the authors of those programs. Logger32 simply uses the start/end in it receives. SeventyThree(s).

On August 8, 2019 at 10:29 AM Valery Prodanov <ur5wca@...> wrote:

QSO from WSJT-X logged on the first second,

but QSO from JTDX logged on a fifth second.

Why?


--
Best regards!
Valery P. Prodanov
UR5WCA
73!

WinXP autopdate

Vytenis LY2KZ
 

Hi guys, I'm looking why program and clublog country call files does not autopudate on Windows XP machine. Although I was able to update program manually, There is no firewall enabled now and there is no antivirus at the moment (don't ask me why - its not my PC)
Should autoupdate work as it is on Win7,8,10... ?

Thank you

Vytenis LY2KZ

UDP

Valery Prodanov
 

QSO from WSJT-X logged on the first second,

but QSO from JTDX logged on a fifth second.

Why?


--
Best regards!
Valery P. Prodanov
UR5WCA
73!

Re: deleated qso

Gerry VE6LB
 

One should remember that L32 offers several log backup options that keep multiple copies of your log automatically.

73, Gerry VE6LB

On 07/08/2019 14:23, Gary Hinson wrote:
Yes. In decreasing order ...

1. Retrieve the QSO details from your backup log, saved prior to "the incident".
2. Retrieve info from LoTW or ClubLog or QRZ log or eQSL log or whatever, uploaded before "the incident".
3. Guess and estimate the details, hoping to get close enough for a confirmation match (if that's what you want).
4. Plead with the counter-party to confirm. Try offering beer or diamonds.
5. Invent time travel. Charge up your dilithium crystals. Get a Delorean.
6. Live and learn, mate, live and learn. Become a backup evangelist, like me and Bob.

73 GL
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ronald Scalise
Sent: 08 August 2019 00:27
To: Hamlogger <hamlogger@groups.io>
Subject: [hamlogger] deleated qso

Is there any way to get a deleted qso back As some dumb ass deleted the wrong one (me) Wa5zfp Ron





--
73, Gerry VE6LB ve6lb@... ve6lb.ve6hams.com

Re: deleated qso

Gary Hinson
 

Yes. In decreasing order ...

1. Retrieve the QSO details from your backup log, saved prior to "the incident".
2. Retrieve info from LoTW or ClubLog or QRZ log or eQSL log or whatever, uploaded before "the incident".
3. Guess and estimate the details, hoping to get close enough for a confirmation match (if that's what you want).
4. Plead with the counter-party to confirm. Try offering beer or diamonds.
5. Invent time travel. Charge up your dilithium crystals. Get a Delorean.
6. Live and learn, mate, live and learn. Become a backup evangelist, like me and Bob.

73 GL
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ronald Scalise
Sent: 08 August 2019 00:27
To: Hamlogger <hamlogger@groups.io>
Subject: [hamlogger] deleated qso

Is there any way to get a deleted qso back As some dumb ass deleted the wrong one (me) Wa5zfp Ron

Re: deleated qso

Bob <k4cy@...>
 

Not really, no backup? Have you maybe exported to to clublog, LoTW or somewhere you can find the information? 73.

On August 7, 2019 at 8:26 AM Ronald Scalise <wa5zfp@...> wrote:


Is there any way to get a deleted qso back
As some dumb ass deleted the wrong one (me)
Wa5zfp Ron


Re: Logger32 and QRZ Lookup Registry Error Running Windows 10

Cliff
 

Thanks all!

73 Cliff WA2TMF 


On Aug 7, 2019, at 7:55 AM, Rick Ellison <rellison@...> wrote:

I am working on this error. It’s happening when it is checking the registry for a certain setting and the setting is not there. By this weekend I will release a new version that corrects this. One good thing is if you hit continue then you will not see this error again until the next time it is loaded. Once it has been loaded and Logger32 takes control of hiding and un-hiding it you will not see the error again..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Tuesday, August 6, 2019 11:55 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 and QRZ Lookup Registry Error Running Windows 10

 

Lucky me, looks like Logger32 escaped the axe on this one. N2AMG (the L32Lookups author) monitors the reflector, he'll jump in here soon enough. But, while you're waiting, after your new install of Logger32, did you allow it to install the updates? You need to be on version 3.50.391. Seventy Three(s).

On August 6, 2019 at 11:42 PM Cliff <clgreen@...> wrote:

Brand new install of Logger32 and QRZlookups in Windows 10.
After placing callsign into log entry window and hitting tab to induce a QRZ lookup a registry error appears at the same time QRZ window appears.

Here is the text of error message

:************** Exception Text **************

System.NullReferenceException: Object reference not set to an instance of an object.

   at L32Lookups.RegistrySettings.Check64bitRegistryValue()

   at L32Lookups.RegistrySettings.Initialize()

   at L32Lookups.wndQRZLookup.wndQRZLookup_Load(Object sender, EventArgs e)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.OnCreateControl()

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WmShowWindow(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at L32Lookups.wndQRZLookup.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B

----------------------------------------

L32Lookups

    Assembly Version: 1.0.0.13

    Win32 Version: 1.0.0.13

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 10.0.0.0

    Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B

----------------------------------------

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Data

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C

----------------------------------------

System.Numerics

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Any help would be appreciated!

Thanks, 
Cliff WA2TMF

 

 


Virus-free. www.avast.com

deleated qso

Ronald Scalise
 

Is there any way to get a deleted qso back
As some dumb ass deleted the wrong one (me)
Wa5zfp Ron

deleated qso

Ronald Scalise
 

Re: Logger32 and QRZ Lookup Registry Error Running Windows 10

Rick Ellison
 

I am working on this error. It’s happening when it is checking the registry for a certain setting and the setting is not there. By this weekend I will release a new version that corrects this. One good thing is if you hit continue then you will not see this error again until the next time it is loaded. Once it has been loaded and Logger32 takes control of hiding and un-hiding it you will not see the error again..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Tuesday, August 6, 2019 11:55 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 and QRZ Lookup Registry Error Running Windows 10

 

Lucky me, looks like Logger32 escaped the axe on this one. N2AMG (the L32Lookups author) monitors the reflector, he'll jump in here soon enough. But, while you're waiting, after your new install of Logger32, did you allow it to install the updates? You need to be on version 3.50.391. Seventy Three(s).

On August 6, 2019 at 11:42 PM Cliff <clgreen@...> wrote:

Brand new install of Logger32 and QRZlookups in Windows 10.
After placing callsign into log entry window and hitting tab to induce a QRZ lookup a registry error appears at the same time QRZ window appears.

Here is the text of error message

:************** Exception Text **************

System.NullReferenceException: Object reference not set to an instance of an object.

   at L32Lookups.RegistrySettings.Check64bitRegistryValue()

   at L32Lookups.RegistrySettings.Initialize()

   at L32Lookups.wndQRZLookup.wndQRZLookup_Load(Object sender, EventArgs e)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.OnCreateControl()

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WmShowWindow(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at L32Lookups.wndQRZLookup.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B

----------------------------------------

L32Lookups

    Assembly Version: 1.0.0.13

    Win32 Version: 1.0.0.13

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 10.0.0.0

    Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B

----------------------------------------

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

System.Data

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C

----------------------------------------

System.Numerics

    Assembly Version: 4.0.0.0

    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Any help would be appreciated!

Thanks, 
Cliff WA2TMF

 

 


Virus-free. www.avast.com

Re: Logger32 and QRZ Lookup Registry Error Running Windows 10

Bob <k4cy@...>
 

Lucky me, looks like Logger32 escaped the axe on this one. N2AMG (the L32Lookups author) monitors the reflector, he'll jump in here soon enough. But, while you're waiting, after your new install of Logger32, did you allow it to install the updates? You need to be on version 3.50.391. Seventy Three(s).

On August 6, 2019 at 11:42 PM Cliff <clgreen@...> wrote:

Brand new install of Logger32 and QRZlookups in Windows 10.
After placing callsign into log entry window and hitting tab to induce a QRZ lookup a registry error appears at the same time QRZ window appears.

Here is the text of error message

:************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at L32Lookups.RegistrySettings.Check64bitRegistryValue()
   at L32Lookups.RegistrySettings.Initialize()
   at L32Lookups.wndQRZLookup.wndQRZLookup_Load(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at L32Lookups.wndQRZLookup.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
 
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
L32Lookups
    Assembly Version: 1.0.0.13
    Win32 Version: 1.0.0.13
    CodeBase: file:///C:/Logger32/L32Lookups.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
 
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
 
For example:
 
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
 
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Any help would be appreciated!

Thanks, 
Cliff WA2TMF
 
 

Logger32 and QRZ Lookup Registry Error Running Windows 10

Cliff
 

Brand new install of Logger32 and QRZlookups in Windows 10.
After placing callsign into log entry window and hitting tab to induce a QRZ lookup a registry error appears at the same time QRZ window appears.

Here is the text of error message

:************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at L32Lookups.RegistrySettings.Check64bitRegistryValue()
   at L32Lookups.RegistrySettings.Initialize()
   at L32Lookups.wndQRZLookup.wndQRZLookup_Load(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at L32Lookups.wndQRZLookup.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
 
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
L32Lookups
    Assembly Version: 1.0.0.13
    Win32 Version: 1.0.0.13
    CodeBase: file:///C:/Logger32/L32Lookups.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
 
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
 
For example:
 
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
 
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Any help would be appreciated!

Thanks, 
Cliff WA2TMF
 
 

Re: SNTP Timeout?

Bob <k4cy@...>
 

Right click on the date/time in  lower status bar, leftmost pane. Click GET ATOMIC CLOCK TIME. You are now looking at the SNTP clock interface. Click SETUP. Try a server address of us.pool.ntp.org or maybe you can find the address of a tier 1 SNTP server somewhere near you. SeventyThree(s).

On August 4, 2019 at 5:20 PM John Owens <jcowens1@...> wrote:

I keep getting this message (SNTP Timeout) with no apparent issue or problem. What is this all about. Nothing in HELP File about it.

John Owens -  N7TK

 



 


 

SNTP Timeout?

John Owens
 

I keep getting this message (SNTP Timeout) with no apparent issue or problem. What is this all about. Nothing in HELP File about it.

John Owens -  N7TK

 


FYI

Bob <k4cy@...>
 

Today my development PC has been the subject to an ongoing determined hacking attempt. Also, several attempts have been made today to penetrate other PC in the house with what looks like ransomware. Other than inconvenience, nothing was touched. Looking back on the events of the day, it is all rather amusing ... Ransomware? What could you possible want from me?


Anyway, it's all quiet now and the alarm bells/sirens/klaxons have stopped. Just a word of caution BACKUP YOUR LOGBOOKS REGULARLY! SeventyThree(s). 

Re: FT testers needed.

NICK K. PLUMIDAKIS
 

I am always in to help as much as I can.

Best 73’s

Nick

SV1VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Hargrave
Sent: Friday, 2 August, 2019 05:43
To: hamlogger@groups.io
Subject: [hamlogger] FT testers needed.

 

The next Auto-update is currently being tested/De-bugged. This version is primarily enhancements to FT4 / FT8 interface with Logger32.

If you frequently operate FT4 / FT8 and would like to help us insure all is working well, please advise by personal message to w5ifp@....

 

Jim – w5ifp-

 

FT testers needed.

Jim Hargrave
 

The next Auto-update is currently being tested/De-bugged. This version is primarily enhancements to FT4 / FT8 interface with Logger32.

If you frequently operate FT4 / FT8 and would like to help us insure all is working well, please advise by personal message to w5ifp@....

 

Jim – w5ifp-

 

Re: FT4 and Cherry-Picking

David Ross
 

Bob, Well that explains it very well.
Do not use highlight gridsquare if not confirmed in Cherry-Picking mode.

Many thanks

David Gi4sna