Re: flrig v2.0.05 has a problem setting 2 stop bits
suggest you try the latest
development release which was posted this morning at
Note this is NOT a secure URL.? If you allow your browser to
force https you will be transported to another world.
David
toggle quoted message
Show quoted text
Yes, I did click on the save button. There is definitely an
issue with the windows version of FLRIG 2.0.05. FLDIGI does work
with the FT747. It changes frequencies but it also fails with
the init button. I think it fails to initialize because it sends
a wrong opcode to the radio. It sends 0xFA and that opcode does
not exist. I?m guessing what it?s trying to do is to send 0x10
which is to get the status of the radio. But I?m not sure.
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Yes, I did click on the save button. There is definitely an issue with the windows version of FLRIG 2.0.05. FLDIGI does work with the FT747. It changes frequencies but it also fails with the init button. I think it fails to initialize because it sends a wrong opcode to the radio. It sends 0xFA and that opcode does not exist. I?m guessing what it?s trying to do is to send 0x10 which is to get the status of the radio. But I?m not sure.
|
Re: Double-clicking setup.exe does nothing
I use 7-zip all the time...but my action of choice is to
right click the file in the Windows file manager
from the context menu...with options created by installing 7-zip...
...I choose...
Extract to "name_of_zip_file"
That is the fastest for me. Then I rename the resulting dir if I want it renamed...and in this case, I suspect you do.
The other recommendations about fldigi config directory and files is ~exactly~ why I never install any fl_suite program, but always unzip. I have spent far too much time with hams trying to debug the mess they created by installing, removing, etc., unaware that they were contributing to their problems. Then follow the other suggestions of Tobias.
~R~
|
Re: Double-clicking setup.exe does nothing
Bill,
Just like Rich wrote, if setup doesn't run as expected (and provided you have downloaded the correct FLdigi setup file!) it may make more sense to extract (unzip) it directly into the new folder of your choice.
Then you can:
1. First verify that the setup file is complete.
2. See exactly what you put where.
3. Then run the fldigi.exe from your (new) folder and see what happens. Normally, you should be OK now.
Please take a look at the attached screenshot:
If you don't have/use it already, I highly recommend to download the lightweight, versatile and free 7zip archive manager from 'www.7-zip.org'.
With it, you can open the setup file just like an ordinary zip file, which is what I show in the attached screenshot.
Either drag the 'fldigi...setup.exe' onto '7zFM.exe' (see below) or, if you have setup 7zip this way, use the context menu (or right click) in the Explorer and then, with your FLdigi setup file selected, choose 7zip > Open archive.
In 7zip, once you have the setup file opened, first click the 'test' icon to see whether the archive as such is OK. This is *not* a malw./vir. check (!), it simply tests the archive data integrity. 7zip may or may not check and find issues in the file while opening it, so this extra check is useful.
The 7zip File Manager (7zFM.exe) can be setup to display 2 windows side-by-side, as shown here.
There simply select all the program files and folders contained in the setup file and (if you have entered the path of the target folder on the right side, as shown here), click the 'Copy' icon and the files are extracted into your chosen folder. Alternatively, you may also drag the selection into the right window or into a separate explorer window showing the target folder.
Then run FLdigi as usual and all should work as expected. From this point onward, the 7zip window is no longer needed.
Notes:
1. If all looked OK so far but the FLdigi program window still does not open, consult the Windows 'Task Manager' (Ctrl+Shift+Esc) and look for fldigi.exe in the 'Process' tab. If it is visible there (possibly multiple times: sort the list it by name clicking the respective header!), close all these previous instances and run FLdigi from your new folder again.
2. If FLdigi still won't open, you may try and locate existing data and settings from an (old) installation, usually in 'C:\Users\<UserName>\fldigi.files'. If this folder exists, close all fldigi instances (as described in 1.) and rename the 'fldigi.files' folder into something else, e.g. '_BACKUP_fldigi.files' (you may wish to keep it in case you still have useful data there). Then run Fldigi again - now there's no reason why it should fail. FLdigi will recreate the 'fldigi.files' folder with default values. Then copy what you still need from the _BACKUP_ into the new fldigi.files folder and you're all set. Once complete, you can remove the _BACKUP_ folder. If this method did not work either, I'm afraid I don't have an explanation or advice.
3. Should you wonder, no, not every app ('exe') can be opened this way as an archive. But the fldigi setup for Windows is compatible with this operation.
Hope this helps. Good luck!
And please let us know whether (and if so, how) you were successful.
73s
Tobias
.-.-. Am Montag, 16. September 2024 um 05:14:29 MESZ hat Bill Wiltschko <bill@...> Folgendes geschrieben:
I set up a folder on my C:\ drive called FL_APP, saved the fldigi-4.2.05_setup.exe file to that folder, and double-clicked it.? I get a window asking me to login as Administrator, which I do, after which nothing happens.? No dialogs at all, no files saved anywhere.? The same thing happens when I right-click the setup.exe file and "Run as Administrator".?? I haven't seen this (non) behavior with any other setup.exe file I have ever run.? I checked the manual and online messages.? Can anyone help? Bill, KJ6PN
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Can you test WSJT-X-Improved to see if it works with the FT747?
Then we can compare debug logs.
Or if you contact me off-list maybe we can hook up using AnyDesk and do some debugging.
Mike W9MDB
toggle quoted message
Show quoted text
On Monday, September 16, 2024 at 05:13:41 AM CDT, nico-florio@... <nico-florio@...> wrote:
Hi, yes. Changing them makes no difference. I also noticed that it does not detect the FT-747 because it sends an instruction that the radio does not recognize. The instruction is 0xFA.
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Last night I re-installed FLRIG 2.0.05 freshly downloaded from Sourceforge. It installed and controls FLDIGI correctly, to operate an IC7300.
I don't think that the "problem" resides in the two programs themselves. Be sure that -after setting the stop bit 2- you go to the bottom of that screen and choose SAVE or INITIATE.
Also, on the FLDIGI Configure tab there is an option to SAVE SETUP.
73 Bill K2TNO?
On Sun, Sep 15, 2024, 11:14?PM nico-florio via <nico-florio= [email protected]> wrote:
Hi,
?
I?m using flrig v2.0.05 with a Yaesu FT-747 and it doesnt work. Upon further debuggin with a logic analyzer I found out that it does not set 2 stop bits. How can I solve this issue? I?ll attach a trace debug generated by flrig. Thanks!
?
12:50:23.300 : closeRig()
12:50:23.300 : close serial port
12:50:23.378 : clear frequency list
12:50:23.378 : initialize title bar
12:50:23.378 : start tranceiver serial port
12:50:23.532 : I: OpenPort: Open Comm port //./COM7 ; hComm = 988
?
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.547 : I: ConfigurePortA:?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
?
12:50:23.547 :?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
12:50:23.547 : I: SetCommunicationTimeouts:?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
?
12:50:23.547 :?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
12:50:23.563 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : COM7
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 500
? ? RTSCTS ? : 1
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 1
?
?
12:50:23.563 : initialize transceiver
12:50:23.563 : selrig->initialize()
12:50:23.563 : init_rig()
12:50:23.579 : selrig->check()
12:50:23.579 : WriteBuffer: ?00 00 00 01 FA
12:50:23.663 : 1: ReadBuffer [69.07 msec] (0):?
12:50:23.663 : E: ReadBuffer: ReadBuffer FAILED [69.07 msec], read 0 bytes
?
12:50:23.663 : 2: ReadBuffer FAILED [69.07 msec], read 0 bytes
12:50:23.679 : FAILED
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
I can do the testing for the Yaesu FT-80C or the FT-747 because they are almost the same and I have the 80C. I forgot to mention that the issue of the stop bits happens only in the windows version. I have tested the linux version and it does not have that issue. But both versions have the issue that they do not recognize the radio. Do I have to send Dave a message or will he read this messages? Thanks!
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Ok, well hopefully Dave will be able to check the code and find the issue. One of the big challenges is that he does not have any way of actually testing on many of the rigs to verify the code.
toggle quoted message
Show quoted text
Hi, yes. Changing them makes no difference. I also noticed that it does not detect the FT-747 because it sends an instruction that the radio does not recognize. The instruction is 0xFA.
|
Re: Double-clicking setup.exe does nothing
I never install it, because of the way I use it. Installations always result in conflicts with the constant changes I make to my systems. I unzip, and run from there.
I wondered at the choice of FL_APP, because that suggests you are thinking of FL_APPS....for the portable installation.
Sorry to say I don't have a clue about why 4.2.05 would do this.
You should not have to log in as admin.
Did you download from
*** Note http, NOT https !
What Windows version?
I imagine that even if, as I have seen on occasion, the install window winds up behind some other window or minimized, it would still be on the taskbar.
Sorry not much help.
~R~
toggle quoted message
Show quoted text
On 2024-09-15 14:00:, Bill Wiltschko wrote: I set up a folder on my C:\ drive called FL_APP, saved the fldigi-4.2.05_setup.exe file to that folder, and double-clicked it. I get a window asking me to login as Administrator, which I do, after which nothing happens. No dialogs at all, no files saved anywhere. The same thing happens when I right-click the setup.exe file and "Run as Administrator". I haven't seen this (non) behavior with any other setup.exe file I have ever run. I checked the manual and online messages. Can anyone help?
Bill, KJ6PN
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Hi, yes. Changing them makes no difference. I also noticed that it does not detect the FT-747 because it sends an instruction that the radio does not recognize. The instruction is 0xFA.
|
flrig 2.0.05.75 alpha release
Index of /alpha/flrig
Corrected read errors on Windows OS.? See readme.txt for full
list of changes.
The MacOS dmg is a universal build for Sonoma, Intel and Apple
silicon.? I am currently not able to build a dmg for earlier OS
versions.
73, David
W1HKJ
|
Re: flrig v2.0.05 has a problem setting 2 stop bits
Did you have the 2 Stopbits checkbox checked on the Transceiver config page?
toggle quoted message
Show quoted text
Hi,
?
I?m using flrig v2.0.05 with a Yaesu FT-747 and it doesnt work. Upon further debuggin with a logic analyzer I found out that it does not set 2 stop bits. How can I solve this issue? I?ll attach a trace debug generated by flrig. Thanks!
?
12:50:23.300 : closeRig()
12:50:23.300 : close serial port
12:50:23.378 : clear frequency list
12:50:23.378 : initialize title bar
12:50:23.378 : start tranceiver serial port
12:50:23.532 : I: OpenPort: Open Comm port //./COM7 ; hComm = 988
?
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.547 : I: ConfigurePortA:?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
?
12:50:23.547 :?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
12:50:23.547 : I: SetCommunicationTimeouts:?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
?
12:50:23.547 :?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
12:50:23.563 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : COM7
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 500
? ? RTSCTS ? : 1
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 1
?
?
12:50:23.563 : initialize transceiver
12:50:23.563 : selrig->initialize()
12:50:23.563 : init_rig()
12:50:23.579 : selrig->check()
12:50:23.579 : WriteBuffer: ?00 00 00 01 FA
12:50:23.663 : 1: ReadBuffer [69.07 msec] (0):?
12:50:23.663 : E: ReadBuffer: ReadBuffer FAILED [69.07 msec], read 0 bytes
?
12:50:23.663 : 2: ReadBuffer FAILED [69.07 msec], read 0 bytes
12:50:23.679 : FAILED
|
Double-clicking setup.exe does nothing
I set up a folder on my C:\ drive called FL_APP, saved the fldigi-4.2.05_setup.exe file to that folder, and double-clicked it.? I get a window asking me to login as Administrator, which I do, after which nothing happens.? No dialogs at all, no files saved anywhere.? The same thing happens when I right-click the setup.exe file and "Run as Administrator".?? I haven't seen this (non) behavior with any other setup.exe file I have ever run.? I checked the manual and online messages.? Can anyone help?
Bill, KJ6PN
|
flrig v2.0.05 has a problem setting 2 stop bits
Hi,
?
I?m using flrig v2.0.05 with a Yaesu FT-747 and it doesnt work. Upon further debuggin with a logic analyzer I found out that it does not set 2 stop bits. How can I solve this issue? I?ll attach a trace debug generated by flrig. Thanks!
?
12:50:23.300 : closeRig()
12:50:23.300 : close serial port
12:50:23.378 : clear frequency list
12:50:23.378 : initialize title bar
12:50:23.378 : start tranceiver serial port
12:50:23.532 : I: OpenPort: Open Comm port //./COM7 ; hComm = 988
?
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.547 : I: ConfigurePortA:?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
?
12:50:23.547 :?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
12:50:23.547 : I: SetCommunicationTimeouts:?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
?
12:50:23.547 :?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
12:50:23.563 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : COM7
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 500
? ? RTSCTS ? : 1
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 1
?
?
12:50:23.563 : initialize transceiver
12:50:23.563 : selrig->initialize()
12:50:23.563 : init_rig()
12:50:23.579 : selrig->check()
12:50:23.579 : WriteBuffer: ?00 00 00 01 FA
12:50:23.663 : 1: ReadBuffer [69.07 msec] (0):?
12:50:23.663 : E: ReadBuffer: ReadBuffer FAILED [69.07 msec], read 0 bytes
?
12:50:23.663 : 2: ReadBuffer FAILED [69.07 msec], read 0 bytes
12:50:23.679 : FAILED
|
Rich,
To be on the safe side, I just went a step further and submitted the original zip I had forwarded to the FLdigi group today to a renowned online meta-checker which includes M-Soft any many others: it came out 'clear', see attachment. Which is yet another zip containing the screenshots taken on my phone during this malw. check. I hope at least this will make it without hickups. Bu you may repeat it yourself if in any doubt. The website is visible in the 1st few screenshots before I had to scroll down to see the other results.
Sorry, these things are well beyond my horizon - and sphere of influence...
TNX es 73s
Tobias
.-.-. Am Sonntag, 15. September 2024 um 16:34:56 MESZ hat Rich NE1EE <thedustykey@...> Folgendes geschrieben:
On 2024-09-15 10:24:, T? via groups.io wrote:
>Rich,
>I always check any file I attach using the official M-Soft System Endpoint Protecton with updated definitions, so I must assume they are clean.
I assumed they are clean after several non-MS checkers all agreed they are clean. I tried to submit it to MS, but I needed to login, so skipped that step. In retrospect, I don't think it will do any good anyway. Defender would simply add that specific file to its exception list, and prolly not figure out why it thinks there is a virus. But Defender quarantined both files immediately upon receipt for the same virus, so there must be some pattern that Defender is finding...I can't imagine that MS would simply quarantine ANY zip file from email, and then make up a virus name. So, your files are OK by me. I was just letting folks know that W11 has a problem with them, and a dozen other services don't.
~R~
|
On 2024-09-15 10:24:, T? via groups.io wrote: Rich,
I always check any file I attach using the official M-Soft System Endpoint Protecton with updated definitions, so I must assume they are clean. I assumed they are clean after several non-MS checkers all agreed they are clean. I tried to submit it to MS, but I needed to login, so skipped that step. In retrospect, I don't think it will do any good anyway. Defender would simply add that specific file to its exception list, and prolly not figure out why it thinks there is a virus. But Defender quarantined both files immediately upon receipt for the same virus, so there must be some pattern that Defender is finding...I can't imagine that MS would simply quarantine ANY zip file from email, and then make up a virus name. So, your files are OK by me. I was just letting folks know that W11 has a problem with them, and a dozen other services don't. ~R~
|
Rich,
I always check any file I attach using the official M-Soft System Endpoint Protecton with updated definitions, so I must assume they are clean.
The contents are simply 2 FLAC audio files and a png showing the results. Could it be linked to the zip format?
I just don't get it.
If anyone has evidence of a real issue, please let me know!!!
To give it a try, I attach the same png as is, unzipped, to see, if it is the 'culprit'...
73s Tobias
.-.-. Am Sonntag, 15. September 2024 um 15:55:15 MESZ hat Rich NE1EE <thedustykey@...> Folgendes geschrieben:
My Windows 11 has flagged the last 2 zip files as infected with
Trojan:Script/Sabsik.TE.A!ml
I submitted the first to several online virus checkers, and no virus was found.
Makes me wonder what pattern this file contains.
Or maybe just W11 being annoying, as usual.
~R~
On 2024-09-15 09:37:, T? via groups.io wrote:
>In other words, the glitch positions are independent from the frequency or signal pattern!
Yes...we observed that earlier.
>3. While I had initially assumed the glitches may be linked to some sort of signal clipping, in fact they are not, since they do appear at any amplitude
Agrees with earlier observations.
Very nice summary and eval. I havna looked at the zip file contents yet.
73 Rich NE1EE
The Dusty Key
On the banks of the Piscataqua
|
My Windows 11 has flagged the last 2 zip files as infected with Trojan:Script/Sabsik.TE.A!ml I submitted the first to several online virus checkers, and no virus was found. Makes me wonder what pattern this file contains. Or maybe just W11 being annoying, as usual. ~R~ On 2024-09-15 09:37:, T? via groups.io wrote: In other words, the glitch positions are independent from the frequency or signal pattern! Yes...we observed that earlier. 3. While I had initially assumed the glitches may be linked to some sort of signal clipping, in fact they are not, since they do appear at any amplitude Agrees with earlier observations. Very nice summary and eval. I havna looked at the zip file contents yet. 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua
|
Rich, Carl, and All,
Here's yet another bit of information based on a different test run today.
- - - - - -
I created two audio files with (reasonably) 'perfect' sine waves, using Audacity, the 1st one at 100 Hz, the 2nd one at 345 Hz.
The lower frequency was chosen to get a high resolution in the SIG display (and as a straightforward time reference in the SIG display), the second one is intentionally 'odd' to possibly see frequency-dependent effects, if any.
Both files consist of 10 s each of 95%, 50%, 25%, and 12.5% amplitudes to reveal any amplitude-related influences.
They can directly be played back in FLdigi, preferably in Loop Mode.
In the attached zip archive, apart from the two created FLAC files, you'll find a compiled and annoated summary screenshot showing the results of all different conditions vertically stacked.
- - - - - -
NOTABLE RESULTS:
0. Please take a look at the attached summary first, which should be self-explanatory based on the respective annotations, along with the explanations below.
Line-shaped semi-transparent highlights have been added to visualize the equi-distant glitch positions, as described in the result 1. below.
1. To my surprise, the 'glitches' always appear at the exact same spots (time wise, or in 'x' on the screen), and these positions are not at all random: they are equally spaced at 512 pixels, or 64 ms intervals. In other words, the glitch positions are independent from the frequency or signal pattern! These distinct figures (512 and 64), as you may agree, point to a repetitive software issue, possibly at transitions of a repeating loop or the like, used to calculate the dots to draw the signal polygon.
2. In addition, the glitches always point fom the current (correct) amplitude towards the zero line in amplitude. As a conequence, they disappear altogether when (by chance) being close to a zero-crossing within the sine curve.
3. While I had initially assumed the glitches may be linked to some sort of signal clipping, in fact they are not, since they do appear at any amplitude (as long as the glitch positions are far enough from signal zero-crossings).
4. It does not matter whether an external (INPUT / OFF FILE) or a internal (OUTPUT) signal is displayed.
- - - - - -
CONCLUSION:
Based thereon, my assumption is, that, instead of the correct current amplitude value, a zero (0) value is used while drawing the curve at the supposed loop transition or (re-)initialization points.
I hope this little investigation may help the capable 'wizards of code' to find and fix the issue for good.
Thank you.
Best regards
Tobias
.-.-.
2024-09-15 Am Samstag, 14. September 2024 um 22:52:42 MESZ hat Rich NE1EE <thedustykey@...> Folgendes geschrieben:
Thanks for that...nice to get another look at the situation...
On 2024-09-14 15:45:, T? via groups.io wrote:
>So bottom line, I would recommend to ignore the 'signal' trace in the FLdigi Gui and keep using the waterfall, which appears to be ok for all usual intents and purposes.
I disagree with the suggestion to ignore SIG. The glitch should be identified and commented upon in the fldigi docs...or corrected. I find the SIG display very useful, and I recommend anyone continue using it, but with awareness. Now that we've had this discussion, it will be easy to overlook the glitch, but the best approach is not to have it in the first place. I find the WF, FFT, and SIG displays all have use in their ways, and I would not give up one of them.
~R~
|
Rich,
All agreed, thanks!
I didn't mean to imply the SIG display was useless, but IMHO I'd consider fixing it as a task of lower priority than more pressing truly functional matters, now that it appears to be evident that in real life, FLdigi does NOT actually create unintentional artefacts fed into the radio.
But for the time being, as it causes confusion, I agree it should at least clearly be documented the way it is until it will finally be fixed for good (which as we all know may well take a while).
73s Tobias
.-.-. Am Samstag, 14. September 2024 um 22:52:42 MESZ hat Rich NE1EE <thedustykey@...> Folgendes geschrieben:
Thanks for that...nice to get another look at the situation...
On 2024-09-14 15:45:, T? via groups.io wrote:
>So bottom line, I would recommend to ignore the 'signal' trace in the FLdigi Gui and keep using the waterfall, which appears to be ok for all usual intents and purposes.
I disagree with the suggestion to ignore SIG. The glitch should be identified and commented upon in the fldigi docs...or corrected. I find the SIG display very useful, and I recommend anyone continue using it, but with awareness. Now that we've had this discussion, it will be easy to overlook the glitch, but the best approach is not to have it in the first place. I find the WF, FFT, and SIG displays all have use in their ways, and I would not give up one of them.
~R~
|
Dave
Rich NE1EE
Bill Wiltschko
