PRB: D2027 or D1001 Error: Cannot Execute '<Path>Filename' (49497)


The information in this article applies to:

  • Microsoft FORTRAN Compiler for MS-DOS 4.0
  • Microsoft FORTRAN Compiler for MS-DOS 4.01
  • Microsoft FORTRAN Compiler for MS-DOS 4.1
  • Microsoft FORTRAN Compiler for MS-DOS 5.0
  • Microsoft FORTRAN Compiler for MS-DOS 5.1
  • Microsoft FORTRAN compiler for OS/2 4.0
  • Microsoft FORTRAN compiler for OS/2 4.01
  • Microsoft FORTRAN compiler for OS/2 4.1
  • Microsoft FORTRAN compiler for OS/2 5.0
  • Microsoft FORTRAN compiler for OS/2 5.1
This article was previously published under Q49497

SYMPTOMS

An attempt to compile an application fails and the compiler generates one of the following messages. In FORTRAN version 5.1:
Command line error D2027 : cannot execute
'C:\FORTRAN\BINB\f1.exe'
In FORTRAN version 5.0:
Command line error D2027:could not execute
'C:\FORTRAN\BINB\f1.exe'
In FORTRAN versions 4.0, 4.01, and 4.1:
Command line fatal error D1001 : could not execute
'C:\FORTRAN\BINB\f1.exe'

CAUSE

These errors occur under the following four conditions:

  • The system cannot find the F1.EXE file. This condition can be caused by a terminate-and-stay-resident (TSR) program that alters the setting of the PATH environment variable. -or-

  • Insufficient memory is available. If you are running PWBED.EXE instead of PWB.COM, it is possible that there is not enough memory left to build the application. -or-

  • The EXE file is corrupt or it has an illegal EXE file format. -or-

  • The installed version of MS-DOS and the COMMAND.COM file are incompatible. If the MS-DOS and COMMAND.COM version numbers are identical, the compiler may not successfully open the intermediate file in the TMP directory.

RESOLUTION

The corresponding techniques to address the four conditions above are as follows:

  • Modify your AUTOEXEC.BAT file (CONFIG.SYS file in OS/2) to remove as many TSR programs and special device drivers as possible.
  • Use the MEM command to check available memory. FORTRAN requires at least 320K memory free (512K recommended).
  • If the F1.EXE program is corrupted, make a fresh copy from the distribution disks.
  • If the VER.EXE utility and COMMAND.COM do not report identical version numbers and manufacturers, reinstall the operating system or obtain the correct version of COMMAND.COM.
Modification Type:MajorLast Reviewed:12/1/2003
Keywords:KB49497
©2003 Microsoft Corporation. All rights reserved.