Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with specific versions of Norton Antivirus 1

Status
Not open for further replies.

div0

Programmer
Sep 11, 2001
3
US
First, let me say that I have tried Symantec tech support repeatedly on this question. I am a software developer and a software product of ours has some type of conflict with a couple of specific versions of Norton Antivirus. Specifically, we are experiencing problems with NAV 2000 Version 6.10.20 and NAV 2001 7.00.51F. Earlier versions prior to 6.10.20 and versions later than 7.00.51F do not appear to have the problem with our application. Disabling NAV makes the problem go away. We get either a OE exception with blue screen on windows virtual driver vxd ifsmgr(04) or we get invalid page exception on our program. We get many reports from our customers and have also recreated the problem in-house. The application is primarily a DOS console application running in Win9x written in Visual C. The problem occurs when our applicaiotin issues a system call to run a dir DOS command. The computer hangs and typically cannot recover. Searching for an answer, found where Python (open source Python programming language) also had a similiar problem with Ver 6.10.20. Any help would be appreciated.
 
I had a problem similar to yours. Get round it by getting the NAV to exclude .exe files from its check. This solved the problem.

Upgrading to NAV corporate also cured the problem.
 
I have tried most all options and exclusions NAV has available, none have worked short of just out-right disabling the NAV auto-protect. I think it is some type of resource and/or timing conflict. NAV is a resource hog and ours has a pretty good appetite also. I've heard it takes a lot for windows to switch back and forth from protected mode to real mode. Are the DOS commands such as dir still real-mode 16-bit programs? We are pretty sure this problem occurs when we issue a C system call to run the DOS dir command.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top