When you downloaded Argos 6 or received it on CD, you initially executed UnpackArgos.exe. This initial installation routine is - as its name suggests - simply unpacking the various installers that comprise Argos. UnpackArgos.exe "explodes" the various Argos installation packages into a single directory. This main directory is known as your deployment folder, and it's important for installing the rest of your Argos software.
By default, the deployment folder is called Argos60 and it located directly beneath the C: root. You may have specified a different name or location when you initially ran UnpackArgos.exe.
The deployment folder only contains installers - it does not contain actual print tracking data. For this reason, it is possible to move your Argos deployment folder at any time. If you choose to move your Argos deployment folder, be sure to move it as a whole. Do not move or copy any of the deployment folder subdirectories in isolation. Doing may result in incorrect subsequent server and/or desktop installations.
The deployment folder contains a number of subdirectories. Each subdirectory contains
a full InstallShield installation package for one Argos
component. At the root of your Argos deployment folder is
SetupArgos.exe, which is the Argos installation launcher. The launcher acts as a
"front end" for the various installers found in the deployment folder subdirectories.
Also found in the deployment root is this Quick Start Guide, and Setup.ini, described
below.
After installing the Argos database, a Setup.ini is created in the Argos deployment folder root. Setup.ini will not initially be found after running UnpackArgos.exe. Setup.ini contains information used by each of the subsequent Argos install packages to access the Argos database. For this reason - as described earlier - it is imperative that the deployment folder subdirectories maintain their relationship to the root folder.
After running UnpackArgos.exe, it is suggested that you use Windows sharing to make your deployment folder accessible via the network. Although it is not necessary to make the Argos60 folder a share point, doing so will significantly ease the process of installing Argos components to your desktop and server computers. At a minimum, the Argos60 deployment folder should be accessible from a higher-level share point.
When sharing the Argos deployment folder, ensure that all users who will potentially install any Argos components have at least read permissions.
Once you've established your Argos deployment folder, you're ready to get started installing Argos software.