HomeSoftware & Software SupportL32Lookups for Logger32


L32Lookups for Logger32 — 109 Comments

  1. Graham..
    I can’t right now but can after 7pm my time. email me your teamviewer login and password to qand I will do it as soon as I can. Also include your QRZ login information so I can set it all up for you..

    73 Rick N2AMG

  2. I am having a problem when using QRZ XML lookup in logger32. It seems that the callsign field is not cleared each time you click on a new DX spot and you wind up with several call signs connected together. I have tried this on a really old version of logger32 3.31 and it works fine. Running version 3.5 and the update that came later both have this issue. Any suggestions ? 73, K4MMX

  3. Hi Craig..
    To me it sounds like you are your an old version of the of the QRZXMLLookup. That software has been replaced by the program at the top of this thread called L32Lookups. Download the full install first and install it and then download the update and unzip that into the directory where you installed the lookup to. You will also need to point to the new lookup in the Logger32 internet lookup window. All of that is explained in the included pdf file. Install that program and update it and then let me know how you have made out.

    73 Rick N2AMG

  4. Hi Rick,
    I want to say THANKS ! It worked ! I thought that I needed to run the XML version since that was the service I was using. I did not realize that the updated version of L32Lookups did that as well. I did everything you said, and now its perfect ! Thanks for all your hard work.
    Craig K4MMX

  5. Hallo Rick,the MAP is ok. In the windows View DX, IOTA Spots and DX Spots the red point for my qth is ok. But in the grayline window this point is anywhere in Kazakhstan. Do you have an explanation?
    73 and merry Xmas
    Hugo, dl2hrh

  6. Are you using the default map for the grayline window? Each window has its won map if you have used a customized map it might not be centered where it should be. If that happens then all of the locations will be off.

    73 Rick N2AMG

  7. Hi Rick
    Just did a new full install of L32 on an XP Machine and everything is working fine except when using L32Lookups I get an unhandled exception error with the following details (see paste below).

    I have tried uninstalling and then using CCleaner to remove any orphan Registry items (usually a couple) before re-installing, but still get the pop-up error message after first use.

    I think I need to delete traces in the registry still, but not sure how to go about it.

    Any ideas?
    Thanks Jeff VE3CV


    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
    at L32Lookups.QRZ.SetRegistrySetting()
    at L32Lookups.QRZ.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 **************
    Assembly Version:
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    Assembly Version:
    Win32 Version:
    CodeBase: file:///C:/L32Lookups/L32Lookups.exe
    Assembly Version:
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    Assembly Version:
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.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 section.
    The application must also be compiled with debugging

    For example:

    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.

  8. Hi Jeff..
    hmm I’ll have to do some digging and see why the Registry setting can’t be set with XP. Give me some time as I am swamped in both N1MM code and other projects I’m working on at the moment.. I will post an update when I get it figured out..

    73 Rick N2AMG

Leave a Reply

Your email address will not be published. Required fields are marked *