Chapter 15 - Using VINES for OS/2 2.x
How you log in to the Banyan network from an OS/2 workstation depends on how your system administrator has set up your working environment. Before going any further, check with your system administrator for login details. If the administrator has not modified your working environment, use the instructions in the following sections.
To Log In to the Banyan Network from an OS/2 Workstation
1. Open either an OS/2 window or a full-screen window.
2. At the OS/2 prompt, enter:
cd \VINES
Where <VINES> is the name of the directory in which VINES is installed.
3. At the OS/2 prompt, enter ban. The Login screen appears.
4. Enter your StreetTalk user name and password.
As your user profile processes, your network drive and network printer mappings appear on your screen. When the OS/2 command prompt appears, you are logged in to the network.
The LOGOUT command works identically in OS/2 and DOS. To log out of the network from the OS/2 prompt, enter logout and press ENTER.
Note: If multiple OS/2 sessions are open, each running Banyan networking applications, all of the Banyan networking applications exit when you log out from any OS/2 session.
Printing from OS/2 Workstations
Banyan networking software running on OS/2 workstations supports the Banyan SETPRINT and BPRINT programs, as well as the Print Manager functions built into OS/2.
The network printer must match the printer driver installed as part of the OS/2 installation procedure. For this reason, make sure you install the printer drivers you need for the network printers you will use before you use Banyan print services.
You can use any Banyan print service. The physical printer can be connected to either a Banyan server or a DOS workstation that runs the PC printing option.
To use and manage Banyan print services, refer to the VINES User's Guide for DOS and OS/2 and Managing VINES Services.
The SETPRINT command, like the SETDRIVE command, applies globally to all sessions on your workstation. For this reason, wait until a print job completes before you use the SETPRINT command to change network printers. As soon as the complete print job is sent to a print queue, use SETPRINT to select a new printer.
It is recommended that you copy PCPRINT.EXE to the workstation local drive. Due to OS/2's virtual memory swapping and the potential for lost connections, doing so results in better performance.
Make sure you install the printer drivers you need for PCPRINT on your workstation before you use Banyan print services. If you plan to use COM1 or COM2, make sure you install serial device drivers.
To begin a PCPRINT session, enter the following command from an OS/2 command prompt, using this syntax:
[C:] pcprint print_service [LPT1, LPT2, LPT3, COM1, COM2]
The print service must be previously created through the MSERVICE command and configured as a remote destination.
There are some differences from the DOS version:
PCPRINT will not load if the printer port (LPTn) is already mapped in the user's profile through a SETPRINT statement or the SETPRINT command. If you run PCPRINT, you cannot use SETPRINT to map to the same printer port used by PCPRINT. You can run multiple PCPRINT sessions, provided you specify different print services. If a user logs out, the PCPRINT session does not exit and continues to print. However, if a different user logs in who does not have access to the print service, the login causes PCPRINT to exit.
To exit a PCPRINT session, press CTRL-C or close the window.
When you reset a network drive to a new file service using the SETDRIVE command, the change affects all current and future sessions on your OS/2 Desktop Manager.
Note: Use caution when changing network drives. Be aware of active applications that are running in other windows. Using SETDRIVE to reset a drive mapping while an application is running in another window can disrupt that application.
If you use files with OS/2 extended attributes, check whether the service you want to use supports OS/2 extended attributes. File services on servers running VINES 4.11(5) or greater support OS/2 extended file attributes. The SETDRIVE command has a switch, /STATUS, that lets you check the VINES protocol of any VINES file service.
Like the /LIST switch, the /STATUS switch displays the user's current drive settings. In addition, the /S switch adds a line for each drive that reports the file service protocol type and the VINES revision number associated with that file service protocol, as shown below:
Drive F: =] ProjectFiles@Marketing@WCTUS
SMB Protocol: VINES 4.11
Drive H: =] ProjectApps@Marketing@WCTUS
SMB Protocol: VINES 5.50
Note that SMB stands for the industry-standard Server Message Block protocol.
Note: The SETDRIVE /S switch does not reliably determine which VINES software revisions are available on the network. The SETDRIVE /STATUS command only shows the revisions for the drives to which file services are mapped in your user profile. It does not show all the files services on the network.
This section describes how to run Banyan networking DOS programs in a DOS session.
To run Banyan networking DOS programs, you must:
1. Set a drive to the DOS VINES Files directory on a server.
2. Specify the drive letter in the PATH statement in your AUTOEXEC.BAT file.
3. Load the BANSVC.COM TSR, as described in "DOS Redirector Support" later in this chapter.
Drive Z contains your OS/2 VINES Files. For this reason, you need to map, or set a drive to, a DOS VINES Files file service. All Banyan networking DOS applications make use of DOS VINES Files.
To Set a Drive to DOS VINES Files
1. Enter a SETDRIVE statement in the user's user profile according to the following syntax (this example uses the letter Y, and USA for the Location):
SETDRIVE Y "VINES Files@Server_name@Servers" /Root:DOS\USA
Be sure to specify the /Root:DOS\USA parameter. The SETDRIVE statement should appear on one line. Due to page constraints, the line appears on two lines in this document.
2. Specify the drive letter in the PATH statement in the user's AUTOEXEC.BAT file. Make sure the drive letter Z does not appear in the AUTOEXEC.BAT PATH statement.
3. Add the following line to the AUTOEXEC.BAT file:
ASSIGN Z=Y
The ASSIGN statement is required because some DOS programs look for ancillary files, such as .MSB files on drive Z. This does not affect OS/2's drive Z, because it is not visible to DOS.
The next section describes the Virtual Device Driver (VDD) that provides DOS Redirector support.
VINES for OS/2 2.x includes support for the DOS Redirector. This virtual device driver lets you run DOS programs created with the VINES Toolkit version 4.10 or later.
Note: Banyan networking DOS programs created with Toolkit versions earlier than 4.10 are not supported.
There are two components to this support:
VBAN.SYS - This device driver is installed by the VCLIENT program and a line is added to the CONFIG.SYS file. It assumes a DOS interrupt of 63. If you run applications that are not VINES which require interrupt 63, modify the CONFIG.SYS file to change the interrupt value. Refer to "Changing the Interrupt Value" later in this chapter for more information.
BANSVC.COM - This DOS TSR program performs DOS Redirector functions that cannot be handled by VBAN.SYS.
For more information, refer to "Using BANSVC.COM" later in this chapter.
The rest of this section discusses administrator and user issues. System administrators should disseminate pertinent information on using the BANSVC.COM TSR program to their users.
This section discusses how to change the default interrupt value (if necessary) and VBAN.SYS error messages. If you make any changes, you need to shutdown and restart your workstation for these changes to take effect.
VBAN.SYS assumes a DOS interrupt of 63. Because two applications that use the same interrupt cannot run at the same time, it is necessary to change the interrupt value if your application that is not a VINES application requires interrupt 63.
To change the interrupt value, modify the DEVICE=VBAN.SYS line in your CONFIG.SYS file using the following syntax:
DEVICE=VBAN.SYS /INT=[60-66]
For example, to change the interrupt value to 65, use this line:
DEVICE=VBAN.SYS /INT=65
VBAN.SYS Error Messages
VBAN.SYS error messages appear in a message popup window. If your application causes VBAN.SYS to return the error message, "Function not supported," you may want to check with the application vendor for a later release of the product.
Users need to run the BANSVC.COM TSR before running VINES DOS programs in a DOS session. The TSR can be placed in the user's AUTOEXEC.BAT file or can be run manually from a DOS session.
Users must run this TSR before running any VINES DOS applications.
When this TSR loads, a message appears confirming that the TSR has started:
VINES DOS Interface for OS/2 2.x has successfully installed.
If you place the TSR in your AUTOEXEC.BAT file, this message appears each time you start a DOS session.
Selecting a Redirector for an OS/2 Workstation
OS/2 workstations currently use OS/2 revisions 2.x, as well as version 2.x of the redirector. On an OS/2 workstation, the redirector is loaded as a standard OS/2 Installable File System (VINES.IFS or VINES2.IFS for OS/2 2.x).
Because OS/2 can manage multiple Installable File Systems (IFSs), the DOS redirector can coexist with IFS redirectors from other network vendors.
The redirector program diverts DOS commands entered at a workstation to the network. A redirector executable file must be in the Banyan networking workstation directory. For more information about the redirector, refer to Chapter 6.
Running Banyan Windows Programs
You must first follow the same steps described in "Running Banyan DOS Programs" before running Windows programs with Banyan networking software.
To run Windows applications that are aware of VINES software, you need to specify VINES.DRV in the [boot] section of the SYSTEM.INI file. This file is located in the \OS2\MDOS\WINOS2 directory:
[boot]
useos2shield=1
os2shield=winsheld.exe
shell=progman.exe
network.drv=vines.drv
comm.drv=comm.drv
sound.drv=sound.drv
When you install OS/2 2.x, the NETWORK.DRV= statement is blank.
In the [boot description] section, another NETWORK.DRV= statement reads:
network.drv=Network not installed
This message appears when you click Windows Setup. You can change this text string to "Banyan Network." Changing this statement has no effect on running Banyan networking Windows programs.
The Command Reference summarizes all of the VINES commands and programs, and the workstations to which each applies.
