If you really believe Norton is the answer to PC protection then you're probably in a lot more risky a situation then you're thinking. The amount of "Norton protected" systems I've had to clean viruses off...
Just don't rely on any one anti-virus pack to keep safe, that's all I'm saying. No anti-virus and a good understanding of how infections happen is a heck of a lot safer then a false sense of security.
I mean, think about it. On one hand you're saying "don't let them fool you into being less protected", and on the other you're quite happy to rollback to Norton '07. Seriously, think about it.
I recommend AVG Free myself. Grisoft has been around for well over a decade now.
the problem is client.exe attempts to write to the macro file, tus triggering a block as it might be damaging something.
this can be fixed by EA by changing permissions for the macro area and sending the path's and why the program does this to symantic so they can put client.exe on the 'safe' list.
There are two problems here.
1) They can't add "client.exe" to any safe list.
Obviously they won't even consider treating all files that happen to have that name "safe", so they need to use a hash checking system to identify it.
But whenever the client gets patched, Norton would also have to release a patch for their safe list in order to match the new hash. They simply
won't bother to do this, and even if they do assign an employee to the task, odds are he's gonna take at the very least a day to get it done with each patch.
Instead they need to kill whatever file writing block they've put in place entirely, or at least provide a pop-up giving you the option to allow that particular program to write in that particular way.
2) How the heck is EA supposed to know what part of their code is triggering
Norton's danger flags? They didn't write the checking routines. They wrote the
macro routines, and they did that well before Norton's code existed. Code which, I might add, EA doesn't have access to. How are they supposed to debug it for Symantic?
Symantic, on the other hand, doesn't need to grab the UO source (which EA won't give them anyway) in order to find out when it's triggering their software. A compiled EXE is perfectly suitable for that task, and those are freely available.