Suntower
Posts: 225
|
| Posted: 08/21/2006, 1:14 PM |
|
For some reason, out of the blue, my AVAST anti-virus started thinking CCPROJECT.DLL was infected with a Trojan virus and thus prevented CCS from running. I thought it was for real, so I ran a full scan, uninstalled CCS then re-installed with a fresh copy from the Yessoftware web site. And then, the next time I started CCS, the same virus warning shows up.
Anyone else run into this?
---JC
_________________
---On a campaign for more examples and better docs! |
 |
 |
wkempees
Posts: 1679
|
| Posted: 08/21/2006, 1:33 PM |
|
no 
_________________
Origin: NL, T:GMT+1 (Forumtime +9)
CCS3/4.01.006 PhP, MySQL .Net/InMotion(Vista/XP, XAMPP)
if you liked this info PAYPAL me: http://donate.consultair.eu
|
|
|
|
mamboBROWN
Posts: 1713
|
| Posted: 08/21/2006, 6:27 PM |
|
Suntower
You might want to contact support ( http://support.yessoftware.com ) and see if they have had any other users with this same issue.
|
|
|
|
peterr
Posts: 5971
|
| Posted: 08/21/2006, 11:45 PM |
|
Yes, someone else reported this problem to Avast. You may want to contact Avast to help them resolve it.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
wouter
Posts: 3
|
| Posted: 08/22/2006, 6:48 AM |
|
I have the same problem. I guess avast is being overzealous.. Any news from avast yet?
|
|
|
|
Emmanuel Bocquet
|
| Posted: 08/22/2006, 9:15 AM |
|
We have the same problem. Several DLLs are identified as infected by avast since this morning. We tried on version 3.0.2.2 (downloaded a few weeks ago) and 3.0.3.1 (more recently)... same thing.
And when reinstalling you get the warning too!
|
|
|
|
cres12
Posts: 4
|
| Posted: 08/22/2006, 9:32 AM |
|
A virus in codeCharge.
Hi,
I just come to download the evaluation version of codeChargeStudio3.0, and with my antivirus Avast, I obtain this message:
C:\ProgramFiles\CodeChargeStudio3\CCShe ll.dll contains the hostile Win32 software. Pcclient-CO [ Trj]
|
|
|
|
peterr
Posts: 5971
|
| Posted: 08/22/2006, 10:41 AM |
|
Looks like this happened during an Avast update, so please contact Avast about this. Only they can support their own product.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Claudio Morinico
|
| Posted: 08/22/2006, 12:53 PM |
|
Hello, i will try to do my best at explaining this behavior. First sorry
about my Enlish, my default language is Spanish 
The reason Avast says it is a virus, is because of heuristics. Most
viruses/trojans come compressed with executable compressors like UPX or
others, so there is no way of knowing if the original executable has
harmful functions inside it (the compressor hides everything).
Every executable compressor, compresses the executables and then inserts
a Loader into the executable for unpacking the protected application
upon execution.
This Loader is common for all the executables compressed with the same
compressor, so if the antivirus software takes a signature from the
compressed executable, it is probable that this signature is the same
for many executables compressed with the same compressor.
CCProject.DLL from CodeCharge is compressed with some executable
compressor (ASProtect I think).
Maybe some virus or trojan uses this compressor, so there is a common
signature for this type of compressor and Avast says CCProject.DLL is a
Trojan or Virus. Just note that it is a generic detection and no special
virus name is given.
Maybe contacting Avast would help, but also consider that if they "fix"
this, maybe in the future it won't recognize those compressed trojans
which match the same signature and that is a problem.
My 2 cents..
--
Claudio Morinico,
Montevideo - Uruguay.
El dia Mon, 21 Aug 2006 13:14:29 -0700, Suntower
(Suntower@forum.codecharge) dijo...
> For some reason, out of the blue, my AVAST anti-virus started thinking
> CCPROJECT.DLL was infected with a Trojan virus and thus prevented CCS from
> running. I thought it was for real, so I ran a full scan, uninstalled CCS then
> re-installed with a fresh copy from the Yessoftware web site. And then, the
> next time I started CCS, the same virus warning shows up.
>
> Anyone else run into this?
>
> ---JC
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
>
|
|
|
|
peterr
Posts: 5971
|
| Posted: 08/22/2006, 1:12 PM |
|
Claudio,
Good comments. Just keep in mind that CCS was also changed many times to prevent virus warnings, but CCS cannot be modified every time when some antivirus software is updated (which happens very often). In such case Yes could spend most of their time fighting antivirus errors instead of supporting CCS features. Thus I think that some antivirus companies should take more responsibility and improve their own detection methods. If other antivirus programs don't display virus warning then it means that AVAST could do better job as well.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Suntower
Posts: 225
|
| Posted: 08/22/2006, 3:00 PM |
|
I e-mailed Avast support.
I didn't mean to stir things up. This just seemed so weird---never noticed this with any other program so I thought that Avast was -correct- (at first, anyway). I wanted confirmation so that if there -was- a virus in the Yessoftware download someone could be notified.
Thanks to all,
---JC
_________________
---On a campaign for more examples and better docs! |
|
|
|
Claudio Morinico
|
| Posted: 08/23/2006, 12:17 PM |
|
I agree with you Peter, my comments were not meant as a critic for CCS,
I just tried to clarify things.
Best Regards,
--
Claudio Morinico,
Montevideo - Uruguay.
|
|
|
|
peterr
Posts: 5971
|
| Posted: 08/23/2006, 1:14 PM |
|
I understand and found your comments useful as well. Thanks Claudio.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
wouter
Posts: 3
|
| Posted: 08/28/2006, 1:23 AM |
|
The problem has disappeared on my machine. I guess avast fixed it.
|
|
|
|
|
