Menu

#16 .exe will not open

1.0
closed
None
2025-01-28
2025-01-26
No

I downloaded the windows zip file to my downloads folder. I extracted the file and dragged the KB6IBB SWLogger folder to C:\Users\gregh\OneDrive\Documents. I then dragged the SWLog51 to my C: drive When clicking the .exe file in SWLog51 I get the Logger file not found error. I then tried dragging the KB6IBB-SWLogger folder to C:\Users\gregh\Documents, I received the same error message. Those are the only two "documents" locations I know of.

I am using Windows 11 Pro on an HP desktop

Related

Tickets: #16

Discussion

  • Jeff Stillinger

    Jeff Stillinger - 2025-01-27

    First and foremost, ensure you don't have any security software getting in the way.

    It appears that you did not install according to instructions. If you wish to use One Drive, then section 4.3 of the instructions applies. Which first requires a working standard installation to be completed. Either way, One Drive does work, just depends how you configured your system. You can lean about all the One Drive features and configuration option on the Microsoft Knowledge Base so that you don't have to use a non-standard installation.

    The startup sequence is detailed in Section 5 of the instructions. We are going to need a lot more than just " I get the Logger file not found error". Perhaps a screen shot of the message. We need to determine if it's an actual error with the installation or just information regarding a automatic action taken. We don't do anything behind the end users back, so we tell you each time the program takes a automatic action. As stated in the Troubleshooting secion of the instructions, it's very important to read every message carefully.

    Next I will need to look at the configuration file. It's a simple CSV text file, easy to copy/paste in a reply.
    ~\AppData\Roaming\KB6IBB-SWLog5.cfg

    We are specifically looking for this field, and yours should be this for a standard installation:
    ;C:\Users\gregh\Documents\KB6IBB-SWLLogger\;

    or this for a non-standard One Drive installation:
    ;C:\Users\gregh\OneDrive\KB6IBB-SWLLogger\;

     
    • Greg Hemmings

      Greg Hemmings - 2025-01-27

      Hi Jeff!

      I am attaching a screenshot of the locations of KB6IBB-SWLLogger and SWLog51. Also attaching the config file, it appears to be old information. The version listed is not the one I downloaded. I had an older version about a year ago on an older computer. Could that be the problem? Should I delete the config file and reinstall?

      [cid:78dbc836-e81b-44bc-991f-c4729eca0a8a]


      From: tickets@kb6ibbswllogger.p.re.sourceforge.net tickets@kb6ibbswllogger.p.re.sourceforge.net on behalf of Jeff Stillinger kb6ibb@users.sourceforge.net
      Sent: Monday, January 27, 2025 12:06 PM
      To: [kb6ibbswllogger:tickets] 16@tickets.kb6ibbswllogger.p.re.sourceforge.net
      Subject: [kb6ibbswllogger:tickets] #16 .exe will not open

      First and foremost, ensure you don't have any security software getting in the way.

      It appears that you did not install according to instructions. If you wish to use One Drive, then section 4.3 of the instructions applies. Which first requires a working standard installation to be completed. Either way, One Drive does work, just depends how you configured your system. You can lean about all the One Drive features and configuration option on the Microsoft Knowledge Base so that you don't have to use a non-standard installation.

      The startup sequence is detailed in Section 5 of the instructions. We are going to need a lot more than just " I get the Logger file not found error". Perhaps a screen shot of the message. We need to determine if it's an actual error with the installation or just information regarding a automatic action taken. We don't do anything behind the end users back, so we tell you each time the program takes a automatic action. As stated in the Troubleshooting secion of the instructions, it's very important to read every message carefully.

      Next I will need to look at the configuration file. It's a simple CSV text file, easy to copy/paste in a reply.
      ~\AppData\Roaming\KB6IBB-SWLog5.cfg

      We are specifically looking for this field, and yours should be this for a standard installation:
      ;C:\Users\gregh\Documents\KB6IBB-SWLLogger\;

      or this for a non-standard One Drive installation:
      ;C:\Users\gregh\OneDrive\KB6IBB-SWLLogger\;


      [tickets:#16]https://sourceforge.net/p/kb6ibbswllogger/tickets/16/ .exe will not open

      Status: open
      Milestone: 1.0
      Created: Sun Jan 26, 2025 12:13 AM UTC by Greg Hemmings
      Last Updated: Sun Jan 26, 2025 12:13 AM UTC
      Owner: Jeff Stillinger

      I downloaded the windows zip file to my downloads folder. I extracted the file and dragged the KB6IBB SWLogger folder to C:\Users\gregh\OneDrive\Documents. I then dragged the SWLog51 to my C: drive When clicking the .exe file in SWLog51 I get the Logger file not found error. I then tried dragging the KB6IBB-SWLogger folder to C:\Users\gregh\Documents, I received the same error message. Those are the only two "documents" locations I know of.

      I am using Windows 11 Pro on an HP desktop


      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/kb6ibbswllogger/tickets/16/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       

      Related

      Tickets: #16

      • Jeff Stillinger

        Jeff Stillinger - 2025-01-27

        Yep, that old config file would be the problem, it somehow got corrupted. Your database path is off.

        The logger is currently looking for the database in:
        C:\Users\gregh\Downloads\KB6IBB-SWLLogger500-3LTS-Win64\KB6IBB-SWLLogger500-3LTS-Win64\

        Simply edit the ~\AppData\Roaming\KB6IBB-SWLog5.cfg files path field using Notepad and replace it with:
        C:\Users\gregh\Documents\KB6IBB-SWLLogger\

        Be careful not to delete the semi-colon field seperators.

        Other options include deleting the config file. When the logger starts the next time, you will get a informational message telling you it did not find a config file, and a new one will created for you. From there, Edit - > Preferences to fill in all the rest and save once the program successfully starts.

        Version 5.1,0 uses the same databases as older version 5's do. So your logged data from a year ago should still be preserved. However, you will have to update the Shortwave Reference Databases accordingly. Most simple way is to also delete the ~\Documents\KB6IBB-SWLLogger\EiBi-Data5.sqlite file. A new one will be created for you upon start up, then import the EiBi Database.

        Once you are confident you have a fully tested and working configuration, you can proceed with Section 4.3 of the manual for a non-standard installation and move things over to One Drive. Better yet, set One Drive to keep your Documents folder backed up and nothing else need be done.

        ======================================================
        USE THIS OPTION IF YOU ARE NOT WORRIED ABOUT PREVIOUS DATA

        We don't play around in the Windows Registry, so once these files are deleted, everything is gone, gone, gone. Clean start.
        Delete the ~\AppData\Roaming\KB6IBB-SWLog5.cfg file.
        Delete the ~\Documents\KB6IBB-SWLLogger folder and it's contents.
        Delete the binary folder and it's contents from wherever you put it.
        Delete and clean up your Downloads folder so there are no mistakes with versions or old downloads getting the way.
        Download the New Version 5.1.0-0 LTS from source forge.
        Reinstall following instructions.

         
        • Greg Hemmings

          Greg Hemmings - 2025-01-27

          Thank you so much! All should be fine now!🙂

          [signatureImage]


          From: tickets@kb6ibbswllogger.p.re.sourceforge.net tickets@kb6ibbswllogger.p.re.sourceforge.net on behalf of Jeff Stillinger kb6ibb@users.sourceforge.net
          Sent: Monday, January 27, 2025 5:55:39 PM
          To: [kb6ibbswllogger:tickets] 16@tickets.kb6ibbswllogger.p.re.sourceforge.net
          Subject: [kb6ibbswllogger:tickets] Re: #16 .exe will not open

          Yep, that old config file would be the problem, it somehow got corrupted. Your database path is off.

          The logger is currently looking for the database in:
          C:\Users\gregh\Downloads\KB6IBB-SWLLogger500-3LTS-Win64\KB6IBB-SWLLogger500-3LTS-Win64\

          Simply edit the ~\AppData\Roaming\KB6IBB-SWLog5.cfg files path field using Notepad and replace it with:
          C:\Users\gregh\Documents\KB6IBB-SWLLogger\

          Be careful not to delete the semi-colon field seperators.

          Other options include deleting the config file. When the logger starts the next time, you will get a informational message telling you it did not find a config file, and a new one will created for you. From there, Edit - > Preferences to fill in all the rest and save once the program successfully starts.

          Version 5.1,0 uses the same databases as older version 5's do. So your logged data from a year ago should still be preserved. However, you will have to update the Shortwave Reference Databases accordingly. Most simple way is to also delete the ~\Documents\KB6IBB-SWLLogger\EiBi-Data5.sqlite file. A new one will be created for you upon start up, then import the EiBi Database.

          Once you are confident you have a fully tested and working configuration, you can proceed with Section 4.3 of the manual for a non-standard installation and move things over to One Drive. Better yet, set One Drive to keep your Documents folder backed up and nothing else need be done.

          ======================================================
          USE THIS OPTION IF YOU ARE NOT WORRIED ABOUT PREVIOUS DATA

          We don't play around in the Windows Registry, so once these files are deleted, everything is gone, gone, gone. Clean start.
          Delete the ~\AppData\Roaming\KB6IBB-SWLog5.cfg file.
          Delete the ~\Documents\KB6IBB-SWLLogger folder and it's contents.
          Delete the binary folder and it's contents from wherever you put it.
          Delete and clean up your Downloads folder so there are no mistakes with versions or old downloads getting the way.
          Download the New Version 5.1.0-0 LTS from source forge.
          Reinstall following instructions.


          [tickets:#16]https://sourceforge.net/p/kb6ibbswllogger/tickets/16/ .exe will not open

          Status: open
          Milestone: 1.0
          Created: Sun Jan 26, 2025 12:13 AM UTC by Greg Hemmings
          Last Updated: Mon Jan 27, 2025 05:06 PM UTC
          Owner: Jeff Stillinger

          I downloaded the windows zip file to my downloads folder. I extracted the file and dragged the KB6IBB SWLogger folder to C:\Users\gregh\OneDrive\Documents. I then dragged the SWLog51 to my C: drive When clicking the .exe file in SWLog51 I get the Logger file not found error. I then tried dragging the KB6IBB-SWLogger folder to C:\Users\gregh\Documents, I received the same error message. Those are the only two "documents" locations I know of.

          I am using Windows 11 Pro on an HP desktop


          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/kb6ibbswllogger/tickets/16/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           

          Related

          Tickets: #16

  • Jeff Stillinger

    Jeff Stillinger - 2025-01-28
    • status: open --> closed
    • discussion: enabled --> disabled
     
  • Jeff Stillinger

    Jeff Stillinger - 2025-01-28

    Disposition of ticket number 16.

    Ticket closed with the problem resolved. End user had a left over corrupted configuration file from a previous installation. The fail safe built for upgrading versions did work as intended by preserving the previous configuration, however generated an error when it was discovered the left over config file had a corrupted path. Pointing to a non existent directory. Recommendation is to address this issue in the instruction manual so that end users are aware this could possibly be an issue. I was unable to duplicate any process that could have led to the corrupted path in the file using Version 5.1.0. No further code enhancements or modifications are required at this time.

    DE KB6IBB

     
MongoDB Logo MongoDB