

			  MWSNT210.TXT 6/23/97 

MindWire is a client/server application that offers features such as
email, chat, live messaging, file library, message folders, and third
party Visual Basic application development for use with the server.
This communications tool is an innovative company solution for a 
business Intranet (and Extranet!) needs.
	  
This release of MindWire NT Server 2.10 is designed to run only on a
Windows NT 4.0 Server machine.  Communication with the server is 
established with the MindWire Client.

***IMPORTANT****
MindWire works best when run with the latest client: 
	MindWire Connector v2.10b dated 6/23/97 or 6/20/97.

For the latest updates and information on MindWire, we encourage you 
to join our community on the world wide web (joining is free) at

	http://www.byoc.com/live/Community.idc?ID=719

or visit Durand's web site at
	 http://www.durand.com

This installation of the Server will install approx 10 MB of data 
transfering from our ftp site.  This installation may be found at 
	ftp://mindwire.durand.com/SlimServ/mwsnt210.exe

so make sure you have a connection established to the internet when 
you install the MindWire Server.  Should transfer be interrupted, 
resuming the installation will start download from where it left off.

The full 13 disk installation may be downloaded from our ftp site if
you prefer at 
	ftp://mindwire.durand.com/MindWireServer 2.10/


BEFORE YOU INSTALL
________________________

In order to run this installation of MindWire NT 4.0 Server, you must 
already have installed the MindWire Client, located at
   ftp://mindwire.durand.com/./SlimConn/mw210.exe (approx. 150K)

or the full 4MB install at
   ftp://mindwire.durand.com/./Connector 2.10/mw210.exe

The 150K installation of the Client installs about 3MB of data from
our ftp site, so a constant connection to the internet while 
installing is required.

The connector is a 16 bit application requiring about 3MB of space,
and therefore should only be installed in a subdirectory of the 
old-style 8.3 format (DO NOT USE LONG FILENAMES).  This ensures that
users of 16 and 32 bit platforms can interact with the Server.


SQL Installation
________________

Should you desire MindWire databases to be stored with SQL, instead
of Microsoft access, the option is yours.

This release now supports MindWire Server for integration with SQL 
Server for NT 4.0, but does require special SQL setup instructions 
which must be followed before installing MindWire Server.  See "SQL 
Server Pre-Installation Setup" section below.  

Special Upgrading considerations
________________________________
Users who are upgrading MindWire Servers from Windows NT 3.51 should 
change their system startup configuration from "Automatic" to
"Manual" for the MindWire Server and Guardian Services, before 
upgrading the machine to Windows NT 4.0.  The MindWire Server 2.03 
release for NT 3.51 is not designed to run properly as a service on 
NT 4.0 and could even cause your system to crash!  After the machine
is upgraded from Windows NT 3.51 to Windows NT 4.0 Server, running the
new MindWire Server installation should set the Services back to 
Automatic. 

What's new in 2.10c?
____________________
-Adjustable connection timeout if user has not logged on.
File Library Auto Approve fix for Servers using SQL databases.
-New CAM techniques no longer requires an executable be launched when 
used with the new 2.10b Connector.  Great for customizing system sounds.
-WIP security error fixed when screen set to MindWire Security.


The evaluation copy of the MindWire server is a two user license with
no expiration date.  New users can install their servers for two 
connections at no charge, and upgrade when the server is able to handle
more users.



----------------------------------------------------------------------
     **** SQL Server Pre-Installation Setup for MindWire ****
----------------------------------------------------------------------

The following instructions must be followed in order to ensure 
successful SQL Server and MindWire Database integraion.  Microsoft 
Access users can ignore this section.

The SQL Server must be installed and configured to run as a local 
service account.  This is usually done during the installation of your 
SQL server.  To verify your SQL setup, go into Control Panel, 
Services, select the service "MSSQLServer", then click the 
"Startup..." button.  Make sure the service is set to "Log On As 
System Account" and "Allow service to interact with desktop".  

If you made any changes here, you wil need to restart the service for 
the settings to take effect.

Start SQL Enterprise Manager.  If you are running Enterprise Manager 
for the first time you will have to register SQL Server.

Step 1. Create two database devices for "MindWire_Server":
	- Right Mouse click on "Database Devices" will bring a menu.
	- Select "New Device".
	- Type the device name information in "New Database Device" 
	  window.

	We recommend two separate devices for data and log data:

	- Suggested name for MindWire_Server Data Device is 
	  "MindWireData" (20 MB recommended minimum)
	- Suggested name for MindWire_Server Log Device is 
	  "MindWireLog"  (5  MB recommended minimum) 

Step 2. We also recommend expanding two existing devices on your 
	system.
	- Suggested size for "MSDBData" is 20 MB (minimum recommended)
	- Suggested size for "MSDBLog" is 5  MB (minimum recommended)

Step 3. Next, create database with "MindWire_Server".
	- Right Mouse click on "Databases" folder will bring up a menu
	- Select "New Database..."
	- Type "MindWire_Server" for Name.
	    Choose "MindWireData" for Data Device
	    Choose "MindWireLog" for Log Device

	- Click on "Create Now" button

Step 4. Resize the existing "msdb" database if you made modifications
	to your system in Step 2 above.
	- Double click on the "msdb" database and select the 
	  "Expand..." button.  
	- Assuming the MSDBData and MSDBLog Devices are already
	  assinged, the size fields should be automatically sized 
	  to the correct value.  Select the "Expand Now" button. 

Step 5. Set "Truncate Log on Checkpoint" setting.
        - Double Click on the new "MindWire_Server" database.
	- Go to "Options" tab and make sure the box "Truncate log on 
	  checkpoint" is checked.
	
Step 6.	Verify that the "Truncate log on checkpoint" setting is 
	already set for the "msdb" database.


**********************************************************************
           **** RECOMMENDED SQL CONFIGURATION SETUP ****
**********************************************************************

For SQL database setups in general, it is recommended to send your 
data to a data device, and your log to a separate log device.  This 
ensures logging and data information won't affect or corrupt one 
another.

Use the above examples to setup your "tempdb" database, by creating  
separate data and log devices and assigning them to the "tempdb" 
database.  

To do this, create two devices called "TempData" and "TempLog" for 
example as in Step 1 above.  Double click on "tempdb" database (which 
already exists on your system), and select the "Expand..." button.  
Choose the appropriate Data and Log Devices that you previously 
created.  Save your changes by selecting the "Expand Now" button.

Make sure your tempdb devices are generously allocated to optimize 
efficiency of your SQL server.

We also recommend the option to "Truncate log on checkpoint" on the
tempdb database so that SQL commands succeed in the event that the 
log device gets filled.

**********************************************************************

You are now ready to install MindWire Server 2.10 with SQL Server!

