Norton AntiVirus Rescue Disk Won't Scan

[randau]

Error 35 General protection fault in NAVDX.OVL

When running NAVDX.EXE, it quits the scan and gives the above error
message whether it's run from my booted DOS Rescue disk or from the
Norton AntiVirus folder on drive C in a DOS Prompt window.

However, when run from Windows by right clicking a folder in the
Windows Explorer tree and selecting the option to "Scan with Norton
AntiVirus" or simply running a scan from the AntiVirus user interface,
it runs ok and does the scan without producing an Error 35 message.
But, don't they use the same Norton AntiVirus folder NAVDX files as
used when running from a DOS Prompt window? If so, why the different
results?

I'm running Norton SystemWorks 2003 in Windows'ME and have been doing
Live Updates, testing my Rescue disk, and running system scans weekly
now for many months without a problem until this past week-end.

Below is a sample run of my Rescue disk from a DOS Prompt window:

D:\Rescue> NAVDX.EXE C: /prompt

Loading NAVDX, please wait...
Using virus definitions from C:\...~1\COMMON~1\SYMANT~1\VIRUSD~1\20040514.033
Using options from D:\RESCUE

Scanning Memory... OK
Scanning Master Boot Records... OK
Scanning Boot Record... OK
Scanning file: C:\MSDOS.SYS

Error [35]: General protection fault in D:\RESCUE\NAVDX.OVL at 059F:00F8
code 0000 SS=15AF DS=15AF ES=0000 load base=0157
AX=9BCE BX=DFF2 CX=DFF2 DX=0000 SP=CF6C BP=CF8C SI=002A DI=0000

C:\>

-randau
Oregon, USA
================================
I read and post from the Google Groups web site using a Spam
collecting email address that I don't use for anything else.
So if someone wants to contact me, cleanup the Spam resistant
Email address below.

randau2...(at)...proaxis.com

by replacing ...(at)... with @

 

[madmax]

Error 35 General protection fault in NAVDX.OVL

When running NAVDX.EXE, it quits the scan and gives the above error
message whether it's run from my booted DOS Rescue disk or from the
Norton AntiVirus folder on drive C in a DOS Prompt window.

However, when run from Windows by right clicking a folder in the
Windows Explorer tree and selecting the option to "Scan with Norton
AntiVirus" or simply running a scan from the AntiVirus user interface,
it runs ok and does the scan without producing an Error 35 message.
But, don't they use the same Norton AntiVirus folder NAVDX files as
used when running from a DOS Prompt window? If so, why the different
results?

I'm running Norton SystemWorks 2003 in Windows'ME and have been doing
Live Updates, testing my Rescue disk, and running system scans weekly
now for many months without a problem until this past week-end.

Below is a sample run of my Rescue disk from a DOS Prompt window:

D:\Rescue> NAVDX.EXE C: /prompt

Loading NAVDX, please wait...
Using virus definitions from C:\...~1\COMMON~1\SYMANT~1\VIRUSD~1\20040514.033
Using options from D:\RESCUE

Scanning Memory... OK
Scanning Master Boot Records... OK
Scanning Boot Record... OK
Scanning file: C:\MSDOS.SYS

Error [35]: General protection fault in D:\RESCUE\NAVDX.OVL at 059F:00F8
code 0000 SS=15AF DS=15AF ES=0000 load base=0157
AX=9BCE BX=DFF2 CX=DFF2 DX=0000 SP=CF6C BP=CF8C SI=002A DI=0000

C:\>

-randau
Oregon, USA
================================
I read and post from the Google Groups web site using a Spam
collecting email address that I don't use for anything else.
So if someone wants to contact me, cleanup the Spam resistant
Email address below.

randau2...(at)...proaxis.com

by replacing ...(at)... with @

See Norton FAQ's
http://service1.symantec.com/SUPPOR...ws 2000/Me/98/XP&src=sg&pcode=nav&svy=&csm=no
It says to create new disk
-max

 

[Nemo S.]

When running NAVDX.EXE, it quits the scan and gives the above error
message whether it's run from my booted DOS Rescue disk or from the
Norton AntiVirus folder on drive C in a DOS Prompt window.

Had the same problem with the new Emergency Disk update try adding the
"/CFG:<directory>" switch to the command line worked for me earlier
today...

Hope it helps


~Nemo~

 

[Buffalo]

"Nemo S." >

Had the same problem with the new Emergency Disk update try adding the
"/CFG:<directory>" switch to the command line worked for me earlier
today...

Hope it helps


~Nemo~

How do you do that if you have Norton set up to check those files at bootup?
I received that error message also on my NSW2002pro and so I uninstalled it
completely and put NSW2003pro on it and it does the same thing. It happened
suddenly on NSW2002pro while I was uninstalling certain programs and ended
up with the PC freezing and making me use a hard shutdown. From that time
on, that error always occurs on boot-up, but never while in Windows98SE.
I did not use a rescue disk.
Thanks

 

[Buffalo]

"Buffalo" > "Nemo S." >

How do you do that if you have Norton set up to check those files at bootup?
I received that error message also on my NSW2002pro and so I uninstalled it
completely and put NSW2003pro on it and it does the same thing. It happened
suddenly on NSW2002pro while I was uninstalling certain programs and ended
up with the PC freezing and making me use a hard shutdown. From that time
on, that error always occurs on boot-up, but never while in Windows98SE.
I did not use a rescue disk.
Thanks

Amazing, I was playing Q3 online and shut down my ZoneAlarm (free) and
disabled Norton's auto-protect while I was playing.
When I left the game, I shut off the modem, re-enabled 'auto-protect' and
then immediately put ZA back on. ZA had an error and wouldn't come on (true
vector not working) so I rebooted and, low and behold, Norton now scans the
files at bootup without an error.
Perhaps it was a conflict between one of ZA's files and Norton.
The reason I say that is because of the above and also because the original
problem on 2002 also started when shutting down ZA while in Windows caused
my PC to freeze (vsmon not responding) and I had to do a 'hard' shutdown.

 

[Nemo S.]

but never while in Windows98SE

My sincerist apologize's I did NOT see the *ME at the end of windows
and I use Windows98 and Norton 2004 and DID RECIEVE Error 35 General
protection fault in NAVDX.OVL when I ran NAVDX.EXE from the command
line as the NEW Emergency Disk went from 9 to 7 3.5" floppies and
since it was new I cold booted the new Emergency Disk and got the
Error 35 General protection fault in NAVDX.OVL modified the my
scan.bat file and included the CFG:<directory> line to the command
line and it worked ..

Maybe I was just lucky ...

~Nemo~

 

[randau]

Before submitting my post, I did uncover the Symantec article titled:

"Error 35" when using the Emergency Boot Disk or Rescue Boot
Disk to scan for viruses (Doc ID: 199842992939)

http://service1.symantec.com/SUPPOR...ws 2000/Me/98/XP&src=sg&pcode=nav&svy=&csm=no

As the document suggested, I did add Himem.sys to the boot Rescue
diskette and updated Config.sys and Autoexec.bat accordingly, but it
didn't fix the problem.

However, I was informed from another thread that a subsequent Virus
Definitions update on 5/18 fixes the problem. So, I checked my
current Virus Definitions date and it had been updated to 5/18. I
re-ran my Rescue disk from a DOS Prompt window and as long as it used
the 5/18 definitions from drive C, it runs ok. But, if it tries to
use the prior 5/14 definitions currently on my Rescue diskette, it
results in an "Error 35" termination.

So apparently it was a defective 5/14 definitions set that caused the
problem that seemed to manifest itself when run from a DOS prompt,
but not when run from Windows. It would have been nice if Symantec
had sent out an email notice telling us of the problem and the
subsequent definitions fix (like it does for some virus threats). I
spent the better part of my time since Sun.5/16 screwing around with
this thing.

-randau
Oregon, USA
================================
I read and post from the Google Groups web site using a Spam
collecting email address that I don't use for anything else.
So if someone wants to contact me, cleanup the Spam resistant
Email address below.

randau2...(at)...proaxis.com

by replacing ...(at)... with @

 

[Buffalo]

Veeeerrrrrryyyy Interesting.
Thanks for the post.

 

[Buffalo]

I just received a reply from Symantec that a 'corrupt' virus def file could
be the cause of the [35] error in my case.
Seems as if it was related to your problem,also.
They suggested to revert to an earlier virus def and then use Intelligent
Updater to update to the latest virus def.
They gave links to describe how to do it.
I was satisfied with their answer.

 

[randau]

I just received a reply from Symantec that a 'corrupt' virus def file could
be the cause of the [35] error in my case.
Seems as if it was related to your problem,also.
They suggested to revert to an earlier virus def and then use Intelligent
Updater to update to the latest virus def.
They gave links to describe how to do it.
I was satisfied with their answer.

Why not just LiveUpdate or download the latest VirusDefs?
Why first revert to an earlier virus def?

-randau

 

[Buffalo]

"Buffalo" <eric(nospam)@nada.com.invalid> wrote in message

I just received a reply from Symantec that a 'corrupt' virus def file could
be the cause of the [35] error in my case.
Seems as if it was related to your problem,also.
They suggested to revert to an earlier virus def and then use Intelligent
Updater to update to the latest virus def.
They gave links to describe how to do it.
I was satisfied with their answer.

Why not just LiveUpdate or download the latest VirusDefs?
Why first revert to an earlier virus def?

-randau

Not sure. Perhaps to get totally rid of the 'corrupted' def file.
I didn't do as they said, but I disabled Norton AutoProtect and ZoneAlarm
when I went online to play Q3 (yes, I do feel that it helps the reaction
time because of my fairly high ping) and when I finished playing online, I
put my cable modem in standby, enabled AutoProtect and then ZA. When I
enabled ZA, I got an error message that there was a problem and so I
rebooted and when it came up, there was no longer an error message during
bootup.
Unfortunately, I don't remember if I actually updated the Norton defs that
day or not.
I wish I knew.
BUT, I had the same problem when I was running NSW2002Pro just days earlier
and I am SURE that there were def updates done after I uninstalled 2002 and
put in 2003.
I still believe it was a conflict between ZA and NSW.
Don't know.