Chapter 3 - Managing StreetTalk for Windows NT File Services
Overview of Managing StreetTalk File Services
After you create a file service, you need to configure the service. This chapter explains how to perform administrative tasks related to StreetTalk file services. The following topics are discussed:
In addition to the settings discussed in this chapter, you may need to modify security settings for your file service. Refer to Chapter 4 for information on administering security for a StreetTalk file service.
This chapter does not explain how to manage VINES Files, which contains programs that run on Banyan network clients. For information on managing VINES Files, refer to Chapter 5.
Stopping and Restarting a StreetTalk File Service
To stop and start an individual StreetTalk file service, use StreetTalk Explorer. A stopped file service is also automatically restarted when you start the StreetTalk File Service from the Windows NT Service Controller.
A StreetTalk file service starts automatically after you create it. You can stop and start each StreetTalk file services independently of other services. Stopping and starting a single file service, does not affect the status of other file services on the Windows NT Server. When you stop an individual StreetTalk file service, non-Banyan clients of the Windows NT Server can still connect to directories that correspond to StreetTalk file services.
To Stop a StreetTalk File Service from StreetTalk Explorer
1. Open the property sheets for the file service.
2. On the Summary property sheet, click Stop.
3. Verify the status of the service on the Summary property sheet. By default, this information updates every 30 seconds. Press F5 to update the status of the service immediately.
You can also stop all of the file services on a StreetTalk server at once by stopping StreetTalk File. Use the Windows NT Services Manager to stop the StreetTalk File service. This stops all Banyan file services.
Modifying the Properties of a StreetTalk File Service
After you create a file service, you can modify the existing configuration at any time. StreetTalk File lets you specify who can use a file service, how many users the service can support, how long a user who is not actively using a service remains connected to it, and what kind of information about a service is available in the Windows NT Event Viewer.
You must be the StreetTalk administrator of the service to modify configuration settings. If you are not the administrator, you can view information for the service in StreetTalk Explorer, but cannot edit any configuration settings.
The sections that follow explain how to modify the following settings for a StreetTalk file service:
![]()
Windows NT path ![]()
Idle timeout ![]()
Log settings ![]()
ARL option ![]()
User limit ![]()
Share type ![]()
Share points in a group share
Except for the pathname and share points, a default setting exists for each configuration item. If you do not change the default settings, they remain in effect. You can modify the settings at any time.
After you create a StreetTalk file service, you can modify the path to the disk or directory that corresponds to the StreetTalk name. Update the Windows NT path for a file service if you change the location of a directory on the Windows NT Server.
For information about modifying the Windows NT path for share points within a group share, refer to "Modifying Group Share Points" later in this chapter.
To Modify the Windows NT Path for a Single Share File Service
1. In StreetTalk Explorer, open the Shares property sheet for the file service.
2. Specify a path for the file service by doing one of the following:
- Click the dropdown arrow and select a drive letter from the list of available drives. Extend the path as necessary to specify a directory on the Windows NT Server and click OK.
- Click the browse button. The Select Directory dialog box appears. Choose a drive and directory and click OK. The Shares Page appears.
3. Do one of the following:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
Modifying the Idle Timeout for a File Service
You can configure a StreetTalk file service to automatically disconnect workstations that have not used the connection following a specific period of time.
As a StreetTalk File administrator, you can manually disconnect users from a StreetTalk file service. For information on how to temporarily free SPP connections by disconnecting users from a file service, refer to "Temporarily Disconnecting Users from a Share" later in this chapter.
Specifying the Timeout Value for Idle Connections
For each StreetTalk file service, you can automatically disconnect users who are not actively using a connection. If idle timeouts are enabled, network drives that are mapped to a file service are disconnected after being idle for the specified period time. The idle timeout value specifies the amount of time before StreetTalk File disconnects workstations that are not actively using a file service to which they are connected. A timer automatically tracks the most recent use of the connection. Each time a user accesses the file service, StreetTalk File resets the timer. Users maintain connections to file services on which they have open files.
When the network is accessed, the connection is re-established. If a drive connection times out, the drive and directory mappings on the workstation are preserved following the loss of connection. The next time the user activates the drive, it connects to the file service at the directory last used, as though the connection had never been removed.
Note: If you enable timeouts for VINES Files, after a workstation is disconnected, it broadcasts for a new VINES Files service, and may not automatically re-connect to the service it was using before the connection was broken.
StreetTalk for Windows NT limits the number of concurrent SPP connections. Because the SPP file service connections established by a workstation usually remain alive for the duration of your login session, the number of users mapping to a file service can exceed the number of SPP connections available on the server. Users who attempt to connect to the file service after the maximum number of SPP connections has been reached will be unable to access the service.
Enabling timeouts conserves SPP connections by automatically disconnecting workstation drives connected to a server after a configurable idle time. As an added benefit, network traffic decreases since the messages associated with maintaining idle connections are eliminated.
For more information about SPP connections, refer to the StreetTalk for Windows NT Installation Guide.
The idle timeout value defined for a file service affects Banyan clients only. Other clients are not disconnected from a session if the connection remains idle for the configured amount of time.
To Modify the Timeout Value for a File Service
1. In StreetTalk Explorer, open the Timeouts property sheet for the file service.
2. Select the Idle Timeouts checkbox to enable timeouts.
3. Enter the timeout value in the adjacent text box and select the appropriate unit of time (seconds, minutes, hours, or days) from the drop-down list box. The maximum timeout value is 999.
4. Do one of the following:
- Click OK. The property sheets for the share close. The StreetTalk Explorer browser appears.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
You can modify log settings to increase logging when troubleshooting, or to decrease logging to improve performance. All StreetTalk File log information is written to the Windows NT Event Viewer Application log.
The Windows NT Event Viewer displays informational and error messages that are reported by system services and applications. StreetTalk File reports error and status messages to the Application Log of the Windows NT Event Viewer. By default, StreetTalk File logs error messages only. You can modify event log settings to change the number and type of events reported to the log. You can also configure how the Windows NT Event Viewer creates the log file.
It is recommended that you configure StreetTalk File to log only those events necessary to properly administer the service. Excessive logging can significantly decrease the performance of a file service. Only increase the number and type of events reported to the Event Viewer to assist you in troubleshooting problems.
If the number of events reported to the Application Log in the Windows NT Event Viewer becomes too great, the log begins to overwrite itself, causing you to lose essential event information. Consider increasing the maximum size of the event log or enabling Event Log wrapping. Refer to your Windows NT documentation for information on modifying these Event Viewer settings.
Refer to Table 3-1 to information about the events available for inclusion in the StreetTalk File logs.
Event Name | Description of Event or Operation Recorded |
Errors |
|
Warnings | Warnings. |
Security Violations | ARL security violations. |
Connects/Disconnects | Users connecting to and disconnecting to the service. |
File Opens | Opening files. |
File Closes | Closing files. |
File Reads | Reading files. |
File Writes | Writing to files. |
Other File Operations | Other file operations, such as getting attributes, locking files, or searching for files. |
File/Directory Deletes | Deleting files or directories. |
File/Directory Renames | Renaming files or directories. |
Directories | Any directory operations. |
Other Disk Operations | Other disk operations, such as getting disk attributes. |
ARL Operations | Accessing or modifying ARLs. |
SMB Level Operations |
SMB operations. SMB is the protocol that is
used by workstations to access file services. Note: Enabling this option slows the file service considerably. |
Debugging Info | Debugging information at the lowest level. |
To Modify Event Log Settings
1. In StreetTalk Explorer, open the Log Settings property sheet for the file service.
2. Do one of the following:
- From the Available window on the right, select events to record in the log and click Add. The events selected appear in the Logged window on the left.
- Click Add All to record all events.
- From the Logged window on the left, select events you no longer want to record in the log and click Remove. The events selected appear in the Available window on the right.
- Click Remove All to eliminate logging.
3. Do one of the following:
- Click OK. The property sheets for the share close. The StreetTalk Explorer browser appears.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
Modifying the Access Rights List (ARL) Option
You implement security for the file service by:
![]()
Specifying an ARL option ![]()
Specifying ARLs for files and directories
The following section explains how to specify the ARL option for a file service. After choosing the ARL option, you can modify the default ARL for the service. Refer to "Modifying the ARLs" in Chapter 4 for information on specifying ARLs.
The default ARL option for a new file service allows you to specify a unique ARLs for each directory in a the service. Modify this setting if you want to be able to specify file or directory ARLs other than those allowed by the default.
Setting the Access Rights List Option for a File Service
For each StreetTalk file service, you can specify the users who have access to its directories and files. You specify access rights by assigning an ARL for the file service. StreetTalk File provides three options for setting ARLs.
![]()
Single ARL ![]()
Directory-Level ARL ![]()
File-Level ARL
The option you select determines the number of ARLs you can specify within the file service. The following section provides more information about each of the three ARL options.
ARL Options
The following ARL options are available:
Single ARL - Lets you define a single level of access that applies to all directories and files that exist within a file service. The ARL of the root directory determines the ARL of other objects in the file service. Each new subdirectory you create inherits the directory access rights and file mask of the root directory. Files that you create or copy into a directory inherit the access rights specified in the new file mask of the root directory. If the file service is set to use a single ARL and you modify the ARL of the root directory, the new ARL is automatically applied to existing objects contained in the service.
The ARL of an existing subdirectory or file cannot be changed. Changing these rights requires you to change the ARL option for the service.
Note: For file services mapped to CD-ROM drives or other drives with removeable media, it is recommended that you set the ARL option to Single. When you set ARLs for a file service, the ARL for each file or directory is stored in the ARL database. If you set ARLs for a disk and then replace it with another disk, the ARL database can no longer match access rights to the new directory structure, resulting in unpredictable access and inefficient ARL processing.
Directory-Level - Lets you define unique access rights for each directory within a file service. This is the default ARL applied to new file services. You can specify a different ARL to determine the rights inherited by new files created within the directory.
Under this setting, new subdirectories acquire directory-level rights and a new file mask as they exist in their parent directory at the time of their creation. Files acquire the access rights from the new file mask in their directory when they are created or copied into the directory. When the file is created, its access rights cannot be changed by anyone as long as the service is set to "Directory-Level." A subdirectory's directory-level rights and new file mask can be changed at any time under this setting. Changing the access rights of a directory only affects the access rights of those subdirectories and files created in that directory after the change.
File-Level - Lets you define unique access rights for each file within a file service.
The file-level setting lets you set unique access rights for each directory and its associated new file rights mask, and for individual files. In other words, when the file-level ARL option is set, you can set access rights exactly as you do in VINES 6.0 and greater.
Changing the ARL option setting of a file service from either Single ARL or Directory-Level to File-Level may change the access rights of previously created subdirectories and files.
To Modify the ARL Option for a File Service
1. In StreetTalk Explorer, open the Options property sheet for the file service.
2. From the ARL Option drop-down list box, select one of the following ARL options to apply the StreetTalk file service:
- Single ARL
- Directory-Level[default]
- File-Level
3. Do one of the following:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
You can modify the user limit for a file service at any time. This section explains how to modify the user limit for a file service.
Specifying a User Limit for the Connection
For each StreetTalk file service, you can specify the number of users who can access the file service at one time. The default number is 500. Modify this user limit as necessary to support licensing restrictions for software in the Windows NT directory. You can specify a maximum user limit of 1000.
The user limit defined for the file service is independent of any user limit defined for the directory by Windows NT. Banyan clients can connect to the Windows NT directory even if the number of users exceeds the limit defined for the Windows NT directory.
To Modify the User Limit for a File Service
1. In StreetTalk Explorer, open the Advanced property sheet for the file service.
2. In the User Limit text box, enter the new user limit.
3. Do one of the following:
- Click OK. The property sheets for the file service close. The StreetTalk Explorer browser appears.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
Converting the Share Type of a File Service
StreetTalk for Windows NT supports two types of file services: single share and group share. When creating a file service, you specify the type of share to create. If you later decide that the other type is more appropriate for a given file service, you can convert the share type of the service.
To Convert a Single Share File Service to a Group Share File Service
1. In StreetTalk Explorer, open the Shares property sheet for a single share file service.
2. Click Convert to Group Share. You are prompted to confirm that you want to convert the existing StreetTalk file service to a group file service.
3. Click OK. A window listing the share points configured for the group share appears, displaying a share point with the name SHARE. The path for this default share point is the same as the path for the original single directory share. Modify the default name and path as necessary.
4. Do one of the following:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish.
Converting Group Share File Services to Single Share File Services
When converting a group share file service to a single share file service, you select a share point, and make it the path for a new single share file service. The Windows NT path for the selected share point becomes the default path for the single share. Other share points configured for the group share are removed. The data contained in the Windows NT directories associated with the other share points is not affected.
To Convert a Group Share to a Single Share
1. In StreetTalk Explorer, open the Shares property sheet for a group share file service.
2. Right-click the share point that you want to use as the single directory share, and select Convert from the context menu.
You are prompted to confirm that you want to erase all existing share points and set the default path to the path specified for the selected share.
3. Click OK. All share points, except the selected one, are deleted, and the share is converted to a single share.
4. Do one of the following:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Proceed to another configuration task or click OK to finish..
Modifying Share Points in a Group Share File Service
A group share file service consists of one or more share points, each corresponding to an exclusive directory tree. You can modify share points as follows:
![]()
Add and remove share points ![]()
Modify share point names ![]()
Modify the path of a share point
Adding Share Points to a Group Share
You can assign an unlimited number of share points to a StreetTalk group share.
To Add a Share Point to a Group Share
1. In StreetTalk Explorer, open the Shares property sheet for the file service and do one of the following:
- Right-click the window displaying the share points and select New from the Context menu.
- Press INSERT.
2. The cursor appears beside a new icon in the Name column of the window. The default path is C: and the default drive type is Fixed.
3. Enter a name for the new share point. Share point names are limited to 8 characters.
4. Specify a path for the share point by doing one of the following:
- Enter a new drive letter and path at the cursor.
- Click the browse button to the right of the current path. The Select Directory dialog box appears. Choose a drive and directory, and click OK.
The drive icon and drive type designation change to reflect the type of drive specified.
To Rename a Share Point
1. In StreetTalk Explorer, open the Shares property sheet for the file service.
2. Right-click the share point to rename, and select Modify, Share from the Context menu. The share point name is highlighted.
3. Type the new share point name and press ENTER.
4. Do one of the following for the new name to take effect:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Create additional share points or click OK to finish.
Users see the new name the next time they access the file service.
To Modify the Path of a Share Point
1. In StreetTalk Explorer, open the Shares page for the file service and right click the share point to modify.
2. From the context menu that appears, point to Modify and select Path. The share point path is highlighted.
3. Specify a path for the share point by doing one of the following:
- Enter a new drive letter and path at the cursor.
- Click the browse button to the right of the current path. The Select Directory dialog box appears. Choose a drive and directory and click OK.
4. Do one of the following for the new name to take effect:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button becomes grayed out. Modify additional share points or proceed to another configuration task. Click OK to close the property sheets for this file service.
You can delete one or more share points for a group share. Delete a share point if:
![]()
You no longer want Banyan clients to share the data in the corresponding Windows NT directory ![]()
The drive for this share point is no longer available ![]()
You no longer want the contents of the directory associated with the other information in the group share Note: You cannot delete the last share point in a group share.
To Delete a Share Point
1. In StreetTalk Explorer, open the Shares property sheet for a group share file service.
2. Select the name one or more share points to delete and do one of the following:
- Right-click the name of the share point, and select Delete from the Context menu that appears.
- Click DELETE.
You are prompted to confirm that you want to delete the share point.
3. Click Yes. The share point is deleted.
4. Do one of the following:
- Click OK. The property sheets for the file service close.
- Click Apply. The Apply button is dimmed. Modify additional share points or click OK to finish.
Temporarily Disconnecting Users from a Share
StreetTalk File lets you temporarily disconnect selected users from a StreetTalk file service to free SPP connections. The drive and directory mappings on the user's workstation are preserved following the loss of connection. The next time the user attempts to access the drive, the drive connection is re-established at the directory last used.
Note: If you disconnect a user from VINES Files, the user's workstation broadcasts for a new VINES Files service, and may not automatically reconnect to the service it was using before the connection was lost.
To Disconnect Users from a Share
1. In StreetTalk Explorer, open the Users property sheet for the file service.
2. Do one of the following:
- To disconnect individual users, select the users to disconnect. Right-click, and select Disconnect from the Context menu.
- To disconnect all users, right click anywhere within the users window. From the context menu that appears, select Disconnect All.
The selected users are temporarily disconnected.
Managing Directories and Files in a File Service
Managing directories and files in a StreetTalk file service is similar to managing directories and files on a local disk. You manipulate files and directories in a StreetTalk file service using a combination of the native management tools available on your client and specific Banyan tools. Managing directories and files in a StreetTalk file service involves:
![]()
Listing contents of a directory ![]()
Copying files and directories and their attributes ![]()
Creating new files and directories ![]()
Deleting files and directories ![]()
Renaming files and directories
To perform these operations you must have the appropriate access rights to the files and directories being managed (Table 3-2).
OPERATION |
|
|
File | Directory | |
COPY a file | none | SRW |
COPY a directory* | RW | SRW |
Create a file | RW | SRW |
Create a directory | none | W |
Delete a file | none | SRWD |
Delete a directory | none | SRWD |
Rename a file | none | SRW |
Rename a directory | none | SRW |
View files/directories | none | SR |
*If the directory is empty, no file rights are required, and only RW rights are required on the parent directory. |
Refer to Chapter 4 for more information about using and setting access rights for a file service.
Using DOS and OS/2 Commands with File Services
You can execute most DOS and OS/2 commands against StreetTalk file services. However, DOS and OS/2 utilities designed for local operation only, such as SUBST, CHECKDISK, JOIN, and FORMAT, cannot be run against network file services.
A user can execute a command or access an application stored on a StreetTalk file service only if:
![]()
The attributes for the directory and file permit the type of access requested ![]()
The user has the access rights required to perform the necessary operation on the target file, directory, or file service
For complete information on access rights and attributes, refer to Chapter 4.
Listing the Contents of a Directory
To view the contents of a directory on a file service, use the Banyan VDIR command, or another tool supported by the operating system on your workstation. For example, on a DOS client, use the DIR command.
To rename files or directories in a file service, use the Banyan VRENAME command, or another tool supported by the operating system on your workstation. For example, on a DOS client, use the RENAME command.
Note: The DOS RENAME command renames files on a network drive differently than it does on a local workstation drive. On a local drive, the RENAME command aborts if it encounters a file that matches the destination template. On a network drive, the command renames all files that it can before displaying an error message if it encounters duplicate names. That is, the command continues on error and renames all the files that it can.
Creating Directories on File Services
You can create directories on a StreetTalk file service from a DOS, OS/2, or Windows workstation on the Banyan network. When creating directories or folders, use the procedures supported by the operating system on your workstation (Table 3-3).
Workstation type | Tool for Creating Directories |
All client types | MKDIR command. |
OS/2, Windows 3.1, Windows NT 3.51 | Create Directory in File Manager |
Windows 95/98, Windows NT 4.x | New Folder in Windows Explorer |
Copying Files into StreetTalk File Directories
After you connect a client to a directory on a StreetTalk file service, loading files into that directory is the same as loading files into a directory on a local disk; use the procedures supported operating system on your workstation (Table 3-4). Refer to Chapter 6 for information about connecting clients to a StreetTalk file service.
Workstation type | Tool for Loading Files |
All client types | VINES VCOPY command |
DOS or OS/2 | DOS COPY command |
Windows 3.1, Windows NT 3.51 | Drag source files to the target directory in File Manager |
Windows 95/98, Windows NT 4.x | Windows Explorer |
You can copy source files from any supported local or network directory to its target destination on the StreetTalk file service.
To preserve the Banyan ARLs for a file, you must use the Banyan VCOPY command. Using the DOS COPY command or dragging files does not copy Banyan ARLs.
Using the Banyan VCOPY Command
This section describes the Banyan VCOPY command for copying directories and files on Banyan network servers.
This command lets you copy both short (DOS 8.3) and long file names. It has a command-line syntax and a menu-driven interface that you can use at DOS, Windows, and OS/2 workstations. This chapter describes the command-line syntax and menu interface for each command in detail.
The VCOPY command copies files and directories, optionally including subdirectories, empty subdirectories, and ARLs. VCOPY automatically copies OS/2 Extended Attributes associated with the specified files. The DOS COPY command does not copy Extended Attributes. To preserve this information, use VCOPY instead of DOS COPY when copying directories and files created and stored in StreetTalk file services.
To use the VCOPY command, you must have the access rights listed in Table 3-5.
File Service Component | Access Rights Required |
Root directory of file service | Search |
Parent directories | Search |
Source directory | Search and Read |
Source file | Read |
Existing target directory | Search, Read, and Write |
Existing target file | Read and Write |
Caution: If you start to copy a large number of directories and files, you cannot abort the copy without rebooting. Only those files that had been copied before the reboot are copied.
The command syntax of the VCOPY command is:
VCOPY source-pathname [destination-pathname] [/A] [/E] [/O] [/P] [/S] [/HELP]
If you do not specify any parameters, the system displays the VCOPY Command menu. Table 3-6 explains how to use the switches at the command line.
Use | To | Notes |
source-pathname | Specify the DOS name of the file (or group of files) that is the source of the copy. Enter a drive letter, path, or file name for the source pathname. | If source is a group of files, indicate group with wildcards. |
destination-path | Specify the DOS name of the destination, or target, file name of the copy. | If you omit a destination path name, the default is the current directory. If file names are omitted or if *.* is specified, the source file names are used. When you specify a destination pathname, a prompt asks you to specify if the destination is a file or a directory. See "Example: To Copy a Directory Using Switches" later in this chapter. If the destination pathname ends with a backslash (\), the prompt does not appear. |
/A | Copy the Access Rights List (ARL) associated with the source file to the target file. | |
/E | Copy all directories, including empty directories. | Always use the /E switch in conjunction with the /S switch. |
/O | Bypass the prompt "File exists, do you want to overwrite? Y/N" that appears if you omit this switch and the specified destination file already exists. | Use the /O switch with care, as you might overwrite a file by mistake. |
/P | Use this switch if you copy multiple files and need to interrupt the process. | Receive a prompt before each file is copied. |
/S | Copy all subdirectories and their contents. | If you omit the /S switch, VCOPY copies only the contents of the specified directory and does not copy the subdirectories or their contents. |
/HELP | Display the VCOPY syntax and a definition of each switch. | This same text appears if you make a mistake in syntax when entering the command. |
When you specify a destination pathname, VCOPY first checks if the DOS file name is a duplicate. If not, VCOPY creates the new file under the specified directory.
If you specify a destination DOS file name that already exists in the target directory, VCOPY returns a message:
FILE EXISTS, DO YOU WANT TO OVERWRITE? Y/N?
If you enter Y, VCOPY overwrites the destination file with the source file contents. The destination retains its former name. VCOPY displays the name of the source file and informs you that the file is copied.
This section describes how to:
![]()
Copy a file to an existing directory ![]()
Copy a file to a new directory ![]()
Copy a directory with switches ![]()
Copy a directory to the root of another file service ![]()
Use the VCOPY Command menu
Copying Files with VCOPY
The first example shows how to use VCOPY to copy a file to an existing directory while renaming the file. The second example shows how to copy a file to a new directory while retaining the same file name.
In both examples, you can override the confirmation prompt by entering a backslash (\) at the end of the target pathname. For example, if you type \newuser\ as the destination, VCOPY automatically creates a directory called newuser and copies the file to this directory. If you type \newuser\my_file\ as the destination, VCOPY creates a directory called newuser and a subdirectory under newuser called my_file.
Example: To Copy a File to an Existing Directory
1. Enter:
vcopy f:\user\old_file.exe h:\public\new_file.exe
The following message appears:
Does new_file.exe specify a directory (D) or a file name (F) on the target?
2. Enter F. VCOPY copies the file old_file.exe in the f:\user directory and names the copy new_file.exe in the h:\public directory.
Example: To Copy a File to a New Directory
1. Enter:
vcopy f:\user\my_file.exe \newuser.
The following message appears:
Does NEWUSER specify a directory (D) or a file name (F) on the target?
2. Enter D to create the new directory. VCOPY copies the file my_file.exe to the newuser directory that it has created. The copy keeps the same file name.
If you enter F, VCOPY does not create a new directory; instead, it copies the file my_file.exe to the file called newuser within the user directory.
Preserving ARLs When Copying Files
Use VCOPY with the /A switch to copy the ARLs from a source rather than automatically inherit the ARLs for New Files specified in the root directory.
Copying Directories with VCOPY
The first example shows how to use VCOPY switches to copy a directory. The second example shows how to copy a directory to the root of another file service.
Enter:
vcopy f:\user\applica*.* h:\public\*.* /e /p /s.
VCOPY copies everything within the f:\user directory matching applica*.*, including files, directories, and empty subdirectories, to the h:\public directory and prompts you before copying each file.
Example: To Copy a Directory to the Root of Another File Service
To copy the directory \mydir to the root directory of another StreetTalk file service, enter:
vcopy s:\mydir p: /s.
VCOPY copies all files and subdirectories in the directory s: and places the destination files in the root of the file service assigned to drive p (p:\). VCOPY does not create the directory mydir in the root of the other file service.
Enter the VCOPY command without any parameters to display the VCOPY Command menu.
The following options appear:
![]()
CHANGE source - Lets you enter and change the source file or directory. ![]()
CHANGE destination - Lets you enter and change the destination file or directory. ![]()
SELECT options - Lets you select copy options.
To choose an option, press the right arrow key or the space bar.
Note: You must first enter a source file or directory before you enter a destination file or directory.
To Use the VCOPY Command Menu
1. From a PC on the network, enter VCOPY at the command prompt. The VCOPY Command menu appears.
2. Choose CHANGE source. The cursor moves to the bottom half of the screen and a new function key template appears at the bottom of the menu. Table 3-7 describes these keys.
Press | To |
F5 | Display the Select Pathname screen |
F10 | Return to the options at the top of the menu |
ESC | Return to the command prompt |
3. Select a source pathname by either:
- Entering the pathname and pressing F10.
- Pressing F5 and choosing a pathname from the Select Pathname screen. Use the arrow keys to highlight the pathname and press ENTER.
The VCOPY Command menu displays the source pathname you choose in the Source field. CHANGE destination is highlighted.
4. Press ENTER. Choose a destination pathname by either:
- Entering the pathname and pressing F10.
- Pressing F5 and choosing a pathname from the Select Pathname screen. Use the arrow keys to highlight the pathname and press ENTER.
The VCOPY Command menu displays the destination pathname you selected in the Destination field. SELECT options is highlighted.
5. After selecting the source and destination, do one of the following:
- Choose SELECT options to set switches. Move the cursor to the desired switch and press ENTER. An asterisk (*) appears next to the enabled switch. The ENTER key toggles the selection of a switch on and off. You can set more than one switch. Press F10 to execute VCOPY. A message appears confirming the copy.
- Press F10 to execute VCOPY. A message appears confirming the copy.
6. Press ESC to return to the command prompt.
You cannot rename a StreetTalk file service. To change the name of a file service, delete it and create a new service mapped to the same Windows NT directory.
The Summary page for a file service reports the current status of the service and the number of active and total sessions opened with this service. By default, the information on this page is automatically updated every thirty seconds.
Viewing StreetTalk File Log Reports
StreetTalk File logs events to the Applications Log in the Windows NT Event Viewer. These events are listed under the service name StreetTalk File. Refer to your Windows NT documentation for information about how to use the Event Viewer.
Use your Windows NT utilities to monitor disk usage regularly and take appropriate action to prevent disks from filling up. To conserve disk space, delete files that are no longer needed. Create new file services on your disks as needed to minimize the overhead involved in accessing files on fewer file services.
Backing Up StreetTalk File Services
Use your Windows NT backup utility to back up your StreetTalk for Windows NT file services regularly. StreetTalk File maintains the information needed to support the Banyan Access Rights Lists (ARLs) and OS/2 Extended Attributes (EAs) for a file service object in a directory separate from the object itself. To properly back up ARLs and EAs, you need to back up all files in the following directory:
C:\Program Files\Banyan\File\Data
Refer to the StreetTalk for Windows NT Release Notice for information about the backup utility recommended for use with StreetTalk file services.