"Invalid Drive Or Filename" When Accessing Ne

DocumentID: 601360
Revision Date: 29-Feb-96 1:28:40 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

Symptoms: Working on a MainLAN network, the customer is trying to access the I: drive with a stand-alone copy of WordPerfect 5.1. The customer is using the List Files (F5) feature. When the user tries to access the drive, the error message "Invalid Drive Or Filename" occurs. The user can access the I: drive through DOS and can create a file there. A customer installed WordPerfect on a MainLAN network. When the user typed WP to enter the program, the floppy disk lights came on, and the error "Insert WP 2 Disk Back In Drive" followed by "Can't Find Correct Copy Of WP.FIL. Enter Path" displayed. Even if the customer entered the network path to the WP.FIL, the error would repeat itself. Solutions: The customer was able to fix his problem by putting a LASTDRIVE= statement in his CONFIG.SYS file. Including a LASTDRIVE= statement in the CONFIG.SYS can also correct messages similar to "Put WordPerfect Disk Back In Drive A:." Users may want to specify LASTDRIVE=Z. Specifying Z will give the user the option of using drive letters A-Z. A customer running WP 5.1 DOS on a MainLAN network could get into WP fine from a nondedicated server, but received the error "Put WordPerfect 2 Disk Back In Drive" when starting the program from a workstation. Drive X: was being linked to the C:\WP51 directory on the server. It turns out that the customer had a LASTDRIVE=E command in the CONFIG.SYS file on the station. When the line was removed or changed to read LASTDRIVE=Z, WordPerfect could be entered without the error. Another customer under the same circumstances receiving the "Put WP 2 Disk Back In Drive" error did not have the LASTDRIVE command in the CONFIG.SYS file. Adding the command corrected the problem. A user on a MainLAN network received the error "Invalid Drive Path Specification" when changing directories to the F: or G: drive in List Files. The user corrected the problem by entering the line LASTDRIVE=Z into the CONFIG.SYS file and rebooting. FYI: Another customer that was unable to print from one workstation on a MainLAN network added a LASTDRIVE statement, and the problem did not recur. While adding a LASTDRIVE statement may have solved the problem, the reason that it did was attributed to the change in environment space that occurred on the machine when adding the LASTDRIVE statement.

Answer:

Details:

Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER.