			 SPSS 6.1 for Windows
			 June 23, 1994


*   Installing over a previous version of SPSS

    It is best to install SPSS in a new directory or to delete all
    files in the SPSS directory before installing (unless you have
    user files in that location).  If you install over an older
    version of SPSS for Windows, a few files that are not used in
    SPSS 6.1 will remain in the SPSS directory. 

    A complete installation of the system adds six new icons to the SPSS
    Program Manager group.  No attempt is made to remove older SPSS
    icons from that group as it is possible to have two versions
    installed on the same PC.  You should remove the old set of icons if they
    are no longer needed.  Version 6.1 has new icons except for SPSSTran, so
    it is easy to tell the two sets apart.

*   Swap file

    As a 32-bit Windows application, we recommend the use of a temporary
    Windows swap file.  If a permanent swap is used, it should be as large as
    the physical memory of the computer with a minimum of 8 megs.

*   Obsolete versions of win32s

    If you have an older version of another 32-bit Windows application, you may
    have an obsolete version of win32s installed.  The Microsoft win32s
    installation, which is run as part of installing SPSS, may not update
    this to the newer version.  SPSS requires at least version 1.15.111.  An
    older version can cause SPSS to fail.

    If the SPSS install does NOT install win32s, check the version number in
    win32s.ini, which is found in the  Windows SYSTEM directory.  The version
    number should be at least 1.115.111 or appear as blank (Version= ).  If it
    is older, you will need to reinstall win32s.

    To reinstall win32s, delete the contents of the win32s subdirectory under
    the Windows SYSTEM directory and the file win32s.ini from the SYSTEM
    directory itself.  Then insert SPSS Disk 6 and run win32su.

*   Low-memory considerations

    SPSS can become unstable under unusually low memory conditions.  This
    can be remedied on most systems by increasing the physical RAM on the
    machine or by enlarging the size of Windows' swap file if permanent.  If
    the amount of free memory in the first 640K is low, SPSS may sometimes
    have trouble starting in Windows, especially if other large applications
    are already loaded.  You can check low memory with the DOS mem command.

*   Low disk space problems

    If SPSS runs out of disk space while performing a save to an
    existing file, the original file will be deleted.  You should free some
    disk space and try again.

    If SPSS runs out of disk space while a procedure is inserting high
    resolution charts into the carousel, it will warn you that it is out of
    disk space and can only produce low resolution charts.  However, all
    previously produced high resolution charts will be lost. 
 
    If you are using disk compression software, and if the free
    storage on your PC is near the minimum required to accommodate SPSS at
    installation time, SPSS may not be able to detect an insufficient disk
    space condition until well into the installation process.  Free up
    some disk space and try again.

*   System resources drain

    If you run SPSS several times in the same Windows session, you may
    experience a slow drain on your available system resources.  This occurs
    only when you have printed a chart during the session.  Printing several
    charts will not make the problem more severe.  You can recover these
    resources by exiting from Windows and restarting it.

    Resource availability is displayed by the Program Manager menu Help / About
    Program Manager.  When resources are low, you may be unable to produce or
    edit charts or to display other graphical elements such as bitmaps.

*   Installation of VSHARE.386
 
    SPSS installs VSHARE.386 automatically. It supersedes DOS SHARE
    for Windows applications. We recommend that you remove DOS
    SHARE from your AUTOEXEC.BAT file unless required for other purposes.
     
    If you reinstall Windows, you may have to add the line
    DEVICE=VSHARE.386 under the section [386Enh] in your
    SYSTEM.INI file in the Windows directory.

*   Oracle and SQL Server

    Oracle and SQL Server are now supported through ODBC.  The appropriate ODBC
    drivers can be obtained from Oracle, Microsoft or other sources.

*   OLE chart considerations

    Certain applications including the current versions of Word for Windows
    and Excel do not always retain chart sizing information. You may have 
    to resize an SPSS chart in such an application when it is reopened.

*   Running SPSS for Windows under OS/2 2.1 or Windows NT

    SPSS 6.1 for Windows does not run under OS/2 2.1. OS/2 2.1 does not support
    32-bit Windows applications.

    SPSS for Windows does not currently run under Windows NT.

*   Nonstandard video drivers

    a)  The Chart Editor will automatically query your display driver for its 
    logical PPI (pels per inch) and resolution when a chart is created.
    If the PPI is inconsistent with the resolution, and the resolution is higher
    than VGA, the Editor will scale the fonts based on the driver-supplied
    resolution.  For instance, if the driver is running at 800x640, but the PPI
    matches the VGA value, the PPI value will be scaled up by 1.25 (800/640).

    Adding the line:

    NoAdjustSVGA=1

    to the [spsswin] section of your SPSSWIN.INI file will disable this
    feature.

    b)  Some graphics accelerator cards have problems with a graphics technique
	called "double buffering". This technique is used in the 3D
	scatterplots in SPSS. If major problems (e.g., system hanging) occur
	when using a graphics accelerator card,  adding the following line:

    NoDoubleBuffering=1

    to the [hoops] section of your SPSSWIN.INI file to disable this
    feature.

*   Suppressing errors on a secured system

    (This note refers to hardware key-protected and network systems only.)

    If a user suppresses the display of error messages in the output
    (via the Preferences/Output dialog box or via syntax), it is possible
    that statistical calculations will fail for no apparent reason under
    the following conditions:

       Hardware-secured systems:  This could occur if the hardware key is
       removed from the PC while SPSS is operating.

       Network-secured systems:  This could occur if the network license
       server terminates or the hardware-key is removed from the license
       server while SPSS is running.

    Suppressing errors is rarely useful.  We recommend not suppressing
    the error messages.

*   Drag-n-Drop

    SPSS/PC+ files and SPSS Portable files cannot be "dropped" onto the
    Print Manager.

*   Changes to EDATE format

    The Base System manual states that EDATE (European Date) format is in 
    DD/MM/YY format.  The format is actually DD.MM.YY.

*   Support for Hebrew Windows

    This product does not operate properly under Hebrew and Arabic versions
    of Microsoft Windows.  There are numerous problems when using characters
    from any right-to-left character set.  In addition, using the Arial font
    (and possibly others) results in problems with chart titles and axis
    labels.

*   Reading SPSS/PC+ data files

    Some statistical procedures in SPSS cannot read SPSS/PC+ data files.
    The workaround is to read these files into SPSS for Windows and save
    them as SPSS for Windows data files.

*   Using floppy disk drives

    It is possible to crash SPSS by prematurely removing the floppy
    disk containing your data while SPSS still has the file open.  In all
    cases, an alert box will be posted asking you to return the disk to
    the drive.

*   Installing a subset of the procedures

    The install program will allow you NOT to install some statistical
    procedures that you do not plan to use.  The corresponding menu items in
    the Statistics and/or Graphs menu will then be removed.  However, some
    menu items require for multiple statistical procedures.  Choosing not to
    install a procedure may cause some unexpected menu items not
    to appear in the system. 

       -   The "Pearson Correlations" menu requires both "Correlations" and
	   "Partial Correlations" to be installed.
 
       -   The "Multidimensional Scaling" menu requires "Alscal" and
	   "Proximities" to be installed.  This is in the Professional
	   Statistics option.

       -   The "Hierarchical Cluster" menu requires both "Cluster" and
	   "Proximities" to be installed.  This is in the Professional
	   Statistics option.

*    SPSSWIN.EXE appears to be in use after exit
     
     As a 32-bit application, certain program files could appear to be
     in use after SPSS is closed, although they are not in memory.
     This could prevent an administrator from updating these files.
     Closing Windows will release these files.

*   User Procedures

    The advanced user can write custom statistical procedures that will
    run in SPSS with the User Procedures facility.  The files and documentation
    for this facility are now part of the Developers Kit. They are not included
    with the SPSS for Windows materials.
       
-------------------------------- 06.01.00 -------------------------------------
