16 bit subsystem error and Symantec Norton Antivirus under W2k

[gustavo]

I am running Windows 2000 Professional Service Pack 2 and Norton AntiVirus 2001 and I get the following error message from the 16 bit subsystem, that seems Symantec related, could you help me ?? ....

Error translated from spanish :
" SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers.VDD
The virtual devices controller format in the registry is
not valid, choose close to end the application."


The SYSTEM\CurrentControlSet\Control\VirtualDevideDrivers.VDD is a REG_MULTI_SZ whose value is:

C:\Program Files\Symantec\S32EVNT1.DLL (file dated august 25, 2000)


Also I noticed that there is another copy S32EVNT1.DLL also dated august 25 2000 under C:\WINNT\System32

Thanks Gustavo.-

 

[Slikkster]

You might want to download an update for this file...it's included in the package file called "sevinst.exe" from symantec:

Sevinst.exe

Doubleclick on it to install it afterwards.

 

[gustavo]

Slikkster you are the one, problem solved!!!

BTW: what that file is supposed to do ?

Gustavo.-

 

[Slikkster]

I'm glad it worked out. As for what exactly this file does, here's a little snippet from another website:

The Symevnt.386 file is part of the "Symantec Event Handler," which is
actually a set of files named Symevnt.386, Symevnt1.dll, and S32evnt1.dll.
These Norton files monitor system information and report that information
to Norton AntiVirus and other Symantec utilities.

 

[bsobel]

The error in question usually occurs when another application has a driver installed, and that driver is improperly removed. Reinstalling Symevent registers the driver and fixes the problem. Did you recently uninstall anything that might have caused it?
Bill

 

[gustavo]

bsobel:

I did install some programs, but what´s "The virtual devices controller" or the SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers.VDD key anyway ?

What kind of programs could affect this key ?

Thanks both of you Gustavo.-

 

[Slikkster]

Here's a good place to start for info on what "virtual device drivers" are:

Virtual Device Drivers defined

 

[gustavo]

Slikkster:



<< In Windows, a virtual device driver is a program for each of the computer's main hardware devices, including the hard disk drive controller, keyboard, and serial and parallel ports. They're used to maintain the status of a hardware device that has changeable settings. Virtual device drivers handle software interrupts from the operating system rather than hardware interrupts.
A virtual device driver usually has a file name suffix of VXD. >>



Why is the symantec program the unique value under the SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers.VDD key ?

Norton Antivirus originates software interrupts like hardware interrupts ?

I installed the NVidia video driver, sound driver, and programs like office 2000, Microsoft Visual Studio, Genexus...

Thanks Gustavo.-

 

[Slikkster]

Now you're getting into areas that are somewhat out of my range of expertise. My *guess* is that this particular registry key deals with 16-bit device drivers. Windows 2000 prefers 32-bit drivers over 16-bit, so 16-bit drivers need to follow a certain set of rules. Your Symantec software driver might be 16-bit even though the name would suggest differently. In any event, the error occurs in the "16-bit Ms-Dos Subsystem".

The reason only Symantec info appears here is that your other hardware/software drivers probably are 32-bit (as I said, a guess).

Here's the exact information about this error from Microsoft, which I didn't find earlier. It shows you a different solution to the problem. However, if you're not experiencing the issue any more, you probably don't have to follow their instructions. You can if you wish, though:

Microsoft Resolution to this error

 

[bsobel]

> The reason only Symantec info appears here is that your other hardware/software drivers probably are 32-bit (as I said, a guess).

Symevent has both a 16 bit (to hook 16bit apps) and a 32 bit component. Again, some other software that was recently uninstalled corrupted that key (it's a common problem). Reinstalling Symevent fixes it as the installer fixes that key up.

Bill

 

[gustavo]

I have to say many thanks both of you.

I got a comprehensive explanation on the subject, now I know something new and interesting, beyond the specific problem that was a minor one.

My sincere acknowledgements.

Gustavo.-