Thanks Rob, the link gives advice on MS DOS and not Windows. As to the Registry, I don't even know what it IS - let alone know how to open it (or even find it)! Thanks anyway mate.
Main Topics
Browse All TopicsWhen trying to load a game on cd I get the message "C:\PROGRA~1\Symantec\S32E
An installable Virtual Device Driver failed Dll initialization. Choose close to terminate the application. How can I fix this?
I am complet4ely computer illiterate and don't know my DOS from my elbow - please help me STEP BY STEP or I won't have a clue :( I am running Windows XP home edition SP2 and some time back uninstalled (with help) all the Symantec stuff on my system as I didn't want their antivirus or firewall any longer. Thanks for any help you can offer.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
delthebuilder,
Your title was 16bit Windows subsystem...
A 16 bit application is a DOS application. For some reason you get the error you mentioned when tying to do anything that accesses a DOS Window from within Windows. The way to fix it, at least this works in most cases, is to make a change in the "Registry" Here is where I kind of "ducked" the question. Editing the registry which contains thousands or references to program and file information is not terribly difficult, but a little slip up and you can make your system unusable. Therefore I tried to pass the buck to Microsoft. I'll give you some more details but please be careful as I say it can completely lock up your system. You may want to search your Microsoft help files or the internet on backing up the registry before you start.
To access the registry go to the start button and then choose Run. In the run box enter regedit
This will open the registry editor. On the left of each item you will see a '+' click on this to expand the item you want to edit. By clicking on the +'s work your way through to the following location:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Control
VirtualDeviceDrivers
Click on 'VirtualDeviceDrivers' and in the right pane you will see VDD
Right click on this and choose delete
In the blank space where VDD was, right click and choose New 'Multi-String Value'
A new String value icon will appear and a space to enter a name. Enter VDD and click enter
If you cannot enter a name right click on the new String Value and choose rename, enter the VDD name, and click enter
The data field will be left blank, which it should be.
Exit the registry editor and restart your system.
See if that fixes the problem.
Note: you can back up just that registry "Key" by right clicking on VirtualDeviceDrivers an choose export, then enter a location and name to save it. I would recomend doing at least this if not a full registry back up if you are not comfortable with doing the above procedure. Go step by step and it is very straight forward.
Hope this helps you out,
--Rob
Hi Rob. UH OH!!! Did as you said as far as HKEY_LOCAL_MACHINE, there was a - beside it instead of a + ....... but what the hell. I clicked on it and didn't find SYSTEM, I found HARDWARE, SAM, SECURITY, SOFTWARE all below it. Where did I go wrong? (Bought a computer in the first place!) Any offers? Bet you wish you hadn't answered now! Ha!
delthebuilder,
Should be there. Windows XP right?
The System folder should be below the Software folder. It's the 5th and last sub-folder of the HKEY_LOCAL_MACHINE folder.
Pressing '-' or '+' is fine it just expands and contract the list of items within the folder. If there was a '-' means sombody opened something at one point, as it saves the view from last time. Try clicking '-' on the Software folder or just keep scaning down untill you find the System Folder.
>>"Bet you wish you hadn't answered now! Ha"
Not at all, glad to help. Simple answers are no fun. I am verbaly impared <G> so it is good practice too.
Try again and let me know how you make out.
RobWill could have a solution, but I finnd more often than not this error is caused by another problem - a corrupt config.nt or autoexec.nt file.
You can try fixing it by copying these files from C:\WINDOWS\REPAIR to C:\WINDOWS\SYSTEM32. That's it. Just copy the files (note: these files may be hidden, you may need to set Windows to show hidden files).
Try copying these files and then running the program. While again, it could be the problem RobWill has pointed out, I'm fairly confident this will solve it for you.
Leew,
I agree I have seen it numerous times, but just recently noticed there are 3 different errors. Basically the same error but one refers to autoexec.nt, one config.nt (both of which replacing the files, fixes) and thirdly referring to a .dll, such as here, which Microsoft recommends this repair. Seems to work, for the .dll but won't for the other 2.
delthebuilder,
Glad you are up and running, Thanks for the points.
--Rob
Business Accounts
Answer for Membership
by: RobWillPosted on 2005-09-02 at 08:33:45ID: 14811081
The link below should tell you how to fix it with step by step instructions: om/default .aspx?scid =KB;EN- US; q254914&
http://support.microsoft.c