PRB: Phar Lap Error 58 Running Visual C++ on Read-Only DriveLast reviewed: September 1, 1995Article ID: Q107495 |
The information in this article applies to:
SYMPTOMSAn attempt to execute NMAKE.EXE, CL.EXE, LINK.EXE, or MASM.EXE in MS-DOS when Windows is not running fails and generates the following message:
Phar Lap err 58: Can't create VM swap file of size 0 in directory <root directory name>:\H2INC.EXE and CREF.EXE that ship with MASM version 6.11 generate the same error. This error does not occur when running in an MS-DOS window under Microsoft Windows or Microsoft Windows NT. With Visual C++ for Windows and MASM version 6.1a, the error can also occur when the TMP environment variable is invalid or points to a read-only drive. For additional information about the TMP problem, please search in the Microsoft Knowledge Base on the following words:
Phar Lap RW1016 CAUSEVisual C++ is installed on a read-only drive, possibly a network drive. The error occurs because the DOSXNT MS-DOS extender attempts to create a virtual memory swap file on the drive DOSXNT runs from when the operating system does not support virtual memory.
RESOLUTIONTo work around this problem, you can run DOSXNT on a read/write drive listed in your PATH MS-DOS environment variable. Or you can specify one of the following environment variable settings to prevent DOSXNT from attempting to create a swap file on the read-only network drive:
|
Additional reference words: PharLap DOSXNT 1.00 1.50 6.10 6.10a
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |