Installing Cascon on Windows 3.1

Cascon Version 4.1
(Program build 97)
October 19, 1996

Welcome to Cascon, the Computer-Aided System for Analysis of Conflicts. This edition of the Cascon software and database is included with the book Managing International Conflict: from Theory to Policy by Lincoln P. Bloomfield & Allen Moulton, published by St. Martin's Press (New York), ISBN: 0-312-13675-7.

Cascon provides computer support for using the conflict model and analytic methodology explained in the book. To make effective use of Cascon it is essential to understand the conceptual material presented in the book, especially Chapters 7-10, which cover the dynamic phase model of conflict and the Cascon methodology.

The material in this document covers issues related to using Cascon on the older Windows 3.1 or Windows for Workgroups operating systems via the Microsoft Win32s extensions. If you have any of the newer Windows 95, 98, or NT 4.0 operating systems, please refer to the installation notes for those systems.

Topics Covered

General Topics

Installing Cascon
System requirements for Cascon
Files installed in your Cascon folder/directory
Using Cascon with Windows 3.1 or Windows for Workgroups (Win32s)
Requirements for Win32s
What installing Win32s does
Troubleshooting Win32s
Obtaining the latest complete version of Win32s from Microsoft
How to remove Win32s from your computer

INSTALLING CASCON

On Windows 3.1 and Windows for Workgroups:

In Program Manager, click on File in the top menu
Select Run from the pull down menu
Place the Cascon Disk 1 in your floppy drive (e.g., drive A)
In the box that appears, type the following (substituting your floppy drive letter for "A"):

       A:SETUP

Press enter or click OK
Follow directions on the Cascon installation screens that follow
Answer Yes if asked whether to install Win32s (see below for details)

System Requirements for CASCON

Operating System:: Windows 3.1 or Windows for Workgroups; (or Microsoft Windows 95, Windows 98, Windows NT)
Processor:: minimum 386, 486 or Pentium recommended
Memory:: minimum 8 MB, 16 MB recommended
Hard disk space:

A 15" or larger monitor and SVGA 800 x 600 or higher resolution is especially helpful if you want to keep most of Cascon's windows visible at the same time.

Files installed in your CASCON folder / directory

The Cascon SETUP program will install the following files in the Cascon folder / directory:

  CASCON.CDB     Cascon historical conflict database
  CASCON.EXE     Cascon software
  CASCON.HLP     Cascon help file
  CASCON.HTM     Internet page with Cascon links (this file)
  CASCON.INI     Cascon initialization file
  PRO1.CAS       Profile case #1
  PRO2.CAS       Profile case #2
  PRO3.CAS       Profile case #3
  README.TXT     Installation and release notes 
  SAMPLE.CAS     Sample user case for an example in Chapter 10
  USERFORM.CAS   Model form for entering a case offline

Using CASCON with Windows 3.1 or Windows for Workgroups

Cascon is a 32-bit Windows application, designed for the latest Windows 95/98 and Windows NT technology. For Windows 3.1 and Windows for Workgroups users, Microsoft provides an extension to Windows, called Win32s, which supports 32-bit software like Cascon. You may already have Win32s installed by another software package.

The Cascon SETUP program checks to see if you have an adequate level of Win32s. If not, the Cascon SETUP program will offer to install a limited subset of Win32s necessary for Cascon. To obtain and install a complete copy of the latest version of Win32s from Microsoft use one of the procedures described below. Also described below, in case you need them, are the steps needed to remove Win32s from your computer.

Requirement for Win32s

Win32s requires Windows 3.1 or later in 386-enhanced mode with virtual memory enabled. You must have a 386 or better computer with at least 8 MB of RAM memory and preferably 16 MB.

Win32s also requires either SHARE or VSHARE. For Windows 3.1, you must run the MS-DOS program SHARE.EXE before starting Windows. This is often done in AUTOEXEC.BAT. Be sure that the L and F parameters are at least as large as the following:

      SHARE /L:500 /F:5100

For Windows for Workgroups (or the Windows 3.11 upgrade) you do not need to run the MS-DOS SHARE program. Just be sure that the [386Enh] section of your Windows SYSTEM.INI file contains a line reading:

      device=vshare.386

Cascon SETUP will check for SHARE or VSHARE before proceeding with installation of Win32s. If you get a message saying that SHARE is not loaded, exit Windows and execute the SHARE command as above. Then restart Windows and proceed with Cascon installation again.

What installing Win32s does

Win32s is an extension of the Windows 3.1 or Windows for Workgroups operating system. The SETUP program will install files into your Windows System directory, modify your SYSTEM.INI file, and then restart Windows to complete the installation of Cascon.

The SYSTEM.INI file is modified by adding the following line to the [386Enh] section:

      device=WINDOWS\SYSTEM\win32s\w32s.386

A VMCPD line is added to the [386Enh] section (or corrected) to read:

      device=*vmcpd

Also "winmm16.dll" is added to the following line in the [Boot] section:

      drivers=mmsystem.dll winmm16.dll

The following files are installed in the Windows System directory:

      CTL3D32.DLL
      OLECLI.DLL
      W32SYS.DLL
      WIN32S16.DLL
      WIN32S.INI
      WINDOWS.HLP
      WINHLP32.CNT
      WINHLP32.EXE
      WINHLP32.HLP
      WINMM16.DLL

Additional files are placed in a new WIN32S subdirectory in the Windows System directory.

Troubleshooting Win32s

Cascon has been tested extensively on Windows 3.1 computers using Win32s. Win32s problems are usually traceable to the either of two causes: resource limitations and conflict with files installed into the Windows System directory by other applications. The Windows 3.1 generation of operating system has a variety of resource limitations. To correct such a problem follow the usual procedures published in many "Tips" books and other publications. Alternatively, you can upgrade to Windows 95/98 that was designed to remove many of those limitations.

File conflicts can result from other installations of different versions of Win32s or CTL3D32.DLL in your Windows System directory. Files from different versions are incompatible. The best approach is to remove Win32s following the directions below and reinstall. You may also wish to download the complete and most up to date version of Win32s from Microsoft. Upgrade instructions and an Internet link for downloading are provided below.

For more information about Win32s, the best source of information is Microsoft itself at http://support.microsoft.com on the Internet. Microsoft maintains a Knowledge Base with answers to questions about their products, including the Win32s FAQ.

If you have trouble reaching the Microsoft site, look at our saved copy of the Microsoft Win32s FAQ.

The following articles from the Microsoft Knowledge Base may be helpful:

Article ID	Title
Q106715	How to Troubleshoot Win32s Installation Problems
Q117153	Display Problems with Win32s and the S3 Driver

You can also check the Cascon Project home page at http://web.mit.edu/cascon for updates and links to additional information.

Obtaining the latest complete version of Win32s from Microsoft

Note: if you have Windows 95, 98 or Windows NT, see the instructions for those operating systems. Do not download or install this file. It is only for the older Windows 3.1 and Windows for Workgroups.

You can obtain a complete copy of the latest version of Win32s (version 1.30c) from Microsoft by downloading the PW1118.EXE self-extracting file from the Microsoft site.

Click here for instructions for downloading from the Microsoft site.
Click here for other ways to obtain files from Microsoft.
Click here to download a copy of PW1118.EXE from our site.

PW1118.EXE requires about 2.5 MB of disk space to download. You will also need about another 6 MB temporarily during installation for the files that are extracted out of PW1118.EXE. When installed, the full version of Win32s requires about 5 MB on your Windows System disk.

Installing Win32s from `PW1118.EXE`

After you have downloaded the PW1118.EXE file, the files that are contained within it must be decompressed to proceed with installing Win32s. To decompress the files from the self-extracting PW1118.EXE file, do the following:

Create a temporary directory on your hard disk for the decompressed files. For example, you could create a directory named INST32S using the Create Directory function under File in the main menu of File Manager.
Copy PW1118.EXE to the new Install directory (or download it to the temporary directory n the first place). Change directory to your temporary INST32S directory in File Manager, and double click on PW1118.EXE . This runs PW1118 in an MS-DOS box to decompress the Win32s files into an installation layout (setup program) in the INST32S directory.
Double-click Setup.exe. The setup program installs Win32s and restarts Windows to update the system files. Win32s is now installed or upgraded on your system, and any obsolete Win32s files have been removed.
Delete the INST32S directory and its contents.

How to remove Win32s from your computer

Follow these five steps to remove Win32s. The symbols <WINDOWS> and <SYSTEM> refer where the Windows and System directories are located, respectively. In a networked installation, the System directory may be located on a remote shared disk.

Remove the following line from the [386Enh] section in the SYSTEM.INI file:

      device=<WINDOWS>\<SYSTEM>\win32s\w32s.386

Modify the following line from the [BOOT] section in the SYSTEM.INI file:

      drivers=mmsystem.dll winmm16.dll

to the following (remove winmm16.dll):

      drivers=mmsystem.dll

Delete the following files from the <WINDOWS>\<SYSTEM> subdirectory or from the <SYSTEM> directory in network installations:

      OLECLI.DLL
      W32SYS.DLL
      WIN32S16.DLL
      WIN32S.INI
      WINDOWS.HLP
      WINHLP32.CNT
      WINHLP32.EXE
      WINHLP32.HLP
      WINMM16.DLL

If you have installed the complete Win32s, also delete any of the following files found in the same directory:

      COMPOBJ.DLL
      OLE2.DLL
      OLE2.REG
      OLE2CONV.DLL
      OLE2DISP.DLL
      OLE2NLS.DLL
      OLE2PROX.DLL
      STDOLE.TLB
      STORAGE.DLL
      TYPELIB.DLL

Note: It may not be possible to delete W32SYS.DLL while Windows is running. This occurs if you have run some Win32 application. It is recommended that you exit windows and remove Win32s while in MS-DOS, not from a Windows MS-DOS box.

Delete all the files in the <WINDOWS>\<SYSTEM>\WIN32S subdirectory (or the <SYSTEM>\WIN32S subdirectory in network installations). Then delete subdirectory itself. See note below for caveats.
Restart Windows.

NOTE: <WINDOWS> refers to the windows installation directory. On a networked Windows installation, the <SYSTEM> directory may be located on a remote shared disk. If you are only removing Win32s from your machine in a networked installation, then you do not need to remove the shared files in <SYSTEM> and <SYSTEM>\WIN32S). Before removing these files from the network shared disk, make sure that all users that use Win32s have removed the references to Win32s from the SYSTEM.INI file as described above.

Microsoft, MS, MS-DOS, Win32, Win32s, and Windows are registered trademarks and Windows NT, Windows 95 and Windows 98 are trademarks of Microsoft Corporation in the U.S.A. and other countries.