I suspect you are now dealing with a conflict of interests here. NAV is
probably concerned about developers reverse engineering their product
and figuring out how to bypass and/or compromise it. While this is
likely to be ultimately unsuccessful (anyone truly interested in this
level of reverse engineering will use a full-blown reverse engineering
tool such as IDA) it does indicate that Symantec has determined that
certain legitimate configurations are incompatible with their product.
You might consider complaining to them, and also filing a complaint with
the FTC and/or your state AG indicating - a suggestion that this is done
as an anti-competitive technique might be quite persuasive (oddly
enough, big companies are sensitive to anti-trust these days - and often
bashing the lawyers on their heads can be more effective than making a
business case, as sad as that might be.)
In such a situation, my suggestion to you would be to try talking to the
Symantec organization and, if they are unwilling to assist in
interoperability testing in a reasonable development environment,
document to your customers that you cannot guarantee compatibility with
NAV because it is not possible to test with it.
You might also wish to consider attending the next IFS plugfest in order
to do interoperability testing with NAV where there will be NAV
developers present.
A CONSTANT source of frustration in debugging server-class systems is
the lack of availability of symbols for the NAV drivers. That, combined
with their use of FPO, makes it quite difficult to debug in the presence
of their product - difficult, but not impossible. I have finally
reached the point where I advise server-class customers that they should
consider working with a different vendor that might be more responsive
to their needs - and some have decided to do that.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Andrei Belogortseff
Sent: Wednesday, October 20, 2004 2:23 PM
To: ntfsd redirect
Subject: [ntfsd] How do you test compatibility with NAV 2004?
I’ve spent the better part of the day trying to find out why Norton
Antivirus 2004 reports an internal error when installed on a test
machine,
and it turns out it does that when it detects the computer is running in
the kernel debugging mode (as a test computer being debugged with WinDbg
in
kernel mode from another computer).
The Symantec’s web site reports the following:
“Kernel debuggers, which are sometimes used as programming tools, are
incompatible with Norton AntiVirus 2004 and 2005 in Windows XP”
and also:
“If Norton AntiVirus does not function correctly after running a
debugger
program or a debug viewer program, disable the debugger or viewer, and
then
uninstall and reinstall Norton AntiVirus.”
So, if you want to test the compatibility of your file system driver
with
NAV2004, how do you do that?
Thanks!
Andrei Belogortseff
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com