Forum : ARM
| Post Information | Post |
|---|---|
|
December 8, 2008 - 9:31pm
|
Hello. I just loaded RIDE 7 (BN20) and RKit-ARM (BN22), as well as the latest STM3210E-EVAL project from the ST Microelectronics web site. When I try to load the RIDE project (STM3210E-EVAL_Demo.rprj), I get the following anti-virus warning:
This message box flashes a number of times, and then RIDE closes. I don't have a chance to select "allow this script to run" and click "OK"; it's as if RIDE is automatically clicking the "OK" button to abort the script and (eventually) giving up. Has anyone else seen this issue before? I did notice that after the sample code was unzipped, it was all marked "read only". I changed that with a recursive "attrib -r", so everything's writable now, but that had no effect on this problem. Any suggestions? Thank you! -Dan |
Follow-up:
Thinking it may have been a problem in the project file from ST, I tried creating a new project from scratch. That gave the same result: repeated antivirus warning error box, followed by RIDE closing.
Is something wrong with my installation? I installed RIDE 7 and then RKit-ARM, both the latest build available from the download area.
Thank you!
-Dan
Hi,
Can you please try to open and compile one of the RIDE examples in "\examples\..."?
That will tell us if the problem is related to this particular project, or if it is general to your RIDE and/or Windows and/or antivirus.
Note that RIDE uses jscripts internally, so your antivirus must allow these scripts to run. Can you check the antivirus configuration?
Which version of Windows are you using?
Best Regards,
Vincent
I tried that, too. Same result.
I'm using Windows XP SP2 and Norton AntiVirus 2003 (it came with the computer). I do have script checking enabled (standard security practice on networked computers), and have seen these warnings in the past (when installing older versions of the Microsoft Platform SDK, for example), but I was always able to select "Allow script" and click "OK". When RIDE 7 causes these warnings, I do not have the opportunity to click anything. The warning flashes several times (as if there are multiple warnings that occur), and then RIDE closes.
If I disable script checking, I can get RIDE 7 to work. But I'm not particularly comfortable doing that since I need to be able to browse the Internet and receive email on my development system.
As I said, when other programs that use scripting are "caught" by Norton AntiVirus, I have the opportunity to say "allow script". With RIDE, I don't. I have no idea what the difference might be.
Is this a known problem? Is there a plan to resolve it? Or is the "resolution" for me to run in an unsafe mode?
Thank you!
-Dan
Hi,
Can you please give me an estimation of the time during which the Norton window stays open before it closes?
Is it the same duration for all the instances of the window? (approximately)
What version of Norton are you using? I have Norton too and it doesn't look like yours. (and it doesn't block scripts)
Please also confirm that when you installed Ride, you were logged under a user account that has administrator rights.
This is the first time we hear about such a problem. Of course we will do our best to correct it, but first we'll have to understand it and for that we will need your help. (answering questions, testing fixes, ...)
I will discuss it with my colleagues and make a temporary version for you to test, or come back with more questions.
In the meantime the only solution I see is to disable the script locking feature of Norton.
Probably you can tell Norton to always allow scripts from Ride, keeping the current behavior for other application.
Or maybe you can activate the blocking feature in your internet browser and in your email software, so that you are still protected from 'real' malicious scripts. And then you deactivate it in Norton. That's what I've been doing for years and I have never been infected. (I have been attacked, but the attacks were blocked)
Ride needs to execute scripts (a lot of scripts) for operating. It will never work if it cannot do it. And you cannot work in a configuration where you have to manually allow each script execution, as you would have to do it hundreds of times at each compilation.
Best Regards,
Vincent