Microsoft KB Archive/130817: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
(3 intermediate revisions by the same user not shown)
Line 27: Line 27:
<blockquote><div class="ERRORMESSAGE">
<blockquote><div class="ERRORMESSAGE">


<pre class="FIXEDTEXT">  &quot;The MMD.386 virtual device driver is not loaded in Windows.
<pre class="FIXEDTEXT">  "The MMD.386 virtual device driver is not loaded in Windows.
   Ensure that the line 'DEVICE = &lt;Directory Specified in Setup for
   Ensure that the line 'DEVICE = <Directory Specified in Setup for
   Binaries&gt;\MMD.386' exists in your SYSTEM.INI [386Enh] section.&quot; </pre>
   Binaries>\MMD.386' exists in your SYSTEM.INI [386Enh] section." </pre>


</div></blockquote>
</div></blockquote>
Line 44: Line 44:
Please see the following Windows NT article in the Microsoft Knowledge Base:
Please see the following Windows NT article in the Microsoft Knowledge Base:


<blockquote>[[mk:@MSITStore:kbwinnt.chm::/Source/winnt/q103621|Q103621]] Running Visual C++ for Windows with Windows NT</blockquote>
<blockquote>[[../103621|Q103621]] Running Visual C++ for Windows with Windows NT</blockquote>
<br />
<br />



Latest revision as of 10:01, 21 July 2020

PRB: Device MMD.386 Not Loaded w/ Visual C++ 1.0 on Windows NT

Q130817



The information in this article applies to:


  • Microsoft Visual C++, version 1.0
  • Microsoft Fortran Powerstation 32 for Windows NT, version 1.0





SYMPTOMS

When attempting to compile from the development environment while running on Windows NT you receive the following message stating that MMD.386 is not loaded.

   "The MMD.386 virtual device driver is not loaded in Windows.
   Ensure that the line 'DEVICE = <Directory Specified in Setup for
   Binaries>\MMD.386' exists in your SYSTEM.INI [386Enh] section." 



CAUSE

The error message is correct. MMD.386 is a Virtual device driver (VxD) designed for 16-bit Windows, so Windows NT does not load or execute these VxD files. Therefore, you cannot compile from within the development environment on Windows NT.

However, if you obtain the B2FIX patch, you can use the command-line tools in a console session under Windows NT. In this way, you can still use the development environment and Wizards. Then go to a console session, and execute the \MSVC\BIN\MSVCVARS.BAT file to set your environment variables and use NMAKE.EXE on the makefile produced by the development environment. For example:

    namke /f project.mak 

Please see the following Windows NT article in the Microsoft Knowledge Base:

Q103621 Running Visual C++ for Windows with Windows NT



RESOLUTION

This is no longer a problem with Visual C++ for Windows, version 1.5 and later.

Additional query words: 1.00

Keywords : kb16bitonly kbide kbVC kbprb
Issue type : kbprb
Technology : kbVCsearch kbAudDeveloper kbFortranSearch kbvc100 kbZNotKeyword2 kbFORTRANPower32100NT


Last Reviewed: June 4, 2001
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.