Author Topic: Conflict with program using VB Scripting!!  (Read 4593 times)

0 Members and 1 Guest are viewing this topic.

KEF

  • Guest
Conflict with program using VB Scripting!!
« on: August 28, 2004, 06:57:18 PM »
I just installed avast last night since my Norton expired.  I have
a design software I use that uses VB Scripting and I keep getting
an alert for  " win95:SK "  when I run the .exe file.  When I turn
the avas off,  everything works fine.  Is there a way to tell avast
to ignore this program like Norton does so I don't have to turn
the virus protection off and on.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Conflict with program using VB Scripting!!
« Reply #1 on: August 28, 2004, 07:56:41 PM »
I just installed avast last night since my Norton expired.  I have
a design software I use that uses VB Scripting and I keep getting
an alert for  " win95:SK "  when I run the .exe file.  When I turn
the avas off,  everything works fine.  Is there a way to tell avast
to ignore this program like Norton does so I don't have to turn
the virus protection off and on.

If you are sure that the file is not infected then, just open avast! settings and add the folder (or just the specific file) to the Exclusions list. This will affect all avast parts (on-access and on-demand scanning) but not boot time scanning (if you schedule it).  ;)

To get avast settings, run it, right click the skin and choose Settings.
« Last Edit: August 28, 2004, 08:30:17 PM by Technical »
The best things in life are free.

KEF

  • Guest
Re:Conflict with program using VB Scripting!!
« Reply #2 on: August 28, 2004, 08:18:17 PM »
I'm not completely positive, but I'm assuming that the file isn't
infected.  I removed the program from my computer and then
re-installed to make sure.  Sure enough, when installing, I kept
getting the same thing.  I posted this to the software user board
and a friend of mine who's a programmer is the one who told
me about the VB Script.  So if it's actually infectected, that means
the Install disk is hosed as well.  

I just want to get to the bottom of this because were talking about
a $7,000 software package and it's crucial to my business.

Thanks for the response, I really appreciate it.

KEF


Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Conflict with program using VB Scripting!!
« Reply #3 on: August 28, 2004, 08:34:20 PM »
So if it's actually infectected, that means the Install disk is hosed as well.  
I just want to get to the bottom of this because were talking about a $7,000 software package and it's crucial to my business.
Thanks for the response, I really appreciate it.
KEF

Oh, probably, you won't have an infected CD of that price...
Can you scan in on-line (see http://www.security-ops.tk/ for a lot of options)?
After that, and being sure you're clean, disable avast, install your software, install avast again and add the folder/file in your HDD to the Exclusion list.

Can you post the name of the file (with its path) and the name of the software?
The best things in life are free.

KEF

  • Guest
Re:Conflict with program using VB Scripting!!
« Reply #4 on: August 28, 2004, 09:48:24 PM »
 I took your advice and scanned externally using the
Symantec.  No viruses were found.  Does that  mean
that I'm clean?

My design software package is called Matrix which
is a plug-in to Rhino CAD.   It's used for designing
jewelry.  

The path that keeps coming up is:

c:\DGMatrix35\System\Matrix35.exe

It's the executable file for the program that's giving
me the problem.  I went into Avast and settings and
added the .exe file to the exclusion list, but  I keep
getting the alert and then I can't start the software
without deactivating Avast.

Any other hints for me?

Thanks,

KEF

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Conflict with program using VB Scripting!!
« Reply #5 on: August 29, 2004, 01:06:37 AM »
I went into Avast and settings and added the .exe file to the exclusion list, but I keep getting the alert and then I can't start the software without deactivating Avast.
Any other hints for me?
Thanks,
KEF

1. Check the spelling of the added path (or, better, browse to it).
2. Stop and reactivate the providers or, better, boot.

Did you sent that file to avast Chest?
The best things in life are free.