asked on

16 bit apps no longer loading properly...

In one of my Win2K machines, no 16 bit app will load correctly without ignoring a .pif file causing a registry error in System\CurrentControlSet\Control\VirtualDeviceDrivers. It says the Virtual Device Driver format in the registry is invalid. In that registry location there is a default value and one put there by symantec (NAV 2002 I assume).

As the main POS/Inventory software is 16 bit DOS run in Windows, this functionality is critical. Advice is greatly appreciated.

YarnoSG

We had that in our environment
it was AFTER the upgrade from NAV 5 to NAV 7...

Copy this into FIX16.REG:_____________________
REGEDIT4

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers]
"VDD"=hex(7):00
_________________________End of REG File

This file cleans out whatever is in VirtualDeviceDrivers, and replaces it with an empty VDD key (as it should be in NT/2000/XP)

Apply this to your machines by double clicking, or putting:

REGEDIT /S FIX16.reg

into your login scripts.

ASKER CERTIFIED SOLUTION

YarnoSG

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

YarnoSG

By POS, I assume you mean Point Of Sale, not Piece Of .............

fooslin

ASKER

Thx. I'd like to try this but my expertise is insufficient to interpret your advice. I have some experience with regedit but no the login scripts to which you refer. Might there be a way to clarify your suggestions for a less sophisticated user?

Thanks a lot!!

YarnoSG

Between the lines above, "copy"
open up notepad
Paste
save as "Fix16.reg"

put this file where your people can get to it (shared network drive)

Tell them to go double-click it, and select "yes".
The fix will be in place at the next reboot.

Don't worry about the login script suggestion, it was just an alternate deployment strategy.

fooslin

ASKER

Thanks for the clarification. I ended up following the advice in the following link and it removed the error msg (tho there's still something fishy going in in that blasted box...)...

http://support.microsoft.com/default.aspx?scid=kb;en-us;254914

Thanks again.

YarnoSG

That is EXACTLY what this REG file will do; you may want to cut&paste it & save for the future if it happens again.

Define "Fishy"; maybe we can help...