W2K VDD error popup, fixed gpib-vdd.dll, now cmd.exe broken

[CF]

Ok,
I still got a nagging error I can't get rid of.

16 bit MS-DOS Subsystem virtual device driver failed dll initialization
popup error and it won't got away on my windows 2000 (W2K) system.

I used the Microsoft KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;254914&Product=win2000#appliesto

to get rid of the previous error that I will repeat here for google search
hits:
16 Bit MS-DOS Subsystem
C:\WINNT\system32\command.com
gpib-vdd.dll. An installable Virtual Device Driver failed Dll
initialization...
(this was probably from a national instruments install / uninstall)

I was able to get rid of the message about the gpib-vdd.
I deleted the registry line referenced in the KB article

However now I get a new message every time I try to run a 16 bit program
from a cmd window
e.g C:\>edit

I have already tried deleting and recreating the registry entry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD

and the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers

Now I get:
16 Bit MS-DOS Subsystem
CMD.EXE - edit
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. VDD. Virtual device
driver format in the registry is invalid...
close ... ignore ...

I get the popup whenever I run a dos type programm,
or and automatic driver install occurs,
or I plug in a new USB device,
or I intall software that comes with a device driver

Can't get rid of the problem



(I pasted this article below for google search hits so others can find this
real easy, I hope someone's got the answer)
----------------------------------------------------------------------------
------------------------------

Microsoft Knowledge Base Article - 254914
----------------------------------------------------------------------------
------------------------------

Search Support (KB)
Windows 2000

Virtual Device Driver Error Message in 16-Bit MS-DOS Subsystem
View products that this article applies to.
This article was previously published under Q254914
a
SYMPTOMS
After you install some programs, one of the following error messages may
appear when you attempt to run 16-bit programs:

16 bit MS-DOS Subsystem
drive:\program path
XXXX. An installable Virtual Device Driver failed DLL initialization. Choose
'Close' to terminate the application.
-or-



16 bit MS-DOS Subsystem
drive:\program path
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. VDD. Virtual Device
Driver format in the registry is invalid. Choose 'Close' to terminate the
application.
In some cases, clicking Ignore allows the program to run properly, but the
error message continues to be displayed when you start 16-bit programs.

CAUSE
This behavior can occur if the following registry value has become
corrupted:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD

This issue may occur after you install a 16-bit program, or a program that
uses a 16-bit installation program, that is not Windows 2000 compliant.

RESOLUTION
Start Registry Editor (Regedt32.exe).
Locate and click the following value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD

On the Edit menu, click Delete.
On the Edit menu, click Add Value.
Type VDD in the Value Name box, click REG_MULTI_SZ for the Data Type, and
then click OK.
The Multi-String editor appears. Leave this entry blank and click OK.
Quit Registry Editor.


If the above steps do not work, or if you are unable to create the VDD key,
it may be necessary to also delete and recreate the whole
VirtualDeviceDrivers registry key.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.
MORE INFORMATION
These error messages can also occur in Microsoft Windows NT 4.0 if this key
is manually deleted for testing purposes.
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional
Microsoft Windows NT Workstation 4.0
Last Reviewed: 6/3/2003 (2.0)
Keywords: kb3rdparty kbAppDev kberrmsg kbprb w2000apps KB254914

 

[Jim Byrd]

Hi CF - When you create the VDD entry you MUST have Admin privileges, you
MUST use Regedt32, and you must use REG_MULTI_SZ for the Data Type. Did you
satisfy all that? I suspect not, and that that's why you're getting that
error.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

 

[CF]

Hi Jim,
That worked!
I screwed up by using regedit instead of regedt32 as you spec'd below.
(I didn't read: Start Registry Editor (Regedt32.exe). )
regedit won't create the REG_MULTI_SZ for the Data Type.
Thanks.
Carl

 

[Jim Byrd]

YW, Carl - I thought that might be the problem. Glad you've gotten it
straightened out.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Hi Jim,
That worked!
I screwed up by using regedit instead of regedt32 as you spec'd below.
(I didn't read: Start Registry Editor (Regedt32.exe). )
regedit won't create the REG_MULTI_SZ for the Data Type.
Thanks.
Carl

Hi CF - When you create the VDD entry you MUST have Admin privileges, you
MUST use Regedt32, and you must use REG_MULTI_SZ for the Data Type. Did you
satisfy all that? I suspect not, and that that's why you're getting that
error.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

http://support.microsoft.com/defaul...ntControlSet\Control\VirtualDeviceDrivers\VDD

------------------------------------------------------------------------- -

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDDHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD