Thanks.
I knew about that option but want to try the 'send to McAfee' option to see if I get a response and closer validation from them. Might help others going forward.?
If not, successful with that, I'll dig into the memory banks and see if I can figure out how to run the package validation checksum from the SourceForge files.?
My current WSJT-X is recent and working fine for my QM's and QD's on two, fully up to date, Windows 11 laptops. So not desperate :)?
GREG
On Thu, Apr 3, 2025 at 7:32 PM, Stan Dye via groups.io
<standye@...> wrote:
On Thu, Apr 3, 2025 at 07:52 AM, Greg McCain wrote:
Now, if I can get McAfee to check and bless the latest hamlib release which gets immediately quarantined when I try to pull it off SourceForge I can try out the latest WSJT-X version. Sigh ....
Greg, I had to turn off McAfee virus scanning while downloading the file and unzipping it.
After I had the hamlib.lib file out of the zip and deleted the zip, there was no longer a problem with it, and I successfully dropped it in the wsjt-x folder.
?
A few other files (JTAlert) I had to put in the 'Excluded files' list on the real-time scanning tab of McAfee.
?
