MAP Command Summary.
(Last modified: 19Feb2003)
This document (10027779) is provided subject to the disclaimer at the end of this document.
goal
MAP Command Summary.
How to create login scripts
fact
Formerly TID 2911562
fix
Issue
Description: The MAP command can be used to achieve several different results. MAP is used to do the following: To view current drive mappings, create or change network drive mappings, create or change search drive mappings, map a drive to a fake root directory, or map the next available drive.
Syntax: The syntax of MAP for 3.1x and 4.1 are as follows:
NetWare 3.1x MAP
Command Format: Create or change network drive mappings
MAP path MAP drive: = [ drive: | path] MAP [ option] drive:
Create or change search drive mappings
MAP [option] drive: = [drive:path]
Map a drive to a fake root directory
MAP [ROOT] drive:= [drive: | path]
Replace drive with the drive letter mapped to the directory you want to work with.
Replace path with the directory path you want to work with.
Replace option with one of the command options listed later in this document.
Include ROOT to map a drive to a fake root directory.
Command Options: INS[ert]: Use this option to change search drive mappings.
DEL[ete]: Use this option to delete a default, network, or search drive mapping.
REM[ove]: Use this option to delete a default, network, or search drive mapping.
N[ext]: Use this option to map the next available drive to a specified path. To execute this option, type: MAP n[ext] path name <Enter>
Additional Information
Some software applications write files to and read files from the root directory only. Because users do not have rights in the root directory, they cannot retrieve or write to files they create in those applications. NetWare v3.x allows users to map a drive to a fake root directory where they have the rights they need.
Drive mappings are temporary. They are deleted when you log out or turn off your workstation. Drives mapped to fake root directories are also deleted.
You can save drive mappings---including fake root mappings---in your login script if you want them to be invoked each time you log in.
If you attempt to map a local drive to a network directory path, a prompt similar to the following appears on your workstation screen:
Drive B: currently maps to a local disk
Do you want to assign it as a network drive? (Y/N) Y
If you want to assign the drive letter to a network drive, answer "Yes."
View Current Drive Mappings
View all mappings type: MAP <Enter>
You see information similar to the following:
Drive A: maps to a local drive
Drive B: maps to a local drive
Drive F:= COUNT/SYS: /HOME/KAREN
Drive G:= COUNT/SYS: /
Drive H:= COUNT/ACCT: /ACCDATA
SEARCH1:=Z:. [COUNT/SYS: /PUBLIC]
SEARCH2:=Y:. [COUNT/SYS: /PUBLIC/WP]
SEARCH3:=X:. [COUNT/ACCT: /ACCREC]
View Specific Mappings
To view the mapping of drive F:, specify that drive in the command:
MAP F: <Enter>
You see information similar to the following:
Drive F:= COUNT/SYS: /HOME/KAREN
Create or Change a Drive Mapping
Suppose you are user KAREN on file server COUNT. To create or change a drive mapping, complete one of the following:
Create a Default Mapping
To map drive G: to your home directory and use it as your default directory, type
MAP G: = COUNT/SYS:HOME/KAREN <Enter>
Create a Network Mapping
Suppose you want to map a network drive to a directory in which you have files. To see what network drive letters are available, type
MAP <Enter>
Choose a drive letter that is not being used, such as drive J:. Type
MAP J: = path <Enter>
Replace path with the directory path leading to the files to which you want network drive J: mapped.
Extend a Mapping
To extend the mapping for drive G: (your default drive) from COUNT/SYS to COUNT/SYS:HOME/KAREN, type
MAP HOME/KAREN <Enter>
Remap Your Default Drive
Suppose your default drive is mapped as Drive G: = COUNT/SYS:. You want to remap drive G: as Drive G: = COUNT/ACCT:ACCDATA type
MAP ACCT:ACCDATA <Enter>
Because file server COUNT is your default file server, you do not have to include COUNT in the MAP command.
Map to another Volume
To map drive M: to the PUBLIC directory in volume SYS on your default file server COUNT, type
MAP M: = SYS:PUBLIC <Enter>
If file server COUNT is not your default file server, you must include the file server name in your command:
MAP M: = COUNT/SYS:PUBLIC <Enter>
If another drive, such as drive Z:, is already mapped to COUNT/SYS:PUBLIC, you can type
MAP M: = Z: <Enter>
Map to Your Default Drive
You can map network drives to the same path as your default drive. Suppose your default drive is drive G: mapped to volume SYS: on file server COUNT as follows:
Drive G: = COUNT/SYS:
To map a network drive (for example, drive P:) to the same path as your default drive (drive G:), change to your default drive and type
MAP P: = G: <Enter>
Delete a Network Drive Mapping
To delete network drive G:, type: MAP DEL G: <Enter> or MAP REM G: <Enter>
Create or Change Search Drive Mappings
You can create, modify, or delete a search drive mapping. Complete one of the following:
Create a Search Drive Mapping
Suppose you are user TERRY and your search drives appear as follows:
SEARCH1:=Z:. [COUNT/SYS: /PUBLIC]
SEARCH2:=Y:. [COUNT/SYS: /PUBLIC/WP]
The next available search drive is SEARCH3 (S3). To map a search drive to directory ACCREC on volume ACCT:, type
MAP S3: = COUNT/ACCT:ACCREC <Enter>
When you type MAP again, you see that the new search drive mapping has been added:
SEARCH1:=Z:. [COUNT/SYS: /PUBLIC]
SEARCH2:=Y:. [COUNT/SYS: /PUBLIC/WP]
SEARCH3:=X:. [COUNT/ACCT: /ACCREC]
Change a Search Drive Mapping
Suppose that you want to remap search drive 3 so that instead of searching drive X: mapped to COUNT/ACCT:ACCREC, search drive 3 searches the next available drive letter mapped to COUNT/SYS:HOME/TERRY.
To remap search drive 3 in this way, use one of the following commands:
MAP S3: = COUNT/SYS:HOME/TERRY <Enter> or MAP INS S3: = COUNT/SYS:HOME/TERRY <Enter>
The first command converts drive X: to a regular network drive and reassigns search drive 3 to the next available drive letter (in this case, drive W:) mapped to COUNT/SYS:HOME/TERRY:
Drive X:= COUNT/ACCT: /ACCREC
SEARCH1:=Z:. [COUNT/SYS: /PUBLIC]
SEARCH2:=Y:. [COUNT/SYS: /PUBLIC/WP]
SEARCH3:=W:. [COUNT/SYS: /HOME/TERRY]
The second command reassigns drive X: from search drive 3 to search drive 4, leaving search drive 3 temporarily vacant. Then the command inserts the next available drive (in this case, drive W:) mapped to COUNT/SYS:HOME/TERRY into the vacancy:
SEARCH1:=Z:. [COUNT/SYS: /PUBLIC]
SEARCH2:=Y:. [COUNT/SYS: /PUBLIC/WP]
SEARCH3:=W:. [COUNT/SYS: /HOME/TERRY]
SEARCH4:=X:. [COUNT/ACCT: /ACCREC]
Map to another File Server
Suppose you are attached to file servers COUNT and MKTG. Your default server is COUNT, but you need to create a fake root directory on server MKTG so you can use accounting applications. Your drive mapping to accounting applications on server MKTG is as follows:
H: = MKTG/SYS:ACCT/TERRY
From any drive on server COUNT, type
MAP ROOT H: = MKTG/SYS:ACCT/TERRY <Enter>
Change to server MKTG and type MAP. You see the following.
H:=MKTG/SYS:ACCT/TERRY /
.
NetWare 4.1 MAP
Command Format: MAP [P | NP] [option...] drive:= [drive: | path] [/? | /VER]
Parameters: (no parameter) View drive mappings.
P Map to a physical volume. Must be listed first or second.
NP Overwrite local or search drives without being prompted. Must be listed first or second.
option Replace option with any available option.
drive: Specify the drive you want to change.
path Specify the path you want to map a drive to. To map to a physical volume on a server that is not your default server, specify the entire path (including server, volume, and directory name). For example, MACBETH/SYS:ACCOUNTS\PAY (server/volume:directory\subdirectory)
/? View online help. All other parameters are ignored when /? is used.
/VER View the version number of the utility and the files it uses to execute. All other parameters are ignored when /VER is used.
Using MAP
If you don't include drive mappings in your login script, they will have to be manually recreated each time the user logs in. (See "Creating Login Scripts" in Chapter 3 of Supervising the Network.)
You can have up to 26 mappings, including local drives.
Search drive mappings begin with the letter Z and continue backward through the alphabet.
To map a search drive, use S and a number. (See "MAP Options" on page 123.)
If you don't want to overwrite existing search drives, use the "INS" option.
To map to the next available search drive, use "S16:="
MAP Options
Option: P Map to a physical volume. Must be listed first or second.
NP Overwrite local or search drives without being prompted. Must be listed first or second.
C Change a regular drive to a search drive, or a search drive to a regular drive.
DEL Delete a drive mapping.
INS Insert a search drive mapping without replacing an existing mapping.
N Map the next available drive to the specified path.
ROOT Map a drive to a fake root directory for applications that require rights in a root directory.
W Do not change master environment.
Examples
To view mappings, type
MAP
To map drive G: to SYS:\HOME\JAN on the current server, type
MAP G:=SYS:\HOME\JAN
To extend the mapping for drive G: above to SYS:\HOME\JAN\ PROJECTS, type
MAP G:=PROJECTS
To map search drive 4 to PRUFROCK (server) SYS (volume) APP (directory), type
MAP S4:=PRUFROCK/SYS:APP
To change Y: from a regular NetWare drive to a search drive, type
MAP C Y:
To delete the mapping for drive G:, type
MAP DEL G:
To map drive F: to the DOSGAMES volume of the GAMES directory as a fake root, type
MAP ROOT F:=GAMES\DOSGAMES:
To map the last possible search drive to IZARD (server) SYS (volume) PUBLIC (directory), type
MAP S16:=IZARD/SYS:PUBLIC
To map the next available drive to Z:\PUBLIC\DOS\APP from Z:\PUBLIC, type
MAP N DOS\APP
To map the next available drive to BRUTUS/SYS:ACCT\ OLD, type
MAP N BRUTUS/SYS:ACCT\OLD
To insert COUNT (server) SYS (volume) PUBLIC (directory) as a new search drive, type
MAP INS S4:=COUNT/SYS:PUBLIC
To map to PUBLIC\RPTS under Volume object SYS.ACCOUNTING .ACME.US from the root, type
MAP H:=.SYS.ACCOUNTING.ACME.US:PUBLIC\RPTS
File/Patch History: As of the date of this TID, there has been one update/patch for the MAP.EXE command. The following lists the file information:
NetWare 3.1x: MAP.EXE 12/16/94 51701K -- MAP312.EXE
NetWare 4.1: MAP.EXE 9/22/95 273607K -- MAP412.EXE
.
Troubleshooting and Top Issues: Some of the issues regarding the MAP command are as follows:
Issue #1
symptom
SYMPTOM: When running MAP.EXE, the following errors were returned:MESSAGE SYS2070: A program in this session encountered a problem and cannot continue. MESSAGE: The system could not demand load the application's segment. MAP->NWCALLS.513 is in error.
TROUBLESHOOTING: Check the date and size of MAP.EXE being executed. Check the date and size of the NWCALLS.DLL being loaded into the workstation's memory.
cause
CAUSE: The system delayed the loading of some of the application's code until it was needed. Then there was a problem loading the needed code segment.
fix
SOLUTION: Do not use the NetWare 4.01 OS/2 version of MAP.EXE with NWCALLS.DLL dated 1-27-93 with the size of 65,504 bytes (800UPDATE1 and NetWire). When using MAP.EXE or LOGIN.EXE from previous versions of NetWare, use the NetWare 4.01 version of NWCALLS.DLL dated 5-18-93 with the size of 108,432.
Issue #2
symptom
SYMPTOM: Map.exe not properly handling the connection table on expired passwords. Using map.exe from 3.12, 3.11 or 3.11-1000 user, to map to a 3.11 1000-user or 4.01 1000-user using bindery emulation doesn't handle connections above 255 to change password.
fix
SOLUTION: Use map.exe from 4.01 by copying map.exe, map.msg, creating an nls directory and copying unicode tables. You do not need requester support to run the enabled utilities. They will work with netx.
Issue #3
symptom
SYMPTOM: Customer was mapping a search drive in a private dos box. But the mapping appeared invalid in the 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. If the user attempts to change to the invalid drive the message "Invalid drive specification" is reported. If the user then attempts 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. If the user then elects to delete the search drive (in the 2nd dos box) and exits the 2nd dos box, the search drive with the same letter in the 1st DOS box is then remapped as a regular drive mapped drive and not a search drive. In some cases the Z: that was a search drive becomes a regular drive mapping, thus users lose access to SYS:PUBLIC.
fix
SOLUTION: The problem was with MAP.EXE that shipped with 3.12. There is an updated MAP in NSD called MAP312.EXE that resolves this issue.
The updated MAP.EXE does not try to modify the Master Windows environment, only the local. Therefore, the problem does not get carried over into other private DOS VM (Virtual Machines).
Issue #4
symptom
SYMPTOM: When logging in, MAP DISPLAY OFF doesn't work. Drives mapped appear on-screen regardless of the MAP DISPLAY setting
cause
CAUSE: This symptom is caused by using an external MAP (#MAP) command in the login script.
fix
SOLUTION: Use LOGIN.EXE's internal MAP functionality, instead of using an external MAP.EXE to map drives in the login script.
Incorrect syntax:
MAP DISPLAY OFF
#MAP H:=SYS:
Correct syntax:
MAP DISPLAY OFF
MAP H:=SYS:
Issue #5
symptom
SYMPTOM: After mapping a search drive, then changing directories, files are not searched as expected. Instead of finding the files in the current directory, NetWare searches in the (fake) root directory.
cause
CAUSE: Using NetWare 4.x LOGIN.EXE or MAP.EXE, the way a rooted map drive is searched is different than with NetWare 2.x or 3.x. Under previous versions, when you map root a search drive, the drive is added to the search path with the current directory designated: Map root s1:=SYS:Public typing PATH or SET at the command line yields PATH=Z:. Note that the . (dot) after the Z indicates that the current directory will be searched. With NetWare 4.x, the same operation yields PATH=Z:\The \ (backslash) after the Z indicates that the root of Z will be searched.
fix
SOLUTION: The engineers reasoned that if you are setting a search drive to a root location, you must want to search at the root. While this makes sense, it does change the way rooted search drives are searched. To get the old behavior back, you must use a work-around. Here are five possible work-around:
1. Use MAP.EXE from 3.x and use #MAP in login scripts. The downside is that you can't use DS syntax or objects.
2. Remap the entire path after it is set, using the Login SET command, or by setting the path after he logs in, in the AUTOEXEC.BAT file. The downside is that if any drives are subsequently remapped, the problem reappears.
3. MAP drives on the fly as needed. This requires a lot of commands to be entered, or a lot of batch files to be written. Using a DS Directory Map object can make this considerably easier.
4. Don't use MAP ROOT. Simply map the search drive instead. MAP root drives only when necessary - when the application demands to be run at the root, or when path names are too long.
5. Use the MAP CHANGE command. To accomplish this, map the drive as normal, then map change it to a network drive, then map change it again to a search drive. The resultant drive will be added to the search path as it was in previous versions, with the current directory searched. For example:
map root s1:=sys:public
map c z:
map c z:
Issue #6
symptom
SYMPTOM: A Map Root search drive puts a "drive:\" in the DOS path rather than a "Drive:."
fix
CAUSE: MAP.EXE for all Novell NetWare 4.X versions mapping a search drive using MAP ROOT causes a backslash to be part of the Dos Path to that drive letter rather than a period. EX:MAP ROOT S1:=SYS:PUBLIC results in PATH=Z:\MAP S1:=SYS:PUBLIC results in PATH=Z:.The problem with this is some users have programs setup to take advantage of using CD to another subdirectory below the false root to change the search directory. CD does not change the search directory if the DOS PATH has a backslash rather than a period.
SOLUTION: When issuing a map root for a search drive it now places a backslash ( \ ) into the path rather than a period. This is a changed feature of map root and will not change with the 4.x products. However there is a workaround for those who need the period to remain in their path statement.
Work around:
EX: MAP ROOT H:=SYS:PUBLIC
The above command will map root drive H, then in order to make drive H a search driver, issue the following command.
EX: MAP CHANGE H:
The map change command will change drive H from a map rooted logical drive to a map rooted search drive. It will then append Drive H to the path statement with a period rather than a backslash.
Issue #7
symptom
SYMPTOM: MAP Z:=SYS: responds back with two blank lines and a DOS prompt. No error is returned and no drive is mapped.
TROUBLESHOOTING: Checked the config.sys for the LASTDRIVE statement. It was set to O. After mapping all drives from A to O, tested the following commands: MAP N SYS: reported the error "All drives are in use"MAP S16=SYS: reported the same error "All drives are in use"MAP P:=SYS: gave no error. Duplicated the problem here at Novell using the 1.2 vlms and the latest patches on a 4.1 server. The VLMs were verified to be functioning properly. MAP was not reporting an error back.
fix
CAUSE: LASTDRIVE was set to O: in the config.sys MAP.EXE dated 10/24/94 does not return an error.
SOLUTION: Set LASTDRIVE=Z in config.sys and mapping functions worked fine. A bug report was entered on MAP.EXE not reporting an error.
Issue #8
symptom
SYMPTOM: NetWare 4.10 MAP.EXE does not recognize dos variables from the DOS prompt. For example: MAP G:=%<dos_var>
cause
CAUSE: MAP never gets the environment variable, due to the way DOS parses the command line.
fix
SOLUTION: You can do it from within a batch file. For two examples, if you:
SET X=public
SET Y:=sys:public
then in your batch file use these lines:
map h:=sys:%x%
map I:=%y%
H: and I: will be mapped to sys:public.
Issue #9
symptom
SYMPTOM: Trying to map next a drive using the map.exe contained in map312.exe (v3.75 (941216) PTF) results in the message:
Drive <D> is in use by a local drive. Do you want to assign it as network drive? (Y/N)
fix
SOLUTION: The 4.x versions of map.exe do not have this problem. An SPD (#98614) has been entered on the 3.x version of map.exe
Issue #10
symptom
SYMPTOM: The following errors occur when trying to map root a drive in a login script using the %login_name variable when the login name is greater than 8 characters. Login.exe version 3.76 (940711) PTF and login.exe version 3.75. When trying to login to a 3.x server as the user "longusername" and the command: map root h:=sys:users\%login_name is in the login script, the following error is returned: The following drive mapping operation could not be completed. "ROOT H:=SYS:USERS\LONGUSERNAME"The error code was 0003.The following commands do work in the login script: map ins s1:=sys:users\%login_namemap h:=sys:users\%login_namemap root h:=sys:users\longuserSimilar errors occur when trying to map root drives using map.exe version 4.12: The command: map root h:=sys:users\longusername returns MAP-4.12-915: The specified volume does not exist map.exe version 3.75 (941216) PTF. The command: map root h:=sys:users\longusername returns: The following drive mapping operation could not be completed. "ROOT H:=SYS:USERS\LONGUSERNAME" (0x3)With either version of map.exe the following commands do work: map ins s1:=sys:users\longusernamemap h:=sys:users\longusernamemap root h:=sys:users\longuser
fix
SOLUTION: An SPD (#98638) was entered about the issue for NetWare 3.x. In the meantime the work around is to use the NetWare 4.1 shipping versions of login.exe and map.exe
Issue #11
symptom
SYMPTOM: What are the return codes generated by MAP.EXE?
fix
SOLUTION: If the mapping operation is successful, it will generate an errorlevel of 0. If unsuccessful, it will generate an errorlevel of 1.
Issue #12
symptom
SYMPTOM: When you type MAP N SYS: it returns: Drive D is in use by a local drive. Do you want to assign it as network drive? (Y/N) Y
fix
SOLUTION: This is a bug. It should be trying the first available NETWORK drive, instead of the first available drive. Use MAP version 3.75 or specify the drive letter instead of using MAP NEXT.
Issue #13
symptom
SYMPTOM: The documentation in the Novell NetWare 3.12 Installation and Upgrade manual on page 169 (date July 1993) and on page 177 (dated DEC 1993) states that if you have a particular drive letter, use the following command to map the search drive, replacing drive: with the drive letter: Map S16:=drive:=path. For example:
Map s16:=L:=sys:\public an error is returned by Map. Could not interpret command line.
fix
SOLUTION: The documentation is incorrect for the map.exe file that comes with NetWare 3.12. The syntax does not work at all with map.exe that ships with NetWare 3.12. However, this command syntax does work with the map.exe dated 10/20/94 that ships with NetWare 4.1.
Issue #14
symptom
SYMPTOM: A workstation logging into a 4.1 server with the 1.20 vlms experienced problem where drive mappings could not be deleted. For example the command "MAP DEL P:" gave the error: MAP DELETE FAILED. MAP showed that the drive was not deleted. That drive letter could no longer be remapped. If the drive was a search drive, it became a logical drive and new drive mappings could not be added.
fix
SOLUTION: Used map.exe from MAP412.EXE and the latest VLMs and the error never reoccurred.
Issue #15
symptom
SYMPTOM: When using DOS/WIN Client 32, users may expect to see error messages and strange behavior from NetWare 3.12 utilities. For example:
MAP.EXE dated 5-7-93 Unexpected error 4, error code 8801
CAPTURE.EXE dated 5-20-93 When executed, it returns to the DOS prompt, without an error, and without performing a function.
cause
CAUSE: Workstation has attached or is attached to 9 or more servers. NetWare 3.12 utilities only provided functionality for 8 servers, and were not designed for today's network clients.
fix
SOLUTION: Do not use NetWare 3.12 utilities when attaching to more than 8 servers.
-Unload the client or reboot after attaching to more than 8 servers
-Copy corresponding NetWare 4.x utilities to the 3.x file server
-Map search drives to 4.x utilities (ie. SYS:\PUBLIC)--Note: this solution will not work if the user is executing a utility and the 3.12 version of the utility in the current directory.
After preliminary tests, workstations appear to only get these errors with 3.12 utilities if they are attached to 9 or more servers or if they were previously attached to 9 or more servers. 4.x utilities should operate normally when attached to 9 or more servers.
If you have a mixed 3.x/4.x environment, you may attach or map to the public directory of a 3.12 server. Because this may be transparent to the user, and because errors will occur, caution should be used when planning attachments and mappings. Also note that some 3.x utilities such as SYSCON, do not have 4.x replacements. Utilities such as VOLINFO, SLIST and ATTACH do not have direct 4.x replacements. (You may use FILER, NLIST SERVER, and LOGIN <SERVERNAME> /NS /NB)
document
| Document Title: | MAP Command Summary. |
| Document ID: | 10027779 |
| Solution ID: | 1.0.59763863.2571262 |
| Creation Date: | 07Mar2000 |
| Modified Date: | 19Feb2003 |
| Novell Product Class: | NetWare Novell eDirectory |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.