Click filename to download:
map312.exe; 48964 bytes; Date/Time: 03-13-1995/11:57AM

Mapping a search drive in 1st private DOS box in Windows creates a invalid search drive in 2nd private DOS box. This update also corrects a problem with remapping over a NetWare drive with MAP.EXE.

NOTE: Always make a backup of applicable files before applying new fixes.

1) Flag MAP.EXE contained in the PUBLIC directory normal or sharable, read/write.

2) Rename MAP.EXE contained in the PUBLIC directory to MAP.ORG to allow an original copy.

3) Copy the MAP.EXE provided with this update into the PUBLIC directory.

4) Flag the new MAP.EXE sharable, read only.

X_Verified by customer
X_Verified by Novell

1 Mapping a search drive in a private dos box appears invalid in a second private dos box. The characteristics of the invalid search drive in the second DOS box is always mapped to the root of the volume and does not really function.

Attempting to change to the invalid drive reports the message Invalid drive specification. When attempting to add a search drive by using MAP S16:= ..., the last search drive appears again.

Two occurrences of the same search drive now exist, one is invalid, the other is not. Trying to delete the search drive in the 2nd dos box and then exiting the 2nd dos box, will cause the search drive with the same letter in the 1st DOS box to be re-mapped as a regular mapped drive, not a search drive. In some cases the Z:\PUBLIC directory that was a search drive becomes a regular drive mapping, thus losing access to NetWare utilities.

Symptom:

2 Customer is trying to remap over a NetWare drive with MAP.EXE 3.75 PTF and gets the following error:

 H:\>C:

 C:\TEST>map H:=SERVER1\SYS:

 The following command could not be completed:
      H:=SERVER1\SYS:
      Attempt to map drive over non-NetWare redirected drive or
           to JOINed orSUBSTed drive.

2.1 Apply updated MAP.EXE contained in MAP312.EXE. The updated MAP.EXE will not modify the Master Windows environment, only the local environment. Therefore, the problem does not get carried over into other private DOS VM (Virtual Machines).

Self-Extracting File Name: MAP312.EXE Revision: B

Files Included Size Date Time

\
  MAP312.TXT (This File)
     MAP.EXE 51701 12-16-94 2:10p

Installation Instructions:

NOTE: Always make a backup of applicable files before applying new fixes.

1) Flag MAP.EXE contained in the PUBLIC directory normal or sharable, read/write.

2) Rename MAP.EXE contained in the PUBLIC directory to MAP.ORG to allow an original copy.

3) Copy the MAP.EXE provided with this update into the PUBLIC directory.

4) Flag the new MAP.EXE sharable, read only.

X_Verified by customer
X_Verified by Novell

Self-Extracting File Name:  map312.exe

Files Included       Size   Date         Time    Version   Checksum

\
       MAP.EXE      51701   12-16-1994   02:10PM
    MAP312.TXT       3595   03-13-1995   11:57AM