Article ID: 217171 - View products that this article applies to.
This article was previously published under Q217171
This article has been archived. It is offered "as is" and will no longer be updated.
A Virtual Device Driver (VxD) or driver built with Visual C++ fails to load or run.
The /ZI compiler option (debug info for Edit and Continue) uses the the compiler option /GF (constant string pooling) which places strings in .rdata. It is the presence of .rdata that causes the VxDs to fail. This option is turned on by default when a project is ported from Visual C++ version 5.0 to version 6.0.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/194022/EN-US/ )INFO: Visual Studio 6.0 Service Packs, What, Where, Why
(https://support.microsoft.com/kb/194295/EN-US/ )HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
The Visual C++ 6.0 Service Pack 3 linker generates the following warnings:
LNK4075: ignoring /EDITANDCONTINUE due to /VXD specification
LNK4212: Section "section_name" has an unknown VxD section type; image may not load
Article ID: 217171 - Last Review: February 21, 2014 - Revision: 2.0