Banyan VINES

Windows 95 can be installed and run with Banyan VINES version 5.52(5) or later. Banyan VINES servers do not show up in Network Neighborhood. You can use the Map Network Drive dialog box in Windows 95 to connect to servers.

Banyan VINES as the primary network.

If real-mode support for Banyan is installed using a Banyan LAN driver, Windows 95 can support Banyan as the primary network. Banyan is also providing a 32-bit network client to be available after the release of Windows 95. Contact your vendor's sales support representative for information about the availability and features provided with this new client.

Banyan VINES as an additional 16-bit Windows 95 client.

If Banyan is installed with an NDIS 2 network adapter driver, then 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.

To set up Windows 95 with Banyan VINES real-mode network client support

If you are running on an Ethernet network, make sure that the Banyan VINES client is already installed under MS-DOS, Windows 3.1, or Windows for Workgroups. The network should be running when you start Windows 95 Setup. Then follow the steps in "Installing Support for Other Networks: An Overview" earlier in this chapter. No other steps are required.
– Or –
If you are running on a token-ring network, run Windows 95 Setup and choose the Custom setup type. In the Network Configuration dialog box, add Banyan Token Ring as the network client. Setup cannot detect Banyan as a token-ring network client.

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.

The following table shows the entries required in configuration files when Banyan VINES real-mode network support is installed with Windows 95, 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.

Banyan VINES as Primary Network

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

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$