• Server
  • Installing Microsoft Service for NDS from Service Pack 1
  • Uninstalling NDS Service
  • Installing the Service for NDS from Windows 95 OEM Service Release 2
  • Using the Microsoft Service for NDS
  • Running Scala with Microsoft Services for NDS
  • Novell Client 32 for Windows 95
  • Installing Novell Client 32 for Windows 95
  • Using Novell Client 32
  • Running Scala with Novell Client 32 in bindery mode
  • Running Scala with Novell Client 32 in a Directory Tree
  • Example 1 The user SCALA is in the same context where TESTER_SYS is: Example 2
  • Microsoft Service for NDS
  • Novell Client 32
  • Running Scala on a Windows 95 computer in the Novell nds environment




    Download 41.57 Kb.
    Sana21.03.2017
    Hajmi41.57 Kb.



    Scala Support

    Running Scala on a Windows 95 computer in the Novell
    NDS environment


    Standard client software for the NetWare Networking included into the original Microsoft Windows 95 package was not able to work with the NetWare Directory Service (NDS). Therefore several vendors have developed new NDS clients for Windows 95. This document covers installation and configuration of NDS clients developed by Microsoft and Novell.

    Software

    Server


    • Novell NetWare 4.x

    • Novell IntranetWare 4.11

    Workstation


    • Windows 95

    • Windows 95 OEM Service Release 2

    Clients

    Microsoft Services for NDS

    Overview


    There are three Microsoft Services released for NDS. The first client was issued before Service Pack 1 for Windows 95 was. It contains files as on 13 Oct, 1995. The second client was included into the Service Pack 1 as an additional component. The installation of both these clients is identical. They only differ from each other by the NWNP32.NW4 file:




    MS NDS before SP 1

    MS NDS in SP 1

    File name

    Date

    File size

    Date

    File size

    NWNP32.NW4

    13 Oct, 1995

    136 704

    31 Dec, 1995

    138 752

    The third client was included into the Windows 95 OEM Service Release 2.


    Scala (Btrieve) works with all these clients software in the client-server mode but only if you log in to the Novell server in a bindery mode. If you wish to log on to the Novell Directory Tree and to work with Scala in the client-server mode, you have to use not Windows 95 but either the client service developed by Novell or Windows NT Workstations.

    Installing Microsoft Service for NDS from Service Pack 1


    Microsoft Service for NDS is included as an additional component to the Service Pack. As a rule, it is located in the directory \ADMIN\COMPONTS\MSNDS. If you have Windows 95 installed and you wish to install MS Service for NDS, you should do it via the Network Control Panel. To install MS Service for NDS on a computer running Windows 95, follow these steps:

    1. In Control Panel, double-click on the Network icon.

    2. Click on Add.

    3. Double-click on Service.

    4. Click on Have Disk, and type the drive name for the disk or network drive where the MS Service for NDS files are located.

    Note: Do not click on Cancel during the installation. If, for some reason, you decide not to install the Service for NDS, you must complete the installation process, and then remove the Service for NDS. For more information about removing the Service for NDS see “Uninstalling the Service for NDS” below in this document.

    1. Next time you start your computer, you will be prompted to log on to the NDS tree. Make sure that the dialog box complies with the correct context and tree.

    If you wish to install MS Service for NDS as a part of the new Windows 95 installation, you can do it in either of the two following ways:

    1. You can install MS Service for NDS as a part of Windows 95 automated installation. Automated installation routine employs the MSBATCH.INF file to install Windows 95 without any user’s intervention. Once this option has been chosen, you do not need to install MS Service for NDS separately for each computer. See more details about the automated installation procedure in the Windows 95 Resource Kit documentation.

    2. You can also install MS Service for NDS from the Windows 95 setup program. Executing Windows 95 setup, choose Custom installation, and follow steps 2-5 of the above-described procedure.

    Uninstalling NDS Service


    Before to begin, make sure that your Windows 95 setup disk is at hand. The removal program will prompt when you require this disc for it contains some necessary files.

    • In Control Panel, double-click on the Network icon.

    • Click on Service for NetWare Directory Services, and then click on Remove.

    Note: At copying the networking files from your Windows 95 Setup disk, Windows 95 will repeatedly display a message prompting that older version of the files is being copied to your computer, and asking whether you wish the newer versions, currently on your computer, to be kept. To remove the Service for NDS, click on No for the following files: NWREDIR.VXD, NWNP32.DLL and NETWARE.TMP.

    Installing the Service for NDS from Windows 95 OEM Service Release 2


    If you have the Windows 95 OEM Service Release 2 (OSR2) already installed, and you wish to install the Service for NDS, you must do this via the Network Control Panel. To install the Service for NDS on a computer running Windows 95 OSR2, follow these steps:

    1. In Control Panel, double-click on the Network icon.

    2. Click on Add.

    3. Double-click on Service.

    4. Choose the Service for NDS.

    5. Next time you start your computer, you will be prompted to log on to the NDS tree. Make sure that the dialog box complies with the correct context and tree.

    If you wish to install MS Service for NDS as a part of the new Windows 95 installation, you can do it in either of the two following ways:

    1. You can install MS Service for NDS as a part of the Windows 95 automated installation. Automated installation uses the MSBATCH.INF file to install Windows 95 without any user’s intervention. In this case there is no need to install MS Service for NDS separately for each computer. For more details refer to the Windows 95 Resource Kit.

    2. You can install MS Service for NDS from the Windows 95 setup program. At executing Windows 95 setup, choose Custom installation, and follow steps 2-5 from the procedure described above.

    Using the Microsoft Service for NDS


    Microsoft Service for NDS allows you to log on to the Directory Tree as well as to the Novell server in a bindery mode. You can choose the log-on type in the advanced settings:



    or


    Running Scala with Microsoft Services for NDS


    The only supported configuration for running Scala (Btrieve) in a client-server mode in a Novell NDS environment uses the bindery mode. If you log on to the Directory Tree, Btrieve requester will not be able to recognize the network drives which had been mapped by loggin scripts or by Windows 95 tools. These network drives are as on the following screen:

    Thus, if you wish to work with Scala and to use Microsoft Service for NDS, you must log in to the Novell server only in the bindery mode.



    Note: We strongly recommend that you primary log in to the server where Scala is located. Otherwise employ the same user names for both the server where Scala is located and for the primary logging to Windows 95.

    If you wish to log on to the Directory Tree, you should use Novell Client 32 for Windows 95. However there are some limitations described in the next chapter.


    Novell Client 32 for Windows 95

    Overview


    At the end of 1996 Novell Corp. released a new operation system titled IntranetWare 4.11. This bundle includes Novell Client 32 for Windows 95. If you do not have IntranetWare, you can get this client software from the Novell ftp server: ftp://ftp.novell.com.

    Installing Novell Client 32 for Windows 95


    If IntranetWare is installed on the server, the client software is in the directory \PUBLIC\CLIENT\WIN95\IBM_ENU on the volume SYS.

    Note: If you cannot find the client software in this directory, install it from the IntranetWare CDs.

    Run SETUP.EXE and clear checkbox “Upgrade NDIS driver to ODI automatically, if available”. Then follow the instructions on the screen. After rebooting the computer the Novell Client 32 will be installed.


    Using Novell Client 32


    Novell Client 32 allows you to log on into the Directory Tree as well as to the Novell server in the bindery mode. The login type can be chosen in the Novell Client properties:

    Also it can be done by logging to the system:



    For more details refer to the documentation provided with the Novell Client.


    Running Scala with Novell Client 32 in bindery mode


    There are no special requirements for running Scala using this client software if you are logging into the Novell server in the bindery mode.

    Note: We strongly recommend to make primary logon into the server where Scala is located. Otherwise use the same user name for both the server where Scala is located and for Windows 95 primary logon.

    Running Scala with Novell Client 32 in a Directory Tree


    If you have Novell Client 32 installed, you can work with Scala (Btrieve) in client-server mode in the Directory Tree mode. Nevertheless there are some limitations. Scala users must be in the same bindery context where Scala server is located. For more information about bindery contexts please refer to the Novell Documentation about NDS. You can either create one special context for the server with Scala and for all Scala users or to integrate several contexts into a single one on the server by using ”SET BINDERY CONTEXT=” command.

    Let us assume that Scala is located at the volume .CN=TESTER_SYS.OU=LAB.O=SCALA. In this case the following configurations are allowed:


    Example 1


    The user SCALA is in the same context where TESTER_SYS is:


    Example 2


    The user AC is in the context OU=ACCOUNT.O=SCALA. Contexts OU=LAB.O=SCALA and OU=TEST.O=SCALA are integrated into a single one on the server:



    Note: We recommend making primary logon into the Directory Tree. Otherwise we strongly advise to use the same user name for both the server where Scala is located and for the Windows 95 primary logon.

    We strongly recommend to use only login scripts to map the network drive where Scala is located. Login script should be as the following one:



    - Scala will be able to be run from all drives mapped in this login script.

    If you use a Network Neighborhood panel for mapping the drives, you should map a network drive using the server name only (bindery-style convention), do not use NDS names.


    Summary


    Btrieve requester requires the information from the NetWare Bindery to establish the connection to the server and authenticate user’s access rights to a specific Btrieve data file. Btrieve requester currently does not support NDS calls to accomplish these tasks. Summing up we have the following:




    Microsoft Service for NDS

    Novell Client 32

    Login into the Directory Tree (NDS)

    Does not work.

    Works with some limitations: both the users and Scala server should be in the same bindery context.

    Login in bindery mode

    Works.

    Works.

    Our recommendations:



    • If you are not planning to work in the Directory Tree, we recommend using standard Microsoft client for NetWare provided with the original Windows 95 package.

    • If you are planning to work in the Directory Tree, the only solution is to install Novell Client 32.

    Troubleshooting

    Microsoft Service for NDS


    Btrieve error 20 “The Microkernel or Btrieve requester is inactive”:

    • Check that you have copied all *.DLL files from the directory \BTI\NETWARE\WIN32\BIN on the server to the \WINDOWS\SYSTEM on the workstation.

    • Check that you logged on in the bindery mode.

    Btrieve error 94 “The application encountered a permission error”:

    • Check that you primary logged on to the server where Scala is located.

    • If you failed to make the log-on to be primary, check the user names. They should coinside. Btrieve (at least version 6.15.430 for NetWare) makes a problem: the user’s name is taken only from the primary log-on. If the name exists and has rights on the server where Scala is located, Btrieve uses this name. Otherwise Btrieve displays an error code 94.

    Novell Client 32


    Btrieve error 20 “The Microkernel or Btrieve requester is inactive”:

    • Check that you have copied all *.DLL files from the directory \BTI\NETWARE\WIN32\BIN on the server to the \WINDOWS\SYSTEM on the workstation.

    • Check that you do not use Network Neighborhood to map the network drive using NDS names.

    Btrieve error 94 “The application encountered a permission error”:

    • Check that you primary logged on into the Directory Tree on the server (or in the bindery mode) where Scala located.

    • If you failed to log on primary, check your user’s names. They should coincide. Btrieve (at least version 6.15.430 for NetWare) makes a problem: the user’s name is taken only from the primary log-on. If the name exists and has rights on the server where Scala is located, Btrieve uses this name. Otherwise Btrieve displays an error code 94.

    • Check that both you and Scala server are in the same bindery context.



    The software system for local and global business management

    Page


    Download 41.57 Kb.

    Bosh sahifa
    Aloqalar

        Bosh sahifa


    Running Scala on a Windows 95 computer in the Novell nds environment

    Download 41.57 Kb.