20.0 FLAG Messages
The following includes messages from the FLAG.EXE.
FLAG-x-001: Action has been terminated by the operator.
Source:
FLAG.EXE
Possible Cause:
The FLAG was terminated by pressing Ctrl+C, Ctrl+Break, or Esc.
Action:
No further action is required.
FLAG-x-225: The mode you specified is reserved.
Source:
FLAG.EXE
Possible Cause:
Mode 4 or 6 was entered. These modes are reserved and cannot be used.
Action:
Use modes 0, 1, 2, 3, 5, or 7.
FLAG-x-250: The assigned mode was invalid.
Source:
FLAG.EXE
Possible Cause:
The mode that was entered was not in the valid range.
Action:
Use modes 0, 1, 2, 3, 5, or 7.
FLAG-x-275: Specify a file before assigning a mode.
Source:
FLAG.EXE
Possible Cause:
The user specified a valid directory path, not a filename. Directories cannot be assigned modes.
Action:
Specify a filename in the command.
FLAG-x-300: Access is denied.
Source:
FLAG.EXE
Possible Cause:
The user might not have adequate rights to access the file or modify directory attributes.
Action:
Use the RIGHTS utility to check the user’s rights.
Possible Cause:
The file is in use or the directory attributes are being modified while another user is modifying the same directory.
Action:
If the user account has adequate rights, make sure that the file is not in use, or that another user is not currently modifying the directory attributes.
FLAG-x-325: You do not have rights to change file or directory attributes
Source:
FLAG.EXE
Possible Cause:
The user account does not have the Supervisor or Access Control right to modify file attributes.
Action:
Make sure the user has appropriate user access rights. Use the RIGHTS utility to find out what the user account rights are at the volume level, grant the appropriate user access rights, and try the command again.
FLAG-x-350: This utility was unable to set the attributes.
Source:
FLAG.EXE
Possible Cause:
A request to change the attributes for a file or a directory was not successful.
Possible Cause:
The user account does not have the appropriate Supervisor or Access Control rights to change the attributes.
Action:
Make sure the user has appropriate user access rights.
Possible Cause:
The file is locked, or the directory attributes are being modified by another user.
Action:
Make sure the file is not in exclusive use by another process.
Possible Cause:
The file is in use or is corrupted.
Action:
Make sure that the file is not corrupted.
FLAG-x-400: This utility was unable to set the DOS file.
Source:
FLAG.EXE
Possible Cause:
The file might be corrupted.
Action:
Try to read or run the file. If you can, flag the file again. If you can't, the file is probably corrupted. Get a new copy of the file, then flag the file.
FLAG-x-425: The specified attribute(s) is not supported in this version of NetWare.
Source:
FLAG.EXE
Possible Cause:
The user specified an attribute that is not supported by the NetWare® server where the file is located.
Action:
Get a list of attributes supported by the server where the file is located by typing FLAG /? at the command line. Make sure to run FLAG from the drive mapped to the file’s location.
FLAG-x-441: The /DO command is not supported for local drives.
Source:
FLAG.EXE
Action:
When referencing local drives, do not use the /DO command line option.
FLAG-x-450: Owners cannot be assigned to local drives or files.
Source:
FLAG.EXE
Possible Cause:
This attribute is not supported with files on local drives.
Action:
When assigning attributes to files on local drives, do not use this attribute.
FLAG-x-450: The attribute_name attribute is not supported for local files.
Source:
FLAG.EXE
Action:
When assigning attributes to files on local drives, do not use the specified attribute.
FLAG-x-450: The Search mode is not supported for local files.
Source:
FLAG.EXE
Action:
When searching local drives, do not use the search mode in FLAG.
FLAG-x-575: This owner was not found.
Source:
FLAG.EXE
Possible Cause:
The owner specified is not a user on the network.
Action:
Make sure that the user typed the owner's name correctly. Make sure that the owner that the user specified is a current user on the network.
FLAG-x-625: This utility was unable to allocate the volume handle.
Source:
FLAG.EXE
Possible Cause:
The client workstation is not attached to a server
Action:
If the user is using a server version prior to NetWare 4, make sure the client workstation is attached to the desired server. If the user is using a NetWare 4 or later version server, make sure the client workstation has a drive mapped to volume and server or to the volume object.
Possible Cause:
The volume is not mounted or does not exist.
Action:
Make sure that the volume is mounted and that the user typed the volume name correctly.
FLAG-x-650: This utility cannot assign volume attributes in v2.x.
Source:
FLAG.EXE
Action:
When using a NetWare 2 server, do not set volume attributes.
FLAG-x-673: This utility was unable to get the connection information.
Source:
FLAG.EXE
Action:
Retry the command. If the problem persists, contact a Novell® support provider.
FLAG-x-675: This utility was unable to change the volume attributes.
Source:
FLAG.EXE
Explanation:
Your user account must have the Supervisor or Access Control right to change attributes.
Action:
Find out what the user’s account rights are at the volume level by using the RIGHTS utility. If appropriate, make sure the user has the Supervisor or Access Control rights. After the user’s rights are assessed and reassigned if necessary, try the command again.
FLAG-x-700: The Execute Only attribute cannot be assigned to local files.
Source:
FLAG.EXE
Action:
When assigning attributes to files on local drives, do not use this attribute.
FLAG-x-725: The Private attribute cannot be assigned to local files.
Source:
FLAG.EXE
Action:
When assigning attributes to files on local drives, do not use this attribute.
FLAG-x-750: The Index attribute is not supported in v3.x or v4.x.
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Index file attribute to flag a file located on a NetWare 3 or NetWare 4 server. This attribute only works on files located on NetWare 2 servers.
Action:
If the files are located on NetWare 3 or NetWare 4 servers, do not use the Index file attribute.
FLAG-x-775: The Private attribute is not supported in v3.x or v4.x.
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Private file attribute on a file located on a NetWare 3 or NetWare 4 server. This attribute only works on files located on NetWare 2 servers.
Action:
If the files are located on NetWare 3 or NetWare 4 servers, do not use the Private file attribute.
FLAG-x-800: The Purge attribute is not supported in v2.x.
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Purge file attribute on a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.
Action:
If the files are located on NetWare 2 servers, do not use the Purge file attribute to flag the files.
FLAG-x-819: You cannot assign a user and group at the same time.
Source:
FLAG.EXE
Possible Cause:
Users and groups must be assigned in separate commands. The user tried to assign them at the same time.
Action:
Try again, assigning users and groups separately.
FLAG-x-825: The Copy Inhibit attribute is not supported in v2.x
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Copy Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.
Action:
If the files are on a NetWare 2 server, do not use Copy Inhibit file attribute to flag the files.
FLAG-x-850: The Delete Inhibit attribute is not supported in v2.x
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Delete Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.
Action:
If the files are located on NetWare 2 servers, do not use the Delete Inhibit file attribute to flag the files.
FLAG-x-875: The Rename Inhibit attribute is not supported in v2.x
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Rename Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.
Action:
If the files are located on NetWare 2 servers, do not use the Rename Inhibit file attribute to flag the files.
FLAG-x-876: The Migrate attribute is supported only with NetWare v4.x
Source:
FLAG.EXE
Possible Cause:
The user tried to set the Migrate attribute on a server that is not a NetWare 4 server. This attribute is supported only on NetWare 4 servers.
Action:
Use the Migrate attribute only on a NetWare 4 server.
FLAG-x-877: The Compress attribute is supported only with NetWare v4.x
Source:
FLAG.EXE
Explanation:
The user tried to set the Immediate Compress or Don’t Compress attribute on a server that is not a NetWare 4 server.
Action:
If the server is not a NetWare 4 server, do not use the Immediate Compress or Don't Compress attribute.
FLAG-x-878: You cannot set both the Immediate Compress and Don’t Compress attributes.
Source:
FLAG.EXE
Possible Cause:
The user tried to set both the Immediate Compress file attribute and the Don’t Compress file attribute. These two file attributes cannot both be set at the same time.
Action:
Decide whether the file should be compressed or not compressed; then use the appropriate flag.
FLAG-x-879: Migration is not enabled on the server.
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Migration capability on a server that is not currently supporting migration.
Action:
Verify the Migration status on the server. If the problem persists, contact a Novell® support provider.
FLAG-x-880: Compression is not enabled on the server.
Source:
FLAG.EXE
Possible Cause:
The user tried to use the Compression capability on a server that is not currently supporting compression.
Action:
Verify the Compression status on the server. If the problem persists, contact a Novell support provider.
FLAG-x-901: You are not attached to the specified server.
Source:
FLAG.EXE
FLAG-x-903: The command line syntax is invalid.
Source:
FLAG.EXE
FLAG-x-905: This utility was unable to initialize the country information.
Source:
FLAG.EXE
FLAG-x-908: The specified path is invalid.
Source:
FLAG.EXE
FLAG-x-909: You are not mapped to the specified drive.
Source:
FLAG.EXE
FLAG-x-910: This utility was unable to parse the specified path.
Source:
FLAG.EXE
FLAG-x-911: Directory Services is not active at this time.
Source:
FLAG.EXE
FLAG-x-912: The specified file cannot be found.
Source:
FLAG.EXE
FLAG-x-913: The specified directory cannot be found.
Source:
FLAG.EXE
FLAG-x-914: The specified file or directory cannot be found.
Source:
FLAG.EXE
FLAG-x-915: The specified volume does not exist.
Source:
FLAG.EXE
FLAG-x-916: This utility only supports 25 levels of directories.
Source:
FLAG.EXE
FLAG-x-917: This utility was unable to set the context.
Source:
FLAG.EXE
FLAG-x-925: This utility is not supported on Personal NetWare servers.
Source:
FLAG.EXE
Explanation:
FLAG does not support drives located on Personal NetWare servers.
Action:
Use the Personal NetWare utilities to perform the desired task.
FLAG-x-970: The attempt to open the Unicode table files failed.
Source:
FLAG.EXE
FLAG-x-971: The workstation does not have enough memory to load the Unicode table files.
Source:
FLAG.EXE
FLAG-x-972: Access to the Unicode table files was denied.
Source:
FLAG.EXE
FLAG-x-973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number
Source:
FLAG.EXE
FLAG-x-974: The Unicode table files are corrupt.
Source:
FLAG.EXE
FLAG-x-975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.
Source:
FLAG.EXE
FLAG-x-998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.
Source:
FLAG.EXE
FLAG-x-999: The message file for this utility cannot be found.
Source:
FLAG.EXE