Re: VSDATANT.SYS FIX

Re: VSDATANT.SYS FIX

The first time I had a blue screen telling me there was an important error and to power off immediately. It gave me the code as per my ealier post.The second time I received a pop up message saying it was a VSDATANT.SYS problem and if I clicked onto the line to Zone Labs I would find the fix.I clicked but have nor found the fix other that what you have just suggested.Regards,Keith.

Re: VSDATANT.SYS FIX

Try uninstalling ZoneAlarm and then following these Manual Uninstall Direction'sand deleting all instances of ZA,then perform a reinstall and see if you still get the error.Might just be the Vsdatant driver has become corrupted.

Re: VSDATANT.SYS FIX

Re: VSDATANT.SYS FIX

If your problem occurs during boot, I found that ZoneAlarm would not crash if I started it manually. I'm using XP SP2. That led me to try changing the startup order and/or timing of the startup applications. I found Startup Delayer, free here:http://www.r2.com.au/software.php?pa...how=startdelayand set a 45 second delay for ZoneAlarm. I left all other apps alone although you're free to work with them too.My computerhasn't crashed since. Of course, your mileage may vary.

Re: VSDATANT.SYS FIX

Here's the answer to everyone problem with the VSDATANT.SYS File.I booted up my computer using the Windows 98 Emergency Boot Disk and deleted the VSDATANT.SYS File in MS DOS. It is in the C:\windows\System 32 Directory.The I rebooted my computer and saw that Zone Alarm was disabled on the Notification Section of the Taskbar. I then installed the ZA update and it installed without any problem.Hope this works for everyone out there.

Re: VSDATANT.SYS FIX

I get an VSDATANT.SYS error when trying to use Cisco Secure VPN 4.0.1 Client on a Windows 2003 Server machine. I believe the drivers are not compatible, and the fixes listed on this thread aren't applicable. Anyone else out there have the same? Any suggestions?