Previous | Next

Banyan Enterprise Clients and Banyan VINES

Windows 98 can be installed and run with the following Banyan clients:

You should run a protected-mode client rather than a real-mode, 16-bit client.

This section discusses how to run Windows 98 with Banyan Enterprise Client 7.32 or later and Banyan VINES 7.1 and later. For information about running Windows 98 with Banyan Enterprise Clients for Windows 95, contact Banyan.

If you are using a 16-bit client, Banyan VINES servers do not show up in Network Neighborhood or Windows Explorer. You must use the Map Network Drive dialog box in Windows 98 to connect to servers.

However, if you are using a Banyan Enterprise 32-bit client, you can view Banyan file and print services from within Network Neighborhood.

Banyan Enterprise Client 7.32 or later supports system policies, and Banyan Enterprise Client 8.02 or later supports user profiles. Refer to your Banyan documentation for more information.

Banyan Enterprise Clients

This section describes how to install, uninstall, and configure Banyan Enterprise Clients on Windows 98. For information about how to upgrade to Banyan Enterprise Client from real-mode versions of Banyan clients, contact your Banyan vendor.

Installing Banyan Enterprise Client on Windows 98

This section describes how to install and uninstall Banyan Enterprise Client.

To install Banyan Enterprise Client after Windows 98 Setup

  1. In Control Panel, double-click Network.
  2. On the Configuration tab, click Add.
  3. In the Select Network Component Type dialog box, select Client.
  4. Click Add.
  5. In the Select Network Client dialog box, click Have Disk.
  6. Enter the directory where your installation files are located, and then click OK.
  7. Follow the instructions on the screen.

To uninstall Banyan Enterprise Client after Windows 98 Setup

  1. In Control Panel, double-click Network.
  2. On the Configuration tab, select Banyan Client for Windows.
  3. Click Remove.
  4. Select Banyan Vines Protocol for 95.
  5. Click OK.
  6. When prompted, reboot the computer.

Configuring Banyan Enterprise Client

Banyan Common Logon is enabled by default. If you want to disable it, you must do so from the Network option in Control Panel.

The following example shows a sample Autoexec.bat entry when Banyan Enterprise Client protected-mode network support is installed with Client for Microsoft Networks either as a primary network or as a secondary network:

c:\win95\system\bansvc

Table 17.20 shows Banyan system files and their functions.

Table 17.20 Banyan system files and functions

Primary Banyan system files Function
Bancom.vxd Banyan IP communications stack
Vinesifs.vxd Network redirector
Bansvc.com MS-DOS interface enabler
Vsnet32.dll Net provider
Vnsprn32.dll Print provider
Vnsapi32.dll Banyan Toolkit API

Banyan VINES 16-bit Client

You should use the 32-bit clients Banyan Enterprise Client version 7.32 or later instead of the Banyan VINES 16-bit client. For information about the benefits of using 32-bit, protected-mode clients see "Issues with Windows 98 on Other Third-Party Networks" earlier in this chapter. Also, Banyan no longer supports the 16-bit client.

If you are already using the Banyan VINES 16-bit client and you want to upgrade to the 32-bit client, you cannot do so using Msbatch.inf. Instead, you should wait until after Windows 98 Setup to upgrade to the 32-bit client.

If you do choose to use the Banyan VINES 16-bit client, you should upgrade to version 7.1 or higher. Microsoft no longer supports versions lower than 7.1. You should upgrade before you run Windows 98 Setup.

To upgrade to version 7.1

  1. Obtain a patch from Banyan and apply it to at least one Banyan server on your network.
  2. Run Newrev to upgrade all the Banyan clients on which you will be installing Windows 98.
  3. Run Windows 98 Setup.

Banyan can be installed as an additional 16-bit network client, and you can install 32-bit, protected-mode clients, such as Client for Microsoft Networks or Client for NetWare Networks.

Installing the Banyan VINES 16-bit Client

If you want to set up Windows 98 with Banyan VINES real-mode network client support on an Ethernet network, make sure that the Banyan VINES client is already installed and working under MS-DOS, Windows 3.1, Windows for Workgroups, or Windows 95 before you run Windows 98 Setup.

Note

If you are running Banyan VINES with monolithic drivers, you must use the PCCONFIG utility provided by Banyan to change Banyan drivers to NDIS drivers. Make sure that the section name matches the driver name.

Configuring the Banyan VINES 16-bit Client

Tables 17.21 and 17.22 show the entries required in configuration files when Banyan VINES real-mode network support is installed with Windows 98, depending on whether Banyan VINES is installed as the primary network only (connecting to a Banyan server) or is installed with Client for Microsoft Networks. These entries are for NDIS drivers.

Table 17.21 Banyan VINES as primary network, using NDIS

Configuration file Entries
Autoexec.bat cd \banfiles
ban
ndisban ; ndtokban for token ring
redirall
netbind
arswait
z:login
c:
cd\
Config.sys device=c:\banfiles\protman.dos /i:c:\banfiles
device=c:\
banfiles\ndis2driver eg: exp16.dos
Protocol.ini [PROTOCOL MANAGER]
drivername=protman$

[VINES_XIF]
drivername=ndisban$ ; ndtokban$ for token ring
bindings=MS$EE16

[MS$EE16]
drivername=EXP16$
interrupt=5
ioaddress=0x300
iochrdy=late


Table 17.22 Banyan VINES with Client for Microsoft Networks

Configuration file Entries
Autoexec.bat c:\windows\net initialize
cd \
banfiles
ban
ndisban ; ndtokban for token ring
redirall
c:\windows\net start
arswait
z:login
c:
cd\
Config.sys rem device=c:\banfiles\protman.dos /i:c:\banfiles
rem device=c:\
banfiles\ndis2driver eg: elnkii.dos
Protocol.ini [NDISBAN$] ; NDTOKBAN$ for token ring
drivername=NDISBAN$ ; NDTOKBAN$ for token ring
bindings=ELNKII$

[NWLINK$]
drivername=NWLINK$
frame_type=4
cachesize=0
bindings=ELNKII$

[NETBEUI$]
drivername=NETBEUI$
lanabase=0
sessions=10
ncbs=12
bindings=ELNKII$
[ELNKII$]
drivername=ELNKII$
transceiver=external
interrupt=2
ioaddress=0x280
maxtransmits=12
datatransfer=pio_word
xmitbufs=2

[PROTMAN$]
priority=ndishlp$
drivername=protman$

[NDISHLP$]
drivername=ndishlp$
bindings=ELNKII$