Article ID: 108165 - View products that this article applies to.
This article was previously published under Q108165
This article has been archived. It is offered "as is" and will no longer be updated.
Mainframe workstation software that maps drives D and E to hold them for future use when using emulation will cause the following error message to appear when a disk drive cannot be read:
Use of the MS-DOS Interlnk program and the INTERSVR command is also a source of this message. Interlnk's drive mapping redirects the client system's drives to the next available drive letters of the server. If INTERLNK.EXE is loaded in the CONFIG.SYS file of the client and the server PC is then disconnected, FoxPro will be told that sequential drive mapping exists, when, in fact, there will be no response when FoxPro checks the drives in sequence that were on the connected PC.
Cannot read from drive <drive letter>.
Some FoxPro operations appear to scan all consecutive disk drives.
The following operations have been reported to cause this error on computers with a drive that cannot be read:
Reassign the drive letter of the device that cannot be read so that it is not in consecutive order with the other drives.
For example, if drive C is a hard disk drive, and drive D is a CD-ROM drive that causes the error message when it does not contain a disc, reassign the CD-ROM drive letter to drive Z.
You may need to either consult the manual for your CD-ROM drive or use the MS-DOS SUBST command. NOTE: Reassigning the drive letter may require the use of the LASTDRIVE=<drive letter> command in the CONFIG.SYS file.
The following hardware configurations may cause a disk drive to report that it cannot be read:
Article ID: 108165 - Last Review: February 27, 2014 - Revision: 2.1