This produces a false positive.

Started by Elias Montoya, November 05, 2013, 03:35:49 AM

Previous topic - Next topic

Elias Montoya

 Can somebody compile this? my avast antivirus always complains that one of the temporary
PB compiler files is a positive for some kind of threat... here is a capture.

Nothing special in the project, just a timer and couple labels.

Win7, iMac x64 Retina display 5K, i7-5820K 4.4 ghz, 32GB RAM, All updates applied. - Firefly 3.70.

Eddy Van Esch

Elias,
Your code compiles and runs fine with me. AV scanner: 'Total Defense', Win 7.

Kind regards
Eddy

Elias Montoya

Win7, iMac x64 Retina display 5K, i7-5820K 4.4 ghz, 32GB RAM, All updates applied. - Firefly 3.70.

James Padgett

Virus scanners....  uuggg!!!!

They have to flag positives so you will think they work better than their competitions products...

Eddy Van Esch

Quote from: James Padgett on November 05, 2013, 07:07:47 AM
Virus scanners....  uuggg!!!!
In many cases AV scanners are only slightly less annoying than the 'evil' they are trying to combat ..
Eddy

Joerg B.

Hello Elias

Your code compiles and runs fine with me. AV scanner: 'Kaspersky v14', Win XP Pro.
Greeting from Germany

Joerg

Jim Dunn

Fine for me, using Microsoft Security Essentials on Win 7 Ultimate Dell OEM 64-bit.

I've found I can calm most AV programs using the following code at the top of my source, not sure where you would put it in Firefly...

%appmajor    = 1
%appminor    = 0
%apprevision = 0
%appbuild    = &H0000??
'$appversion  = "1.0.0.0"
$appname     = "PowerBASIC Application"
$appfilename = $appname + ".exe"
#RESOURCE VERSIONINFO
#RESOURCE FILEFLAGS  0
#RESOURCE FILEVERSION %appmajor, %appminor, %apprevision, %appbuild
#RESOURCE PRODUCTVERSION %appmajor, %appminor, %apprevision, %appbuild
#RESOURCE STRINGINFO "0409", "04B0"
#RESOURCE VERSION$ "Comments", "Comments"
#RESOURCE VERSION$ "CompanyName", "CompanyName"
#RESOURCE VERSION$ "FileDescription", "FileDescription"
'#RESOURCE VERSION$ "FileVersion", $appversion
#RESOURCE VERSION$ "InternalName", "InternalName"
#RESOURCE VERSION$ "LegalCopyright", "LegalCopyright"
#RESOURCE VERSION$ "LegalTrademarks", "LegalTrademarks"
#RESOURCE VERSION$ "OriginalFilename", $appfilename
#RESOURCE VERSION$ "ProductName", $appname
'#RESOURCE VERSION$ "ProductVersion", $appversion
#RESOURCE MANIFEST, 1, "D:\PB10\Include\Manifest.xml"
#DEBUG ERROR ON
'#DEBUG DISPLAY ON ' will stop ON ERROR from working
#COMPILE EXE
#DIM ALL
#OPTIMIZE SPEED
#REGISTER NONE
#TOOLS OFF
'#Break On
'#Console Off
#Compiler PBCC
#Compiler PBWin
'%unicode = 1
#INCLUDE "win32api.inc"

FUNCTION PBMAIN() AS LONG
'
END FUNCTION
3.14159265358979323846264338327950
"Ok, yes... I like pie... um, I meant, pi."

Robert Eaton

I  had that happen one time with Avast with a PB dll I wrote. It was a dll that I was distributed with a program.
Contacted Avast support and it was fixed in their virus definitions in about 24 hours.

Elias Montoya

Am i the only one using avast here?  ;D
Win7, iMac x64 Retina display 5K, i7-5820K 4.4 ghz, 32GB RAM, All updates applied. - Firefly 3.70.

José Roca

#9
Quote from: Elias Montoya on November 06, 2013, 05:32:39 PM
Am i the only one using avast here?  ;D

Hopefully. Avast is going to become synonim of false positive. The title of this thread should be changed to "This produces an avast".

David Warner


Paul Squires

Paul Squires
PlanetSquires Software