This document describes some steps that you need to take after 
you install OPENSTEP Enterprise for Windows. It also describes:

 Changes made to environment variables during installation
 How to start and stop OPENSTEP processes manually
 How to uninstall OPENSTEP manually
 Some issues related to Enterprise Objects Framework


After Installation
==================

Depending on what options you selected during installation, the following
sections may contain important post-install information.

Enterprise Objects Framework
----------------------------

If you have installed Enterprise Objects Framework, you should also install 
the appropriate client libraries for the databases that you intend to connect 
with.

With the exception of the Enterprise Objects Framework Reference documentation,
which is in Windows Help format, all Enterprise Objects documentation is 
provided in PDF only. PDF readers for various platforms can be found on the
OPENSTEP Enterprise CD-ROM in the /3RD_PRTY directory. Or, you can download one 
from the following World Wide Web site:

     http://www.adobe.com/acrobat/



Configuring Project Builder's PVCS/CVS Support
----------------------------------------------

If you've installed the PVCS Support package, you'll need to instruct Project 
Builder to load an SCM bundle from that package before you can use either PVCS 
or CVS from within Project Builder. Following that, you'll need to set one or
two defaults. 

The following procedure illustrates how to cause Project Builder automatically 
load a bundle:

1. Launch Project Builder, and select Preferences from Project Builder's main 
   menu.
2. Locate the Bundles pane in the Preferences Panel, and click Add.
3. In the file browser that is displayed, traverse to 
   $NEXT_ROOT/NextDeveloper/ProjectBuilderBundles. Double-click the appropriate 
   bundle (PVCS or CVS).
4. Quit and then re-launch Project Builder to force the SCM bundle to load.

If you're using PVCS, enter the following command at a Bourne Shell prompt (all 
on one line) to specify the location of the PVCS executable. Substitute the text 
delineated by <> characters as appropriate for your installation.

   defaults write ProjectBuilder PVCSDefaults '{path="<PVCS Executable Path>"; userName=unknown;}'

PVCS users should set the following default to YES or NO, depending on whether 
or not you want to lock files automatically when you start to edit them in Project 
Builder:

   defaults write ProjectBuilder lockOnEdit <YES|NO>

If you're using CVS, enter the following command at a Bourne Shell prompt to 
specify the location of the CVS executable (substituting the text delineated by 
<> characters as appropriate for your installation):

   defaults write ProjectBuilder CVSDefaults '{path="<CVS Executable Path>";}'


Memory Requirements
-------------------

For optimal performance, we recommend that any machine on which you're running
OPENSTEP Enterprise Developer have 48 MB of available memory. In addition, your 
Virtual Memory paging file sizes should be set to (at least): 64 MB initial, 
128 MB maximum. Finally, the TCP/IP networking protocol must be configured and 
enabled.

Windows NT systems on which you're deploying OPENSTEP applications should have 
32 MB of available memory. Again, the TCP/IP networking protocol must be 
configured and enabled.



Changes to Environment Variables
================================

When Configure Environment Variables is selected in the Choose Options dialog 
box, the setup program makes the following changes to your System Environment 
Variables. You can view these variables in the System Control Panel:

- $NEXT_ROOT shows the drive and directory where the root OPENSTEP directory 
  is located. (Make sure there is a trailing slash.)

- For developer installations, "Lib" includes the resolved paths for
  NextDeveloper/Libraries and LocalDeveloper/Libraries (both relative to
  $NEXT_ROOT).

- "Path" includes the resolved paths for NextLibrary/Executables and, for
  developer installations, LocalDeveloper/Executables,
  NextDeveloper/Executables, and NextDeveloper/Executables/Utilities (all 
  paths are relative to $NEXT_ROOT).

Note:  The paths that identify the various OPENSTEP directories in "Lib" and 
"Path" must come before the corresponding Microsoft directory definitions.



Starting OPENSTEP Processes Manually
====================================

During installation you can request that the various processes needed by 
OPENSTEP be started automatically when you log in. The installer does this 
by creating entries for each of those processes in your Startup (Common) 
program group. If you elected to start these processes manually, you must 
locate and start them.

The two processes that you must start first are services called MachD and 
nmserver. To start these services, open a Bourne shell (by selecting the 
appropriate icon in the OPENSTEP Enterprise program group). Then type the 
following:

	cd $NEXT_ROOT/NextLibrary/System
	machd -install
	nmserver -install

To start the remaining two OPENSTEP runtime processes, locate them in 
the file system (using File Manager or Explorer) and then start them by 
double-clicking. Start them in the following order:

 $NEXT_ROOT/NextLibrary/System/WindowServer.exe
 $NEXT_ROOT/NextLibrary/Frameworks/AppKit.framework/Resources/pbs.exe



Stopping OPENSTEP Processes Manually
====================================

To stop OPENSTEP processes--a step required when uninstalling OPENSTEP, 
described below--first locate the Startup (Common) group containing the 
processes (using the Program Manager for Windows NT 3.51 or the Start 
menu for Windows NT 4.0). Then select or double-click these two processes 
in the following order:

    Pasteboard Server (pbs.exe)
    Window Server (WindowServer.exe)

To stop the OPENSTEP services, open a Bourne shell (by selecting the icon 
in the OPENSTEP Enterprise program group). Then type the following:

	cd $NEXT_ROOT/NextLibrary/System
	machd -remove
	nmserver -remove

For each process, a message will inform you that the process is already 
running and will inquire whether you wish to terminate it. Respond Yes 
to each message. You can also use either the Windows NT Task Manager or 
"Pview" (supplied with Microsoft Visual C++) to terminate processes. 
Terminate them in the same order as listed above.



Uninstalling OPENSTEP for Windows Manually
===========================================

Because OPENSTEP installs all of its files underneath a single 
directory identified by the $NEXT_ROOT environment variable, uninstallation 
is a fairly straightforward process. Essentially, you delete the OPENSTEP 
files, remove any icons that appear in the Program Manager, and clean up 
your Environment Variables.


Delete OPENSTEP Files
---------------------

1. Because the installer may not be able to overwrite running processes, 
   first quit any OPENSTEP or D'OLE applications you're running. Then stop 
   OPENSTEP processes as described in the section "Stopping OPENSTEP 
   Processes Manually," above.

2. Locate the OPENSTEP root directory. This directory is identified by the
   $NEXT_ROOT environment variable. If you are unsure what the root directory 
   is, open the System control panel and look in the System Environment 
   Variables section.

3. Using the Windows NT File Manager or Explorer programs, select the 
   OPENSTEP root directory.

4. Press Delete, or choose Delete from the File menu. A series of message 
   boxes appears, asking you to confirm that you want to delete the selected
   directory and all its contents. Click Yes (or Yes to All) to all messages.

The File Manager deletes each of the files and directories underneath the 
selected directory, and then it deletes the directory itself.


Delete OPENSTEP Icons from Program Groups (Windows NT 3.51)
-----------------------------------------------------------

1. Select--but do not open--the OPENSTEP Enterprise program group 
   icon in the Program Manager.

2. Press Delete, or choose Delete from the File menu. In the Delete 
   confirmation dialog that appears, click Yes.

3. Double-click the Startup (Common) group icon in the Program Manager.

4. If the Startup (Common) group contains icons labeled "MachD", 
   "Mach nmserver," "WindowServer," or "Pasteboard Server," select each 
   icon in turn and press Delete. In the Delete confirmation dialog that 
   appears, click Yes.


Delete OPENSTEP Icons from Program Groups (Windows NT 4.0) 
----------------------------------------------------------

1. Choose the Taskbar option from Settings on the Start menu.

2. Select the Start Menu Programs display of the Taskbar Properties window.

3. Click the Remove button on the Customize Start Menu section. 

4. In the Remove Shortcuts/Folders window, select OPENSTEP Enterprise,
   click Remove, and then click Yes to the confirmation message.

5. In the same window, open the Startup program group by clicking the "+"  
   symbol. Then select the icons labeled "MachD", Mach nmserver," 
   "WindowServer," or "Pasteboard Server." For each icon, press Delete 
   and click Yes to the subsequent Delete confirmation dialog.


Clean up Environment Variables
------------------------------

1. Locate and open the Control Panel window.

2. Within the Control Panel window, double-click the System icon.

3. The System dialog box appears. This dialog box is where you can alter 
   the environment variable settings that Windows NT uses.

4. Select $NEXT_ROOT in the System Environment Variables section. Click 
   Delete.

5. If developer software was installed, select the "Lib" system-environment 
   variable definition. Highlight that portion of the definition 
   corresponding to the OPENSTEP "Lib" directories listed in "Changes to 
   Environment Variables," above, and press the Delete key (do not click 
   Delete). Click Set to register the change.

6. Select the "Path" system-environment variable definition. Highlight those
   portions of the definition that identifies directories corresponding to 
   the OPENSTEP "Path" directories listed in "Changes to Environment 
   Variables," above, and press the Delete key (do not click Delete). 
   Click Set to register the change.

7. Click OK in the System dialog.

This completes the manual uninstallation process.