Discussion Locked

NT 16-bit support

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Situation:

Enterprise Environment, Win9X, WinNT and Win2K client platforms. Over 9,000 users.

Support:

different IS teams for each department. Therefore different profiles are being installed, and different default profiles are being installed on various WinNT 4.0 desktops.

Issue:

16-bit ODBC and Win 16 support for some desktops have caused 16 apps to malfunction. we've located the issue as the 16 bit profiles aren't visible in the registry, and 16-bit ODBC ADM can't manage the proper DLLs because the 16-bit ODBC ADM only sees the 32-bit DLLs.

Question:

No matter how many times I create/recreate a profile, the prompt to ask me to migrate 16-bit support doesn't appear prior to the logon prompt. How do I resolve this issue? I need to be able to migrate 16-bit apps over to a profile that supports the 16-bit ODBC ADM; so that the 16-bit ODBC ADM also sees 16-bit ODBC instead of just 32-bit ODBC DLLs. Please send all responses to AnthonyBernardino@Engineer.com.

1 reply

by jeff anderson

Don't know if this will help but I have used this to resolve other 16bit problems. I went into the registry and searched for the following path Defaultseparatevdm and changed all the values (3 or 4 of them) to 1.
This makes 16bit apps run in a separate memory. Hope this helps.

This discussion is closed to new replies.