[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:

can't find

z:vvinesd.386
0
xfilterx
Asked:
xfilterx
1 Solution
 
rmhinriCommented:
what os? are you on a network....which drive is drive z. what type of computer?
0
 
cmcgeeCommented:
Review the following Technet article. Check your Autoexec.bat for the lines that it states below. If necessary, you may need to reload Banyan Vines.




How to Set Up Banyan VINES in Windows 95
Last reviewed: February 22, 1996
Article ID: Q123877
 
 


--------------------------------------------------------------------------------

The information in this article applies to:
Microsoft Windows 95


SUMMARY
This article describes how to install Banyan VINES connectivity in Microsoft Windows 95.

NOTE: You must be using Banyan VINES version 5.52(5) or later.



MORE INFORMATION

Make sure Banyan VINES connectivity works before you install Windows 95.

Install Windows 95.

Use the right mouse button to click the Network Neighborhood icon, then click Properties on the menu that appears.

Add the following components to Network properties if they are not present:


    - Network adapter
    - Banyan DOS/Windows 3.1 client
    - Banyan VINES Protocol

The AUTOEXEC.BAT file should contain the following lines:


      Path=Z:\...
      C:\WINDOWS\net initialize
      cd \banyan
      ban /nc
      ndisban
      redirall
      C:\WINDOWS\net start
      arswait
      z:login
NOTE: This information assumes that the Banyan files are located in the Banyan directory. If this is not the case, adjust the lines above accordingly.


Restart your computer to make sure you are prompted to log on to Banyan VINES, and that you can access any Banyan VINES mapped drives.
NOTE: Because Banyan VINES servers do not have browsing capabilities, they do not appear in your Network Neighborhood.


Troubleshooting

Check the network adapter in the Network property sheet to make sure it is set for a real-mode 16-bit NDIS driver.

Check the PROTOCOL.INI file in the Windows directory for the following sections:
[BAN$VINES] DriverName=ndisban$ Bindings=EXP16$ Lanabase=1

[NDISBAN$] DriverName=NDISBAN$ Lanabase=1 Bindings=EXP16$

NOTE: This example uses the Intel EtherExpress 16 network card.


Run PCCONFIG.EXE from your Banyan VINES directory to make sure its driver name matches the "Bindings=" line above.

Make sure drive Z has the latest VINES.DRV and VVINESD.386 files.

If you are using token-ring, your AUTOEXEC.BAT should contain NDTOKBAN instead of NDISBAN.

Try to load drivers high. (They require a lot of conventional memory.)

If you add the Banyan VINES client, it does not add the Banyan VINES protocol. However, if you add the Banyan VINES protocol, the Banyan VINES client is automatically added.

To set up a printer, you must run VINES.EXE from drive Z and choose printer services. You, or the network administrator, must set up print queues. This sets up a port (LPT1, for example) to be redirected to a network printer. In Windows 95, you can install a local printer on LPT1 and it should work correctly.

If you receive a message stating that your version of Banyan VINES is not the latest version, edit the Vines.ini file as follows
[NEWREV] dontcopy=1 vines.version=5.5<x> (<x>) USA windows.version=3.95

where <x> is the version of Banyan VINES you are using.


If you do not see the Banyan VINES screen before Windows 95 starts, there is a problem with the VINES drivers in the AUTOEXEC.BAT file.

If you can log on to the network but you cannot map Banyan VINES drives, or drives mapped in the login script appear as local drives, make sure that Z: is included in the Path statement in the AUTOEXEC.BAT file.  

0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now