Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QB64 Phoenix Edition v3.6.0 Released!
#30
(02-28-2023, 06:18 AM)DSMan195276 Wrote:
(02-28-2023, 04:48 AM)madscijr Wrote: Is this a false alarm, or is it a real threat?

We had a report of that on GitHub as well. Personally I scanned both the 7z'd and unzipped version and didn't come up with anything. However, we've had false positives in the past from the MinGW compiler, I think in general the Antivirus scanners just don't like compilation tools. I personally am not worried about it, we get the compiler from a reputable builder and that's the only external piece we place into QB64-PE that comes precompiled.

I would say the "Trojan.Script.Vbs-heuristic.druvzi" is certainly a false positive, we have no Visual Basic Script code in QB64-PE (both in our code, and the MinGW compiler). I would assume it thinks some of the QB64-PE code itself is VBS code, I guess, but who really knows.

(02-27-2023, 04:49 PM)bplus Wrote: It's a bug when the mouse clicks are misaligned the same as the gap. I don't know if it still happens because I got in habit not using a maximized window.

Yeah it does seem like somethings wrong. The black bar is normal when the dimensions are wrong, but I think it's supposed to be on the _bottom_ of the window. And it sounds like the mouse is acting as though the bar is not there, so effectively everything is offset (which doesn't surprise me).

I'm trying it myself and seeing the same behavior, but my older versions seem to do the same thing. I did notice that if I maximize QB64-PE when it's already the correct size then the black bar is on the bottom (you can achieve that by maximizing QB64-PE and then exiting it while maximized. When you start it again it will have retained the maximized size). Not sure what it means Big Grin but clearly it's not consistent at the very least.

Thanks, that does make sense about the compiler, although shouldn't their virus definitions already know about and be able to identify MinGW which is a known and established tool at this point? I can do a file compare against the MinGW files in older copies of QB64 and see if they're the same (not sure if the devs changed the version they're using, then the comparison would fail). Or later on I can just unzip the 7z and do a scan on the individual files. On virustotal it was only one virus checker out of like 50 that saw a threat, and Windows Defender loves giving false positives, especially for all my MS Office VBA macros!!
Reply


Messages In This Thread
RE: QB64 Phoenix Edition v3.6.0 Released! - by madscijr - 02-28-2023, 01:12 PM



Users browsing this thread: 4 Guest(s)