Managing the NWS filesystem

Loading Windows onto the network

You can load Windows onto a network in several ways.

Instructions for the first two options are included in the documentation that came with your Windows software. Instructions for loading program and user files on the server are included in this topic.

Following are some advantages of having all Windows files installed on the server:

The only disadvantage of having all Windows files installed on the server is that it causes more network traffic.

Files needed for NetWare functionality in Windows

Use the following files to run Windows with NetWare functionality. These files are in the Workstation for DOS/Windows client kit that is installed with NetWare Services.

NETWARE.DRV
NetWare device driver. Contains executable code for NetWare-related functions.

NETWARE.HLP
Help file for NETWARE.DRV.

NETWARE.INI
Initialization file for NETWARE.DRV and other Windows utilities for NetWare. Automatically created by NETWARE.DRV.

NWPOPUP.EXE
Handler for broadcast messages.

VNETWARE.386
Virtual NetWare device driver. Performs virtualization among sessions when Windows is in 386 Enhanced mode.

VIPX.386
Virtual IPX(TM) device driver. Virtualizes IPX communications among sessions when Windows is in 386 Enhanced mode.

Guidelines for running windows on the network

Follow these guidelines for running Windows on the network:

Loading and setting up Windows

The following list describes the prerequisites:

Carry out the following procedure:

  1. Install Windows server software using the SETUP /A option.

    For complete information about the Windows SETUP options and the installation procedure, see the documentation that came with your Windows software.

  2. Create a Group object for users who will be running Windows.

    For instructions on creating a Group object, see ``Managing group objects''.

  3. Make the Windows Group object a trustee of the Windows directory.

    For instructions on granting trustee assignments, see ``Adding a trustee to a directory or file''.

  4. Create a directory for each user to store user-specific Windows files.

    WIN.COM and files such as .GRP and .INI files are stored here.

  5. Add the following information to the system login script.

    An example of the syntax used for these login script entries appears at the end of this step.

    The following example shows the container login script entries you would add to set up Windows 3.1 on the network:

    IF MEMBER OF "WIN31" THEN
    MAP INS P:=SYS:USERS\%LOGIN_NAME\WIN31
    MAP INS S16:=SYS:APPS\WINAPPS\WIN31
    SET TEMP = "P:\USERS\%LOGIN_NAME\WIN31\TEMP"
    END
    

  6. Set up the workstations by completing the following steps.
For more information about creating login scripts, see ``Customizing the user environment''.
© 1999 The Santa Cruz Operation, Inc. All rights reserved.
UnixWare 7 Release 7.1.1 - 5 November 1999