BUG: Setup Always Copies Real-Mode Executable Version

 Last reviewed: July 11, 1995
Article ID: Q84732
The information in this article applies to:
  • Microsoft FORTRAN for MS-DOS, version 5.1
  • Microsoft FORTRAN for OS/2, version 5.1

SYMPTOMS

When coping a single file from the distribution disks using the Microsoft FORTRAN version 5.1 Setup program, the real-mode version of any executable will be copied if that executable name is identical for both real- and protected-mode versions. The user is given a choice within the Setup program whether to copy the real- or protected-mode version, but the real- mode version is always copied regardless of the selection. The most common problems occur with the files NMAKE.EXE and QH.EXE.

CAUSE

The Setup program appears to always search first in the current directory for the file to be copied. Because Setup is started with disk 1, disk 1 is searched first. Disk 1 also contains the real-mode versions of all the executable files.

RESOLUTION

To copy the protect-mode version of an executable using the FORTRAN 5.1 Setup program, remove disk 1 from the floppy drive after starting the Setup program but before copying the OS/2 version of the file. Replace disk 1 with disk 3 in the drive, then proceed as usual with the Setup program.

STATUS

Microsoft has confirmed this to be a problem in Microsoft FORTRAN version 5.1 for MS-DOS and OS/2.

Additional reference words: 5.10
KBCategory: kbsetup kbbuglist
KBSubcategory: f51setup

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 11, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.