ms-dos 16 bit error

[Guest]

Running xp pro sp2 and-
Trying to install Security Update for Windows XP (KB920670)
First I got Virtual Device Driver failed DLL initialization so I went to
http://support.microsoft.com/kb/314452 and change the VOD as described
now I get Virtual Device Driver format in the registry is invalid.
The next step was to check the command.com which is supposed to be
Size Date Time
------------------------------
50620 08-23-2001 4:00 A.M.
mine is 50 kb 3/31/2003
Then I read about deleting the avast line in autoexec.nt and did that
to no avail.
What can I do now?

 

[Guest]

Went over it all again and I had made a typo in the registry VOD for VDD.
Corrected that, tried update again. Now fails with-
0x80242FFF error.
present status is Registry ok and avast line commented out in config.nt
any suggestions

 

[Wesley Vogel]

In the 16 bit MS-DOS Subsystem error, what is the program name and path?

This does not work with all error messages, but it does with most.

To copy an error message...
When the error message pops up, click on it to make sure that it has focus.
Hit Ctrl + C to copy the message.
Use Ctrl + V or right click and select Paste to paste into a message or
Notepad or whatever.

For example...
---------------------------
C:\WINDOWS\system32\command.com
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

I think I solved the problem. Read elsewhere to delete all the files in
Windows\SoftwareDistribution\Downloads, so I did. There were a lot of
folders and files. Then I did a custom update, chose the only critical
offered and it installed successfully. Not sure why this worked but suppose
the file had become corrupted somehow in my thrashing around. Thanks for
responding

Henry

 

[Wesley Vogel]

Glad you got it worked out. But I am still trying to figure out WTF 16 Bit
MS-DOS Subsystem had to do with anything.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

That was the first error message, and I think it was caused by Avast changing
the config.nt which I remd out but complicated the problem by mis-spelling
VDD and that screwed up the file which gave the next set of error messages
which was solved by deleting the download. Sort of a cascading screw up.

 

[Wesley Vogel]

You may care nothing about any of this since you seem to have your problem
fixed.

Config.nt and autoexec.nt only affect command.com which is 16-bit. The 16
Bit MS-DOS Subsystem uses command.com. Config.nt or autoexec.nt have no
affect on cmd.exe, the Windows Command Processor which is 32-bit.

Anytime that a 16-bit program runs in NT, ntvdm.exe and wowexec.exe (the
Windows on Windows subsystem) will appear in the Task Manager. If you start
command.com, ntvdm.exe will appear in the Task Manager under the Processes
tab and MS-DOS Prompt will appear under the Applications tab. In Task
Manager if you right click MS-DOS Prompt and select Go To Process, the
Processes tab will open with ntvdm.exe highlighted.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers
Value Name: VDD
Data Type: REG_MULTI_SZ
Value Data: Filenames (By default this is blank with no entries.)

VDD is Virtual Device Drivers.

The registry key above stores the device drivers that are used in an NTVDM
session. NTVDM is ntvdm.exe, the Windows NT Virtual MS-DOS Machine.
wowexec.exe is used in conjunction with ntvdm.exe to run old DOS 16-bit
applications. wowexec.exe is the Windows Win16 Application Launcher or
Windows On Windows Execution Process or Windows on Windows subsystem.
16-bit programs run in the NTVDM in an extra software layer called the Win16
on Win32 (WOW) layer. wowexec.exe is started by ntvdm.exe, which starts
every time you run a 16-bit program.

Is Avast a 16-bit program?

Do you see why I was wondering what the 16 Bit MS-DOS Subsystem had to do
with anything.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In