System requirements and notes

Tarma Installer 5 has the following system requirements:

Development environment: The Tarma Installer development environment requires Windows 2000, XP, 2003, Vista, 2008, or later, including x64 editions. A display size of 1024 x 768 or larger is strongly recommended.
Tarma Installer packages: Tarma Installer packages run on Windows 95, 98, Me, NT4, 2000, XP, 2003, Vista, 2008, and later, including x64 editions.

Platform support notes - Development environment

Please note the following when using the Tarma Workshop development environment on various Windows platforms.

Platform	Notes
Windows 95, 98, Me	Not supported. Use Tarma QuickInstall if you must run the development environment on these Windows versions.
Windows NT4	Not supported. Use Tarma QuickInstall if you must run the development environment on this Windows version.
Windows 2000	Operates as intended. We recommend using the latest Microsoft Service Pack and updates, which at the time of writing is SP4 plus security roll-up.
Windows XP	Operates as intended on both x86 and x64 versions. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2003	Operates as intended on both x86 and x64 versions; IA64 versions have not been tested. We recommend using the latest Microsoft Service Pack and updates.
Windows Vista	Operates as intended on both x86 and x64 versions. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2008 (Full installation)	Operates as intended on x86 and x64 versions of this Windows platform; IA64 versions have not been tested. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2008 (Core installation)	Can be installed on Core installations, but lacks some functionality. This configuration is therefore not currently recommended or supported.

Platform support notes - Installers

Please note the following when using the Tarma Setup.exe programs on various Windows platforms.

Platform	Notes
Windows 95	Operates as intended on this Windows platform, but with some loss of functionality on earlier versions due to missing features in the operating system. We recommend using OSR2 or later.
Windows 98	Operates as intended on both the original and the Second Edition of this Windows platform.
Windows Me	Operates as intended on this Windows platform.
Windows NT4	Operates as intended on SP3 or later; we recommend using SP6a (the final one available for this platform).
Windows 2000	Operates as intended. We recommend using the latest Microsoft Service Pack and updates, which at the time of writing is SP4 plus security roll-up.
Windows XP	Operates as intended on both x86 and x64 versions. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2003	Operates as intended on both x86 and x64 versions; IA64 versions have not been tested. We recommend using the latest Microsoft Service Pack and updates.
Windows Vista	Operates as intended on both x86 and x64 versions. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2008 (Full installation)	Operates as intended on x86 and x64 versions of this Windows platform; IA64 versions have not been tested. We recommend using the latest Microsoft Service Pack and updates.
Windows Server 2008 (Core installation)	Operates as intended on x86 and x64 versions of this Windows platform; IA64 versions have not been tested. We recommend using the latest Microsoft Service Pack and updates. However, please note the following limitations: Tarma installers can run in interactive mode on this platform and they will do so by default. To run them in non-interactive mode, use the /q command line option or add the /q option to the Default args field of the build configuration. Shortcuts and other functionality that requires the Windows shell (for example, file type associations) will be installed as intended, but are not functional because Core installations do not have a Windows Desktop, Start menu, or Windows Explorer installed. The Open and Save As dialog boxes of the Standard Dialog action appear in their old style because Core installations do not support the new style. The ShellExecute variation of the Set Window State action may not function as intended, because Core installations typically do not have the required handlers installed (for example, no Wordpad.exe to handle RichText). For the same reason, hyperlink StaticText controls may not function as intended.