Help! MS Dos Subsystem Missing VDD Error

[PistolPete]

I presently have Matlab 6.1 and LabView 6i installed on a system operating
under Windows XP. I had installed GPIB and removed it using the LabView
setup program.

When executing a dos command from Matlab, I would get a 16 Bit MS Dos
Subsystem Error that said the device driver GPIB-VDD.DLL was missing and it
was, which was probably caused by a sloppy LabView uninstall routine.

I went into the registery and removed the keys with this device driver
referenced. However, now when I have a system call from matlab, the same
error message appears except that it says,

\windows\system32\cmd.exe
\System\CurrentControlSet\Control\VirtualDeviceDrivers Virtual Device Driver
format in the registery invalid. At present there is no entry for
V
irtualDeviceDrivers. Should I add one and if I do what should I set the
value to?

In addition, I have a Win32 executable that does not generate this error
from the command prompt. It always generates this error from the Matlab
system call using DOS, SYSTEM, and !, which makes me think that Matlab
system commands are run in a 16 bit instead of a 32 bit mode. If there is a
way to execute 32 bit console applications from Matlab, it would remedy this
symptom.

Please e-mail me a copy of an reply posts.

TIA,

Pete

[PistolPete]

I figured it out. I was able to copy the VDD key from another system that
was working correctly. Just wish that uninstall programs would leave the
registery clean.

Pete

"Peter de B. Harrington" wrote in message
news:u8qumtog5g0mba@corp.supernews.com...
> I presently have Matlab 6.1 and LabView 6i installed on a system operating
> under Windows XP. I had installed GPIB and removed it using the LabView
> setup program.
>
> When executing a dos command from Matlab, I would get a 16 Bit MS Dos
> Subsystem Error that said the device driver GPIB-VDD.DLL was missing and
it
> was, which was probably caused by a sloppy LabView uninstall routine.
>
> I went into the registery and removed the keys with this device driver
> referenced. However, no
w when I have a system call from matlab, the same
> error message appears except that it says,
>
> \windows\system32\cmd.exe
> \System\CurrentControlSet\Control\VirtualDeviceDrivers Virtual Device
Driver
> format in the registery invalid. At present there is no entry for
> VirtualDeviceDrivers. Should I add one and if I do what should I set the
> value to?
>
> In addition, I have a Win32 executable that does not generate this error
> from the command prompt. It always generates this error from the Matlab
> system call using DOS, SYSTEM, and !, which makes me think that Matlab
> system commands are run in a 16 bit instead of a 32 bit mode. If there is
a
> way to execute 32 bit console applications from Matlab, it would remedy
this
> symptom.
>
> Please e-mail me a copy of an reply posts.
>
> TIA,
>
> Pete
>
>

[PistolPete]

I figured it out. I was able to copy the VDD key from another system that
was working correctly. Just wish that uninstall programs would leave the
registery clean.

Pete

"Peter de B. Harrington" wrote in message
news:u8qumtog5g0mba@corp.supernews.com...
> I presently have Matlab 6.1 and LabView 6i installed on a system operating
> under Windows XP. I had installed GPIB and removed it using the LabView
> setup program.
>
> When executing a dos command from Matlab, I would get a 16 Bit MS Dos
> Subsystem Error that said the device driver GPIB-VDD.DLL was missing and
it
> was, which was probably caused by a sloppy LabView uninstall routine.
>
> I went into the registery and removed the keys with this device driver
> referenced. However, no
w when I have a system call from matlab, the same
> error message appears except that it says,
>
> \windows\system32\cmd.exe
> \System\CurrentControlSet\Control\VirtualDeviceDrivers Virtual Device
Driver
> format in the registery invalid. At present there is no entry for
> VirtualDeviceDrivers. Should I add one and if I do what should I set the
> value to?
>
> In addition, I have a Win32 executable that does not generate this error
> from the command prompt. It always generates this error from the Matlab
> system call using DOS, SYSTEM, and !, which makes me think that Matlab
> system commands are run in a 16 bit instead of a 32 bit mode. If there is
a
> way to execute 32 bit console applications from Matlab, it would remedy
this
> symptom.
>
> Please e-mail me a copy of an reply posts.
>
> TIA,
>
> Pete
>
>

[motta]

yeah..yeah whatever mate

"Peter de B. Harrington" wrote:

> I figured it out. I was able to copy the VDD key from another system that
> was working correctly. Just wish that uninstall programs would leave the
> registery clean.
>
> Pete
>
> "Peter de B. Harrington" wrote in message
> news:u8qumtog5g0mba@corp.supernews.com...
> > I presently have Matlab 6.1 and LabView 6i installed on a system operating
> > under Windows XP. I had installed GPIB and removed it using the LabView
> > setup program.
> >
> > When executing a dos command from Matlab, I would get a 16 Bit MS Dos
> > Subsystem Error that said the device driver GPIB-VDD.DLL was missing and
> it
> > was, which was probably caused by a sloppy LabView uninstall routine.
> >
>
> I went into the registery and removed the keys with this device driver
> > referenced. However, now when I have a system call from matlab, the same
> > error message appears except that it says,
> >
> > \windows\system32\cmd.exe
> > \System\CurrentControlSet\Control\VirtualDeviceDrivers Virtual Device
> Driver
> > format in the registery invalid. At present there is no entry for
> > VirtualDeviceDrivers. Should I add one and if I do what should I set the
> > value to?
> >
> > In addition, I have a Win32 executable that does not generate this error
> > from the command prompt. It always generates this error from the Matlab
> > system call using DOS, SYSTEM, and !, which makes me think that Matlab
> > system commands are run in a 16 bit instead of a 32 bit mode. If there is
> a
> > way to execute 32 bit console applications from Matlab, it would remedy
> this
> > symptom.
> >
> > Please e-mail me a copy of an reply posts.
> >
> > TIA,
> >
> > Pete
> >
> >