Developer’s Guide

4-10 FileMaker Pro Developer’s Guide
4. Install Win32s.
Instruct your end users to insert the Win32s Disk1. In the Program
Manager, choose
Run from the File menu and type a:\setup.exe
from the Program Manager. Follow the Win32s setup instructions.
5. When the Win32s installation is complete, the FreeCell Setup dialog
box appears.
FileMaker, Inc. recommends To verify that the Win32s software has
been installed correctly, your end users should install the game
FreeCell, included with Win32s version 1.30c.
6. Restart the machine before installing the bundled solution.
7. Make sure the 4winsys folder is in the solution folder on the end
user’s hard disk after the solution has been installed.
When installing a runtime solution on a computer with Windows 3.1,
Windows NT 3.51, or Windows for Workgroups 3.11, be sure to
distribute the 4winsys folder. This folder contains DLLs that the runtime
application needs to display the application interface elements correctly.
Opening your runtime solution
The first time end users double-click the runtime application icon, the
runtime application will auto-register and, if appropriate, move items
into the operating system System folder. See “Installing items from the
Runtime Files folder” on page 4-3 for more details.
In Windows, the three-character filename extension associated with the
solution will not be registered by the operating system until the runtime
application has been opened. If a solution file is double-clicked before
the runtime application has registered the extension, the runtime
application won’t be found.
Your end users should start your solution by double-clicking the runtime
application icon, not the primary file icon. Double-clicking the icons for
the primary or auxiliary files might result in errors, depending on
whether there are other copies of the runtime application on the hard
disk. If your end users have more than one solution on their computers
with the same three-character extension and they double-click the icon
for the primary file, the most recently installed runtime application is
opened, which may not be the correct application for your solution’s
primary file.
Runtime application icon
Primary file icon