
ps: kcc if you notice this, please feel free to add a mad man animation who is super alerted running in circles

They sound like stand-up, quality software.blueznl wrote:Cyclaan and eGambit
Yes. Virus-scanners know about UPX (and other compressors) and decompress them before scanning.IndigoFuzz wrote:Do you get the same problem if you process the executable with UPX?
It has been resolved before, but the poor quality control of almost all Anti-Virus software leads to false-positives springing-up again, for all sorts of applications, not only PB.Can this problem between Purebasic and Symantec be resolved?
Here's a support email I got from a customer today, regarding BitDefender.Bitblazer wrote:Just got a Mail from bitdefender support, that they released an update for the signatures that should fix the PB problem. Too late for me but just in case anybody wants to know.
Code: Select all
; IDE Options = PureBasic 5.61 (Windows - x86)
; Executable = App.exe
; DisableDebugger
Code: Select all
; IDE Options = PureBasic 5.61 (Windows - x86)
; Executable = App.exe
; CPU = 1
; DisableDebugger
Manual wrote:Cpu Optimisation (next to Executable format)
This setting allows to include Cpu optimised PB functions in your executable:
All CPU : The generic functions are included that run on all CPUs.
Dynamic CPU : The generic functions as well as any available CPU specific function are included. The function to execute is decided at runtime. This creates a bigger executable, but it will run as fast as possible on all CPUs.
All other options : Include only the functions for a specific CPU. The executable will not run on any Cpu that does not support this feature.
Note: No PB functions actually support this feature for now (it is ignored for them). However, some User Libraries include such optimisations.