Is anyone familiar with the conflict Avast has with Oxford English Dictionary that causes OED to crash when opened to search for definitions?
OED tech support indicated other OED user have experienced this “oedcd_v3.csx encountered a problem and needs to close” issue.
hime3
And who said it has anything to do with avast? I mean, your message doesn’t really imply it.
If you stop avast! resident protection temporarily, does it help?
What operating system do you use?
Just a quick Google scan for “oedcd_v3.csx” shows reports on the OED website on “how to deal with antivirus issues” that are specific to antivirus products other than avast! and may well be more general.
It may be more effective to start with issues known to the OED product … if you exhaust those then please return to ask for help in this forum.
I have been using various free and costly antivirus software for 10 years without any OED conflict. A friend told me about Avast. Avast seems to be superior antivirus software.
Before installing Avast this week OED worked perfectly. After installing Avast OED crashes.
The workaround: stop On-Access protection and OED functions perfectly.
OED tech support reports that Avast has contacted OED and has OED software to determine why Avast causes OED to crash when searching. Other OED users have reported the issue to OED.
The issue was initially printer related. The printer solution does not remedy the Avast issue.
I poseted this to determine if anyone at Avast can confirm that Avast is indeed working on a resolution of the issue?
If Avast has provision to select scan-exceptions for specific installed software, please tell me its location.
Thanks for the feedback…
What operating system do you use?
Hi hime3 you may try to turn off avast from scanning this file.
Right click Avast icon
Select On-Access Protection Control
Select Standard Shield
Select Customize
Select Advanced tab
Select Add
Enter oedcd_v3.csx or .csx
Ok your way out
I don’t think this has any chance to help. I don’t believe the problem is in avast! scanning the file; if there’s some conflict there, it will be much “deeper”.
This is interesting to me because I have Oxford Study Interactive Dictionary on my computer but it runs without conflict nor crashes. Yeah, I know it’s not quite the same dictionary as hime3 states in the other post but it should be similar in the way it works.
I started it up while reading this post just so I could be sure that it would not crash. I have taken my time with this post and messed with the OSID some just to see if I could active a problem. None yet … nor have there been in the past. 
Perhaps, though, there is some slight difference in the 2 programs that can give a clue to the problem. ???
See info in my signature for OS, etc.
OK, maybe I was wrong. The dictionary uses some crappy copy-protection means that cause these troubles. In that case, excluding the files or installation folder from scanning might help. I am not very optimistic about that, but it’s worth trying.
Regarding the current status - even though we contacted the OED support, we don’t have the software for testing.
My OED has no conflick with Avast.
After I installed Avast! my Oxford English Dictionary stopped working with the following message:
Not enough memory : unable to complete. Close other application. Close OED, and try again.
I thought it was a problem with the OED software - such problems had happened before, very good dictionary but rotten software - so I re-installed it, to no avail.
I checked the O E D website, and for the version of their software I am running (3.0) they have a short article saying that that memory problem happens because there is a conflict with some anti-spy software, and they say that there is no workaround.
I tried disabling the scanning on the OED programs, and even on their copy-protection software (the infamous C-Dilla), but it didn’t work either.
The only thing that works is stopping the Standard Shield and re-booting. Just stopping while you’re working with the dictionary won’t work. Obviously not a very satisfactory workaround.
Of course, I’ll be writing to OED (their software costs a cool GBP 350), but, in the meantime if someone has got a solution…
My avast! is 4.6.763, with VPS 0611-2. I’m running Windows XP.
Did you use Norton Antivirus before?
If you add the word ‘REM’ before the avast line into the file C:\Windows\System32\Config.nt, will it help? I mean, open this file in Notepad, add the word REM and a blank space before the avast driver line. Save. Boot.
Will it help?
Yes, I did have Norton Antivirus before.
I’ve just tried what you suggest (I didn’t forget rebooting), but unfortunately it disn’t worK. I’ve set the file back as it was before.
Thanks for answering so quickly, if you or anyone else has another idea, I’m ready to try it.
Ylefevre, can you follow this?
http://forum.avast.com/index.php?topic=19556.msg165617#msg165617
If you hae Norton Antivirus before we must be sure it’s fully uninstalled…
I have been using both avast! and the OECD for years, with no problems.
It is only since the last avast (Home) program update that OECD has started to crash (with “not enough memory” and “csx problem” notifications).
If I disable “avast! Antivirus” in msconfig/services, the problem ceases. Diabling any other avast component service does not do the trick.
Has anyone finally solved this conflict?
Tks
OED uses controversal copy protection system called “C-Dilla”.
See e.g. http://www.privacyandspying.com/privacy-c_dilla.html
It’s C-Dilla that’s causing the problem, not OED itself…
Yes, OECD comes explicitly bundled with C-Dilla. It’s take-it-or-leave-it, but no secret.
So, as I choose - however reluctantly - to take it, how do I mollify Avast?
Tks again.
No, it’s something between the OECD and Avast. Disabling scanning of OECD solves the problem, while disabling scanning of C-Dilla makes no difference.
This is what I did (thanks to OECD support):
[1] Right-click on “avast” icon in taskbar.
[2] Choose ON-ACCESS PROTECTION CONTROL from the menu.
[3] Click the DETAILS button. On the left hand side, click the STANDARD SHIELD icon.
[4] Click the CUSTOMIZE… button, ADVANCED tab.
[5] At the bottom of this screen, add a location to exclude from
scanning by clicking the ADD button. Type in the path where the OED is
installed. (By default it is C:\PROGRA~1\OED*.*, but foreign language versions may use another name for Progam Files. Note that you must use the short filename for the PROGRAM FILES folder.) Click OK.
My OECD is now functioning normally.