HomeSoftware & Software SupportL32Lookups for Logger32

Comments

L32Lookups for Logger32 — 129 Comments

  1. Graham..
    I can’t right now but can after 7pm my time. email me your teamviewer login and password to n2amg@n2amg.com 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.
    73,
    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

    ERROR DETAILS

    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 **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    —————————————-
    L32Lookups
    Assembly Version: 1.0.0.5
    Win32 Version: 1.0.0.5
    CodeBase: file:///C:/L32Lookups/L32Lookups.exe
    —————————————-
    Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    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
    —————————————-
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Drawing
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Configuration
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Xml
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Data
    Assembly Version: 4.0.0.0
    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
    —————————————-
    System.Core
    Assembly Version: 4.0.0.0
    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 system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    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

  9. Hi Rick,

    I just installed L32Lookups in my Logger32 directory and went to Setup Internet callsign lookup and setup C:\Logger32\L32Lookups.exe and click start.

    When I do the callsign lookup, QRX – doing Internet lookup appears in the Name . What have I not done?

    73 Don W4BBT

  10. I was getting that same response Don. I just now did a new reinstall gave myself admin rights to everything and now when I do a look up, the web page opens, it auto logs me in, it looks up the call sign, great!! but the little screen will not populate. It says, “yes master, I searching” strange!!

  11. Up Date, the admin rights for the Logger32 folder did not stay applied. I went back through all of the folders involved and made sure I had admin rights to those folders. Everything works just as it is suppose to. Sorry for the above knee jerk comment. Bob

  12. Now I am getting the little screen not populated and it says “Yes master, I’m looking … I checked advanced properties for the Logger32.exe shortcut and it has the Run as Administrator box checked. Here is the path C:\Logger32\L32Lookups.exe L32Lookups.ini is also in the C:\Logger32 folder. Don

  13. I moved the new L32Lookups.exe file (dated Aug. 3, 2017) to C:\Logger32 folder and it is NOW WORKING. Thanks for your help. Don

  14. I just set L32looks up on Window 10. Is QRZ page suppose to come up at the same time as the lookup wimdow. Is there a way not to have it load up an just have the lookup window onlu

  15. The QRZ window does open unless the user minimizes the window while it is open..
    When the window is displaying the last call you looked up just minimize the window. From then on until you open the window it will open minimized each time it is loaded.

    73 Rick N2AMG

  16. Hi Rick. ZS6RF , Leon here. My Logger is working 100% since the new reload. I had my friend, ZS6BAF’s Swisslog for Dos database converted to .ADIF and installed logger 32, did the latest upgrade and I can not get the Lookup to work. When I open Logger and Click on the QRZ lookuo icon in Logger32 toolbar, it changes from blue to transparent and does not open the box. I can not access it to setup QRZLookup. So I can’t put in the type of lookup and the password. Also, I can’t click on Toolbox to type in the URL for QRZLookuup.exe as there is no box! . But when I type in the callsign. the magnifying glass appears and I can ope QRZ!

  17. Hi.

    I’ve done everything I had to but when I open Logger32 and press on the QRZ Lookup blue icon on Logger to set up the toolbox, the blue icon disappears and nothing happens!

  18. Andreas..
    It sounds like the lookup window has been hidden off the screen..
    In Logger32 Click on the View top menu and then select Find Lost Windows.
    You should be able to find the window that way. You are looking for the Internet Lookup Window

    73 Rick N2AMG

  19. Hi Leon..
    Sorry for not answering sooner been busy..
    As I said to Andreas above it sounds like the Internet Lookup Window is hidden off the screen. You need to use the same as I described above. When you do a lookup and the lookup opens you can click on setup and set the lookup type and password from there. Or you can open the lookup directly and open the lookup that way to set it up.

    Also one other important thing is if you are still using QRZLookup.exe you are using a very outdated program. About a year ago I stopped working on that lookup application. The new program available on my website is now called L32Lookups.exe. The QRZLookup.exe no longer works on some of the Windows 10 flavors as the controls I used are no longer supported.

    73 Rick N2AMG

  20. Hi Peter.
    Thanks so much. I feel like such a fool. I know all about lost windows, but never associated it with QRZLookup! I didn’t realize that the lookup was included in the Lost windows. Everything working fine. Thanks a lot

    73 Leon Dalziel ZS6RF

  21. Got this up and running but, it doesn’t populate/put the info into logger32. Is this normal or did I do something wrong as usual?

  22. Recently started getting Microsoft.NET Framework errors upon qrz.com XML lookup of a callsign entry. Using atest Logger 32 3.50.366 and Windows 10.

    “Conversion from string “08/13/18 14:32.53″ to type ‘Date’ is not valid.”

    Let me know if you need the full debug info.

    73 Gary K2GW

  23. Gary..
    In the directory where the lookup is installed there should be a file called L32LookupsDebugLog.txt please attach that file to an email and send it to rellison@twcny.rr.com
    This way I hopefully can see where this is taking place..

    73 Rick n2AMG

  24. Rick:

    I sent you the file last week but may have solved it.

    I don’t think your code likes it if someone sets there Windows system date format to that other of the default. Mine was at DD-MMM-YY instead of the default MM/DD/YYYY Changing it back tot he default may have fixed it.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.