# wc3270 Installer Documentation

## Windows Installer Options

The Windows installer for wc3270 uses Inno Setup. Complete documentation for the command-line options is here:

http://www.jrsoftware.org/ishelp/index.php?topic=setupcmdline

Options of interest are:

Option | Purpose
--- | ---
/SILENT | Run the installer without user interation
/COMPONENTS="component,component..." | Install only specific components
/TASKS="task,task..." | Perform only specific install tasks

By default, all components are installed. The components are:

Component | Definition
--- | ---
base | wc3270.exe (interactive emulator) wpr3287.exe (printer session emulator) catf.exe (helper program for displaying trace files) root_certs.txt (root CA certificate database)
wizard | wc3270wiz.exe (Session Wizard)
ws3270 | ws3270.exe (scripting emulator) x3270if.exe (command-line interface to ws3270 and wc3270 scrpting)
help | HTML documentation

By default, all tasks are performed. The tasks are:

Task | Definition
--- | ---
desktopicons | Create desktop shortcuts for wc3270 and the Session Wizard
migratefiles | Copy session files from the AppDefaults folders (from older versions of wc3270) to Documents folders

## Notes for Version Upgrades

### AppData File Migration

Release 3.5beta5 stopped the use of the wc3270 AppData folders. When upgrading from an earlier release to 3.5beta5 or later, session and keymap files in an wc3270 AppData folder must be copied to a Documents folder (a user's My Documents or the Public Documents folder) and desktop session shortcuts must be replaced. A Migration Wizard will be run automatically by the installer to handle this, allowing the user to control which files are copied. (Note that when using unattended installation, the Migration Wizard will copy all of the files.)

The Migration wizard will copy only files for the user running the installer and shared files. After the upgrade, other users will be offered an option in the Session Wizard to migrate their own files.

File migration will only happen once per user and for shared files. The files will be preserved in the AppData folders, but will be ignored.

### Upgrading from 32-bit to 64-bit

Release 3.5alpha4 was the first with 64-bit Windows support. When upgrading on 64-bit Windows from an earlier release to 3.5alpha4 or later, the old 32-bit version must be uninstalled before 64-bit installation can proceed. This will be done automatically by the 64-bit installer (with the user's permission; if installing unattended, it will always be performed).