Date
1 - 20 of 21
Locked Error pop up
|
Dave Garber <ve3wej@...>
also the files are located in an "appdata" folder hidden from view normally. if you can get to the 'view' tab in windows to change settings, you can make these folder viewable, but be very careful Dave Garber VE3WEJ / VE3IE On Sun, Oct 25, 2020 at 6:47 PM John Sokol <k9jms.fl@...> wrote: Where do I find the file? I have searched the whole computer. |
|
|
|
On 25/10/2020 22:46, John Sokol wrote:
Where do I find the file? I have searched the whole computer.https://wsjtx.groups.io/g/main/message/12981 |
|
|
|
On 25/10/2020 22:46, John Sokol wrote:
Where do I find the file? I have searched the whole computer.https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.2.html#MENUS "Menu->File->Open log directory" https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.2.html#_file_locations |
|
|
|
John K9JMS
Where do I find the file? I have searched the whole computer.
|
|
|
|
Stuart Sheldon
Seems like this bug has been known now for a few days... Just curious
toggle quoted message
Show quoted text
why this has not just been fixed in a .00001 release. It's sure to cause havoc tomorrow as most will delete their logs for Field Day... Stu AG6AG On 6/26/20 10:46, Bob Shaw wrote:
Thank you all for your help! I am back to all things (apparently) |
|
|
|
Bob Shaw <ve3suy@...>
Thank you all for your help! I am back to all things (apparently) working correctly. Bob VA7SU On Fri, Jun 26, 2020 at 10:05 AM ve3ki <ve3iay@...> wrote: Instead of uninstalling WSJT-X and removing all traces of it from your computer before reinstalling, it might be simpler just to check the Menus check box at the far right of the WSJT-X window, just above the Pwr slider. |
|
|
|
Sam Birnbaum
Hi Bob,
See picture where the menu checkbox is.
ADI file should have this line in it
WSJT-X ADIF Export<eoh>
73,
Sam W2JDB
-----Original Message-----
From: Bob Shaw <ve3suy@...> To: main@wsjtx.groups.io Sent: Fri, Jun 26, 2020 1:27 pm Subject: Re: [WSJTX] Error pop up Thank you Bill. Everything above the activities windows (like menu line) is just NOT there! So I can't show the menu bar, and cannot access Files.
Under %LocalAppData%\WSJT-X\ I do have a file wsjtx_log which opened with notepad, is empty. (I cleared this file out hoping the wsjt-x would restore it).
What should an empty .adi log file contain (so that I can simulate it with notepad)?
Bob
On Fri, Jun 26, 2020 at 9:52 AM Bill Somerville <g4wjs@...> wrote:
On 26/06/2020 17:48, Bob Shaw wrote: |
|
|
|
Bob Shaw <ve3suy@...>
Thank you Bill. Everything above the activities windows (like menu line) is just NOT there! So I can't show the menu bar, and cannot access Files. Under %LocalAppData%\WSJT-X\ I do have a file wsjtx_log which opened with notepad, is empty. (I cleared this file out hoping the wsjt-x would restore it). What should an empty .adi log file contain (so that I can simulate it with notepad)? Bob On Fri, Jun 26, 2020 at 9:52 AM Bill Somerville <g4wjs@...> wrote: On 26/06/2020 17:48, Bob Shaw wrote: |
|
|
|
ve3ki
Instead of uninstalling WSJT-X and removing all traces of it from your computer before reinstalling, it might be simpler just to check the Menus check box at the far right of the WSJT-X window, just above the Pwr slider.
toggle quoted message
Show quoted text
73, Rich VE3KI On Fri, Jun 26, 2020 at 12:48 PM, Bob Shaw wrote:
Thanks for your reply Rich. I read and tried this "fix". However, the menus (above the activities windows) no longer appears, and so I cannot click on FILE to open the log directory. I searched with windows explorer and could not find an .adi file anywhere, so I created a directory under wsjtx to no avail. I copied another computer's file there as well with no result. I have removed and reinstalled a couple times with no success. |
|
|
|
On Fri, 26 Jun 2020 09:48:44 -0700
"Bob Shaw" <ve3suy@...> wrote: Best if I can remove ALL traces of wsjtx and then reinstall I believe, but there are still some remnants of wsjtx still there -- enough to indicate a .adi file which is corrupt?No. A completely fresh install of WSJT-X creates a new ADIF log file with the incorrect header. You are running around in circles. Any other suggestions would be appreciated! Bob Carefully read the advice that Bill and others have posted that works around this known bug. 73 -Jim NU0C |
|
|
|
On 26/06/2020 17:48, Bob Shaw wrote:
Thanks for your reply Rich. I read and tried this "fix". However, the menus (above the activities windows) no longer appears, and so I cannot click on FILE to open the log directory. I searched with windows explorer and could not find an .adi file anywhere, so I created a directory under wsjtx to no avail. I copied another computer's file there as well with no result. I have removed and reinstalled a couple times with no success.Hi Bob, if the menu is missing then you have probably unchecked the "Menus" option to the right of the main row of buttons on the WSJT-X main window. The location of the WSJT-X log files is shown in the WSJT-X User Guide: https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.2.html#_file_locations If you are on Windows then the location is %LocalAppData%\WSJT-X\ 73 Bill G4WJS. |
|
|
|
Bob Shaw <ve3suy@...>
Thanks for your reply Rich. I read and tried this "fix". However, the menus (above the activities windows) no longer appears, and so I cannot click on FILE to open the log directory. I searched with windows explorer and could not find an .adi file anywhere, so I created a directory under wsjtx to no avail. I copied another computer's file there as well with no result. I have removed and reinstalled a couple times with no success.
Best if I can remove ALL traces of wsjtx and then reinstall I believe, but there are still some remnants of wsjtx still there -- enough to indicate a .adi file which is corrupt? Any other suggestions would be appreciated! Bob |
|
|
|
Jon Ermels
Thank you very much Rich and all others. 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 04:21:52 PM CDT, ve3ki <ve3iay@...> wrote:
Start WSJT-X. If the error message appears, just click on OK and continue. Use the "File > Open log directory" menu item in WSJT-X to open a file manager window on the log directory. Look for a file called wsjtx_log.adi . Open that file with any text editor - if you are using Windows, Notepad will do. Look at the first line in the file. It should read WSJT-X ADIF Export<eoh> but if the file was created by v2.2.2 the line ends with <eh> instead. If the line ends with <eh>, change it to <eoh>. Save the edited file. 73, Rich VE3KI On Wed, Jun 24, 2020 at 05:11 PM, Jon Ermels wrote:
|
|
|
|
Jon Ermels
I don't have this or part if it in the log directory. I don't have any idea, unless I drug it into the SD card when moving to the main computer to upload to LOtW. WSJT-X ADIF Export<eoh> 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 04:11:51 PM CDT, Jon Ermels via groups.io <n0igu@...> wrote:
I'm just looking in the log file directory. In the root directory maybe? 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 03:56:02 PM CDT, Bill Somerville <g4wjs@...> wrote:
Hi Jon,
there is a known defect in WSJT-X
v2.2.2 that causes it to write an invalid header to a new ADIF log
file. The file is in the WSJT-X log files directory. You can edit
it with any basic text editor, like notepad.exe on Windows.
The header should look like this:
WSJT-X ADIF Export<eoh> You will probably find it has
<eh> instead of <eoh>, make the change and you should
be OK.
73
Bill G4WJS. On 24/06/2020 21:51, Jon Ermels via
groups.io wrote:
|
|
|
|
ve3ki
Start WSJT-X.
toggle quoted message
Show quoted text
If the error message appears, just click on OK and continue. Use the "File > Open log directory" menu item in WSJT-X to open a file manager window on the log directory. Look for a file called wsjtx_log.adi . Open that file with any text editor - if you are using Windows, Notepad will do. Look at the first line in the file. It should read WSJT-X ADIF Export<eoh> but if the file was created by v2.2.2 the line ends with <eh> instead. If the line ends with <eh>, change it to <eoh>. Save the edited file. 73, Rich VE3KI On Wed, Jun 24, 2020 at 05:11 PM, Jon Ermels wrote:
|
|
|
|
Jon Ermels
I'm just looking in the log file directory. In the root directory maybe? 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 03:56:02 PM CDT, Bill Somerville <g4wjs@...> wrote:
Hi Jon,
there is a known defect in WSJT-X
v2.2.2 that causes it to write an invalid header to a new ADIF log
file. The file is in the WSJT-X log files directory. You can edit
it with any basic text editor, like notepad.exe on Windows.
The header should look like this:
WSJT-X ADIF Export<eoh> You will probably find it has
<eh> instead of <eoh>, make the change and you should
be OK.
73
Bill G4WJS. On 24/06/2020 21:51, Jon Ermels via
groups.io wrote:
|
|
|
|
Hi Jon,
there is a known defect in WSJT-X
v2.2.2 that causes it to write an invalid header to a new ADIF log
file. The file is in the WSJT-X log files directory. You can edit
it with any basic text editor, like notepad.exe on Windows.
The header should look like this:
WSJT-X ADIF Export<eoh> You will probably find it has
<eh> instead of <eoh>, make the change and you should
be OK.
73
Bill G4WJS. On 24/06/2020 21:51, Jon Ermels via
groups.io wrote:
|
|
|
|
Jon Ermels
Should be wsjt_log.adi 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 03:51:31 PM CDT, Jon Ermels via groups.io <n0igu@...> wrote:
Pretty new here but I don't see a header marker. Just wsjt.log.adi 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 03:40:52 PM CDT, Bill Somerville <g4wjs@...> wrote:
On 24/06/2020 21:37, Jon Ermels via groups.io wrote: > I have been getting an error window that says "Error Scanning ADIF > Invalid ADIF Header" when I start WSJT-X. It runs OK but what have I > done wrong? I've uninstalled 2.2.2 and gone back to 2.2.1 and it > still does it. Hi Jon, have you started a new ADIF log file with WSJT-X v2.2.2? If so then there is a known defect and you will have to make a small edit to the wsjtx_log.adi file in the WSJT-X log files directory. Change the end of header marker from <eh> to <eoh>. 73 Bill G4WJS. |
|
|
|
Jon Ermels
Pretty new here but I don't see a header marker. Just wsjt.log.adi 73 de NØIGU
Jon
On Wednesday, June 24, 2020, 03:40:52 PM CDT, Bill Somerville <g4wjs@...> wrote:
On 24/06/2020 21:37, Jon Ermels via groups.io wrote: > I have been getting an error window that says "Error Scanning ADIF > Invalid ADIF Header" when I start WSJT-X. It runs OK but what have I > done wrong? I've uninstalled 2.2.2 and gone back to 2.2.1 and it > still does it. Hi Jon, have you started a new ADIF log file with WSJT-X v2.2.2? If so then there is a known defect and you will have to make a small edit to the wsjtx_log.adi file in the WSJT-X log files directory. Change the end of header marker from <eh> to <eoh>. 73 Bill G4WJS. |
|
|
|
On 24/06/2020 21:37, Jon Ermels via groups.io wrote:
I have been getting an error window that says "Error Scanning ADIF Invalid ADIF Header" when I start WSJT-X. It runs OK but what have I done wrong? I've uninstalled 2.2.2 and gone back to 2.2.1 and it still does it.Hi Jon, have you started a new ADIF log file with WSJT-X v2.2.2? If so then there is a known defect and you will have to make a small edit to the wsjtx_log.adi file in the WSJT-X log files directory. Change the end of header marker from <eh> to <eoh>. 73 Bill G4WJS. |
|
|
