For anyone who comes across the Symantec problem I mentioned, when I opened the registry key mentioned in the KB article, I found the VDD key contained the SYMEVNT1.DLL file that is mentioned in my error box. When I deleted and re-created the VDD key with blank content as directed in the KB (using REGEDT32, as the value has to be a REG_MULTI_STRING), it seems to have (so far) solved my problem.

Thanks, Scott!

At 08:59 AM 2/4/2002, R. Scott Perry wrote:

Actually, I get a similar Windows error related to f-prot.  Something to the
effect of " VDD error: a device attached to your system isn't functioning"
and we aren't running any Symantec products on either of the servers that
get this error.  I'll get the exact message when it happens again.

We just today came across this error message:

        16 bit MS-DOS Subsystem

        C:\Progra~1\FSI\F-Prot\F-Prot.exe
        SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers.  VDD. Virtual Device Driver
        format in the registry is invalid.  Choose 'Close' to terminate the application.

This one caused by a problem in several versions of Windows.  Microsoft has a Knowledge Base article at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q254914 acknowledging the problem and explaining how to fix it (you need to delete and re-add a new registry entry).

This looks like a different message than the one you got, but I figured it may be related.
                       -Scott

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

This E-mail came from the Declude.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".  You can E-mail
[EMAIL PROTECTED] for assistance.  You can visit our web
site at http://www.declude.com .

_______________________
Scott MacLean
[EMAIL PROTECTED]
ICQ: 9184011
http://www.nerosoft.com

Reply via email to