Date   
Receive typing in CW

Vytenis LY2KZ
 

With FOC members active on the air, I found that I have troubles to keep longer CW conversations receiving directly to the head. For me, best is typing while receiving (and I have no idea what is being sent) and reading right after receiving finishes. So far I could not arrange Logger32 so, that this method was possible. At least not simply enough. Any ideas how to setup L32? Any integrated micro notepad?

Thank you

Vytenis
LY2KZ|

Re: ClubLog Upload JA1NLX Not Working

Clark WU4B
 

Aki, 

This is frustrating, and I really appreciate your patience as I try to sort this out.

I am running Windows 10 Home, Version 1803 (installed 5/15/2018).  That was easy to find.
Determining which version of netFramework is more difficult.  I used to be very conversant with Windows 7 in finding out various revision levels of the software, but not so in W10.  The Windows website indicates that netFramework 4.7.1 is included in the last big W10 update, and while I can find the netFramework folder/programs/files, determining the version eludes me for the moment.  Where can I find rev of netFramework?  Or do you recommend installing 4.6.2 (cannot find 4.6.1 on the Microsoft website)?  

Here are the details of the Unexpected exception error:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.
 
************** Exception Text **************
System.IO.EndOfStreamException: Input past end of file.
   at Microsoft.VisualBasic.FileSystem.LineInput(Int32 FileNumber)
   at ClubLogUpload.frmMain.LoggedQSO()
   at ClubLogUpload.frmMain.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.3101.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
ClubLogUpload
    Assembly Version: 3.0.8.0
    Win32 Version: 3.0.8.0
    CodeBase: file:///C:/Logger32/ClubLogUpload.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.7.3056.0 built by: NET472REL1
    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.3056.0 built by: NET472REL1
    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.3101.0 built by: NET472REL1LAST_B
    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.3056.0 built by: NET472REL1
    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.3056.0 built by: NET472REL1
    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.3056.0 built by: NET472REL1
    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.3056.0 built by: NET472REL1
    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.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.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.

73, 




Re: database corruption issues

John Pink
 

Paul,
I suggest that you run an aggressive hard disk checker to see whether there is an issue there.

Also take a look at the system log on your machine - it will show any MB problems

John - G8MM

----Original Message----
From: paulzl4tt@...
Date: 22/05/2018 08:50:01
To: <hamlogger@groups.io>
Subj: Re: [hamlogger] database corruption issues

Thanks Aki & Jacek.

Took a bit of finding as there were no corrupted Qs anywhere near the 56,000 mark where the rebuild failed. I did notice that the last station I logged before the failure was also showing as QSO #1 along with the real QSO #1. It also appeared as QSO #38621 along with the correct #38621 and QSO #126590. Only the latter was correct. I deleted the specious #1 and they all disappeared, even the correct one!

I corrected the ADIF and rebuilt. All seems happy in the world now!

Much appreciate the help guys.

Regards,

Paul

On 21-May-18 21:35, akira yoshida wrote:

Paul

maybe Logbook database is broken somewhere around the record 56000.

Exported adif has something wrong as well.

Repeat partial import.

For example 0 to 50000, 60000 to 120000, 50000 to 55000 etc.

73 de aki  ja1nlx


On 2018/05/21 18:22, Paul Ormandy wrote:
Hi all,

Am having a major problem with L32. Am using latest version and all was 
working well when switched off last night. This morning it threw  a 
message "File error: VIS_BAD_DATASET_NUMBER" so I clicked OK and next 
message was  "error opening a statistics file. Recalculate your 
statistics". Followed by "Open a new logbook or a valid one". I tried 
opening the existing logbook and then did a stats recalc only to get two 
VIS_DISK_ERROR messages, one for LOGBOOK32.Year and one for LOGBOOK32. 
Extension.

So I created a new Logbook, then imported the ADIF of 120,000+ QSOs. 
However after importing about 56000 entries, the VIS_DISK_ERROR messages 
have come back.

Do I need to do a clean install of Logger32 or is there some means of 
fixing the above??

Regards,

Paul

-- 
Paul Ormandy
ZL4TT

--

73 de aki ja1nlx


-- 
ZL4TT


Re: database corruption issues

Paul Ormandy
 

Thanks Aki & Jacek.

Took a bit of finding as there were no corrupted Qs anywhere near the 56,000 mark where the rebuild failed. I did notice that the last station I logged before the failure was also showing as QSO #1 along with the real QSO #1. It also appeared as QSO #38621 along with the correct #38621 and QSO #126590. Only the latter was correct. I deleted the specious #1 and they all disappeared, even the correct one!

I corrected the ADIF and rebuilt. All seems happy in the world now!

Much appreciate the help guys.

Regards,

Paul

On 21-May-18 21:35, akira yoshida wrote:

Paul

maybe Logbook database is broken somewhere around the record 56000.

Exported adif has something wrong as well.

Repeat partial import.

For example 0 to 50000, 60000 to 120000, 50000 to 55000 etc.

73 de aki  ja1nlx


On 2018/05/21 18:22, Paul Ormandy wrote:
Hi all,

Am having a major problem with L32. Am using latest version and all was 
working well when switched off last night. This morning it threw  a 
message "File error: VIS_BAD_DATASET_NUMBER" so I clicked OK and next 
message was  "error opening a statistics file. Recalculate your 
statistics". Followed by "Open a new logbook or a valid one". I tried 
opening the existing logbook and then did a stats recalc only to get two 
VIS_DISK_ERROR messages, one for LOGBOOK32.Year and one for LOGBOOK32. 
Extension.

So I created a new Logbook, then imported the ADIF of 120,000+ QSOs. 
However after importing about 56000 entries, the VIS_DISK_ERROR messages 
have come back.

Do I need to do a clean install of Logger32 or is there some means of 
fixing the above??

Regards,

Paul

-- 
Paul Ormandy
ZL4TT

--

73 de aki ja1nlx


-- 
ZL4TT

Re: ClubLog Upload JA1NLX Not Working

akira yoshida <ayoshida@...>
 

Clark

What is your OS ?

What is netFrameWork version ?

I can not duplicate your problem under Windows 10 1803 and netFrameWork 4.6.1.

73


On 2018/05/22 10:26, Clark WU4B wrote:
Aki,

I just returned from a 6 day trip.  Tried the new update but still get the Windows netFramework unhandled exception.  

It must be a configuration setting on my end that I cannot see--yet.  

--

73 de aki ja1nlx

Re: ClubLog Upload JA1NLX Not Working

Clark WU4B
 

Aki,

I just returned from a 6 day trip.  Tried the new update but still get the Windows netFramework unhandled exception.  

It must be a configuration setting on my end that I cannot see--yet.  

Re: L32LogSync Update

Steph Collas <f5nzy@...>
 

Hello Rick,

Before (when? I don't know) when I was typing a callsign, the first name of the station I worked was update the field Name of my LogBook.

It does not any more!

Do you know why? and How I can resume?

73 de Steph, F5NZY

Re: L32LogSync Update

Rick Ellison
 

Hi Daniel..

Yes that was what it was. I just printed this out so I won’t lose it Now..

I will add this in as I work on the QRZ uploading..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of daniel lavocat
Sent: Monday, May 21, 2018 3:49 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32LogSync Update

 

Hello
@Rick

I don't sure it's me ...

I would like to add the <EOH> on the first line of HRDLogNotUpload File, because HRDLog does not accept a file that does not have a Header :-)

Actually I manually add this Line

FYI : The automatic upload for the new version (V 2.0.4) doesn't works here, but I upload manually and works fine

Thanks Rick


--
Daniel


F6FLU
Daniel Lavocat

F6FLU@...
http://F6FLU.fr

 


F6KOP Team #1277

 


UFT #1277
  

CDXC #1632  

DXCC CW #13586 




21 mai 2018 à 03:49

Let me know if you see any issues with this version. From my point I think
Everything is now working like the old version did. If this is true I will
now start work on the QRZ Upload.

Also one person I think it was an F station wanted something done for
HRDLog. I lost your email could you send what you needed added to the HRDLog
file or something like that..

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick
Ellison
Sent: Sunday, May 20, 2018 9:32 PM
To: hamlogger@groups.io
Subject: [hamlogger] L32LogSync Update

I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG







 

Re: FT8 beta

Jim Hargrave
 

Hi  Steve,

We had a few volunteers and completed the test phase. The results have been incorporated In Logger32 version 3.50.355 autoupdate. A new English help file, version 3.50.355 Beta 2, is available at Logger32.net > Support files.

 

Thanks for your interest.

 

Jim – w5ifp@...

 

>> -----Original Message-----

>> From: Steve Koster [mailto:skoster@...]

>> Sent: Sunday, May 20, 2018 6:32 PM

>> To: Jim Hargrave <w5ifp@...>

>> Subject: FT8 beta

>>

>> Hi Jim... Recently saw on the new IO Group reflector you were

>> looking for FT8 beta testers. Maybe you have enough now but I'm

>> available for that. I currently use JTDX and have been playing in FT8

>> for the past 5 months.

>>

>> +/- 1,000 Q's with 81 countries worked.

>>

>> 73, W6SFK

>>

>> --

>> Best regards,

>>

>> Steve Koster

>> Winery Process Consultant

>> PO Box 990

>> Geyserville, CA 95441

>> P. 707.433.7029

>> C. 707.318.7662

>> skoster@...

 

Re: L32LogSync Update

Carlo, I4HRH
 

All OK Rick.

Thanks

Carlo, I4HRH

Il 21/05/2018 03:32, Rick Ellison ha scritto:
I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG



Re: database corruption issues

Jacek Marczewski
 

Hi Paul,
I had a similar problem during my dxpedition. One record has been corrupted. If you are able to locate its number using partial import then OK, the problem is solved.
But if you have an ADIF backup, it might be easier to edit the ADIF file with a text editor (WordPad) since such a broken record is well visible when you scroll down the screen.
The broken record has another structure than the others. After deleting it, rename the file please (for safety), and then save - everything should work properly.
73 de Jacek SP5EAQ

Re: database corruption issues

akira yoshida <ayoshida@...>
 

Paul

maybe Logbook database is broken somewhere around the record 56000.

Exported adif has something wrong as well.

Repeat partial import.

For example 0 to 50000, 60000 to 120000, 50000 to 55000 etc.

73 de aki  ja1nlx


On 2018/05/21 18:22, Paul Ormandy wrote:
Hi all,

Am having a major problem with L32. Am using latest version and all was 
working well when switched off last night. This morning it threw  a 
message "File error: VIS_BAD_DATASET_NUMBER" so I clicked OK and next 
message was  "error opening a statistics file. Recalculate your 
statistics". Followed by "Open a new logbook or a valid one". I tried 
opening the existing logbook and then did a stats recalc only to get two 
VIS_DISK_ERROR messages, one for LOGBOOK32.Year and one for LOGBOOK32. 
Extension.

So I created a new Logbook, then imported the ADIF of 120,000+ QSOs. 
However after importing about 56000 entries, the VIS_DISK_ERROR messages 
have come back.

Do I need to do a clean install of Logger32 or is there some means of 
fixing the above??

Regards,

Paul

-- 
Paul Ormandy
ZL4TT

--

73 de aki ja1nlx

database corruption issues

Paul Ormandy
 

Hi all,

Am having a major problem with L32. Am using latest version and all was 
working well when switched off last night. This morning it threw  a 
message "File error: VIS_BAD_DATASET_NUMBER" so I clicked OK and next 
message was  "error opening a statistics file. Recalculate your 
statistics". Followed by "Open a new logbook or a valid one". I tried 
opening the existing logbook and then did a stats recalc only to get two 
VIS_DISK_ERROR messages, one for LOGBOOK32.Year and one for LOGBOOK32. 
Extension.

So I created a new Logbook, then imported the ADIF of 120,000+ QSOs. 
However after importing about 56000 entries, the VIS_DISK_ERROR messages 
have come back.

Do I need to do a clean install of Logger32 or is there some means of 
fixing the above??

Regards,

Paul

-- 
Paul Ormandy
ZL4TT

Re: L32LogSync Update

Fred Bourne <g3yjq@...>
 

Hi Rick.

Just updated your L32LogSync files, AVG didn't like it one bit, so I deactivated AVG and install all ok.

System working all ok now.

Thanks for a great program


73 de Fred G3YJQ


On 21/05/2018 02:32, Rick Ellison wrote:
I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG






Virus-free. www.avg.com

Re: L32LogSync Update

daniel lavocat
 

Hello
@Rick

I don't sure it's me ...

I would like to add the <EOH> on the first line of HRDLogNotUpload File, because HRDLog does not accept a file that does not have a Header :-)

Actually I manually add this Line

FYI : The automatic upload for the new version (V 2.0.4) doesn't works here, but I upload manually and works fine

Thanks Rick


--
Daniel

F6FLU
Daniel Lavocat
F6FLU@...
http://F6FLU.fr

F6KOP Team #1277


UFT #1277
  
CDXC #1632   DXCC CW #13586 


21 mai 2018 à 03:49
Let me know if you see any issues with this version. From my point I think
Everything is now working like the old version did. If this is true I will
now start work on the QRZ Upload.

Also one person I think it was an F station wanted something done for
HRDLog. I lost your email could you send what you needed added to the HRDLog
file or something like that..

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick
Ellison
Sent: Sunday, May 20, 2018 9:32 PM
To: hamlogger@groups.io
Subject: [hamlogger] L32LogSync Update

I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG









Re: L32LogSync Update

Rick Ellison
 

Let me know if you see any issues with this version. From my point I think
Everything is now working like the old version did. If this is true I will
now start work on the QRZ Upload.

Also one person I think it was an F station wanted something done for
HRDLog. I lost your email could you send what you needed added to the HRDLog
file or something like that..

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick
Ellison
Sent: Sunday, May 20, 2018 9:32 PM
To: hamlogger@groups.io
Subject: [hamlogger] L32LogSync Update

I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG

L32LogSync Update

Rick Ellison
 

I have just posted an update to L32LogSync. Sometime in the next 24 hours
you should get a notice of it and the program will want to update. On some
systems this should complete ok On other I'm not sure until The new Update
code is on your system. If not you can download the update from here:
http://www.n2amg.com/files/L32LogSyncManualUpdate.zip

Unzip the files into you current install directory overwriting the files
there.

73 Rick N2AMG

Re: Logger32 ver3.50.355 -Help Files, now DXCC Awards window

Mike
 

Ron is correct. I went through the same thing recently and was told to delete the .chi file. It is no longer needed. Did that and Help worked FB.

 

73 N2TBP  Mike

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of w4lde
Sent: Saturday, May 19, 2018 2:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 ver3.50.355 -Help Files, now DXCC Awards window

 

Rich,

I think if my memory is good is:  the need for the chi file was deleted, try moving that file to temp location and try the help function again.  Remember to check the chm file properties and unblock the file if needed.

Have a good weekend

73 de Ron W4LDE


On May 19, 2018, at 9:57 AM, Richard Black via Groups.Io <jrblack99sa@...> wrote:

After downloading and installing the new .chm file, I get an error message that the version does not match that of the .chi file. I don't see the .chi file available at the Logger32 web site. I tried editing the old .chi file with Notepad, but see that it is a binary file. Logger32 freezes when I attempt to access Help.

Suggestions?
--
N0FXQ - Rich


Virus-free. www.avast.com

Re: Logger32 ver3.50.355 -Help Files, now DXCC Awards window

w4lde
 

Rich,
I think if my memory is good is:  the need for the chi file was deleted, try moving that file to temp location and try the help function again.  Remember to check the chm file properties and unblock the file if needed.
Have a good weekend
73 de Ron W4LDE


On May 19, 2018, at 9:57 AM, Richard Black via Groups.Io <jrblack99sa@...> wrote:

After downloading and installing the new .chm file, I get an error message that the version does not match that of the .chi file. I don't see the .chi file available at the Logger32 web site. I tried editing the old .chi file with Notepad, but see that it is a binary file. Logger32 freezes when I attempt to access Help.

Suggestions?
--
N0FXQ - Rich

Re: Logger32 ver3.50.355 -Help Files, now DXCC Awards window

Jan
 

close Logger32
Delete the file
Import a new help file
73
Jan
PA4JJ

Op 19.mei.2018 om 15:57 schreef Richard Black via Groups.Io:
After downloading and installing the new .chm file, I get an error message that the version does not match that of the .chi file. I don't see the .chi file available at the Logger32 web site. I tried editing the old .chi file with Notepad, but see that it is a binary file. Logger32 freezes when I attempt to access Help.

Suggestions?
--
N0FXQ - Rich

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