PS: that's weird though, I can't reproduce the problem at all with the stdrt.exe of the build 251 of MMF2 Dev, Norton doesn't report any warning on virustotal.com. twister maybe the application was built with an older version of MMF2?
PS: that's weird though, I can't reproduce the problem at all with the stdrt.exe of the build 251 of MMF2 Dev, Norton doesn't report any warning on virustotal.com. twister maybe the application was built with an older version of MMF2?
Yves, you could be correct. I don't remember when I updated to 251. It was close.
Give me a few days to test and repost. I'll rebuild my app using 251 as a different version with "Compress the runtime" checked, and have my friend install it to see if it repeats.
I haven't updated to 251 either, I'm still on 249. I had to go through a lengthy process of adding stdrt.exe to its list of exclusions, which was not particularly easy to find.
The numbers of people who would have released their application would be in their gazillions (maybe), and unwittingly have compressed the application down. Many won't even see this thread. Users downloading the application would then think "hey, this can't be trusted, let's delete it".
Norton are slacking big time.
Yves, norton is catching the mmf2 Dev 251 test build with a checked stdrt.exe "Compress the runtime". A unchecked 251 build runs fine without norton catching stdrt.exe. I'm guessing that the stdrt.exe is not used in the unchecked build, therefore it's not there for norton to catch it.
ChrisStreet, the frustration is shared. I rebuilt my older apps in 251 unchecking the "Compress..". But all the past downloads are unknown.
Edit: P.S. I am sure the original norton catch was from 249 because I updated thinking 251 resolved it. The second build was with 251 with "Compress..." unchecked (to be safe). The third test was with 251 "Compress.." checked.
Honestly guys I'm tired of people saying Norton deletes stdrt.exe although it doesn't generate any alarm on virustotal, that's frustrating.
It must not happen with every installation of Norton, because given the number of Norton users we would be flooded with messages if this was happening with all the applications created with MMF2...
twister, please tell your friend to submit the file to Norton. I've already submitted it to them some time ago as someone else reported it too, but I didn't get any answer from them and anyway as I can't reproduce it I can't tell them what happens...
And could any Norton user that sees this post scan the Data\runtime folder of MMF2 and if a false positive is detected submit the file to Symantec, please? And post here "yes I use Norton and I can reproduce the problem" or "no, I use Norton and I can't reproduce the problem". Thanks!
I've had this problem at one point. But I no longer have Norton...
Yves I can understand and I'm sure this will be fixed one way or the other. You guys are great and I really enjoy using mmf. I remember Amos and Stos.
My friend is very strict when it comes to things like this unless he is absolutely sure, so I don't know if he will report it as false. I trust his home computer and judgment because he is the back end programmer for Nintendo, not a gamer. His home computer is connected to them and must pass their international security scrutiny which he programs. I am only telling you this to understand why I trust him and his computer.
Perhaps he is overkill. Maybe norton has different security level setting and scans.
Edit
P.S. The app in question that started this post is here at www.fishraptor.com. Only to give roots to this post.
Edit2
I trust mmf and designers as welland there was no intentional name dropping.
Hi Yves.
I can confirm that this issue happened on four different computers running Nortons software, from the Antivirus to the full 360 Internet Security pack. I posted my files to Nortons loads of time, I always got the standard email reply saying yes, it is a false positive, and it would be resolved in 24 hours. It never got resolved. Once my subscription with Nortons Antivirus expired, I moved over to Esat NOD32 and haven't had any bother since.
I am very disappointed with Symantic over this because they are a huge name in the antivirus world and I would have thought they would have addressed this within the four months odd I had between encountering the issue and my subscription expiring. I don't have Nortons installed any more but the next time I'm at a friends house who has the software on their computer, I'll check it out again and see if it's still happening.
Having being with Nortons since the days of DOS I had a lot of respect for this company and its sortware. I lost that very fast over this issue and I no longer recommend this software when folks ask me.
KnightTrek Productions
http://www.knighttrek.com
what does humble pie taste like?
Thank you Paul! I'm more interested in real tests from current Norton users who use the latest version though.
I agree with what you say. Symantec don't care. ESET or Kaspersky reacts in a couple of hours when you send them a false positive, plus they say they are sorry, that's almost a pleasure to submit them a false positive because you know they listen their customers or the other companies and react very quickly. I used Norton too, but now I recommend people not using Norton nowadays.
But that's not the point of the post. Please any current Norton user tell us if you experience the same issue with the latest virus definitions, and if so please submit the file to Symantec, thanks!
Posting Permissions
Reply With Quote