The Deployment Configuration Program then opens its Configuration Window on your desktop, as shown in Figure 2–1.
The Configuration Window contains:
a Help button, which opens a separate window of information about the entry options available on the currently displayed panel.
three menus: File, Tools and Help.
The Tools Menu offers a Create Package feature that lets you create a new installation package for an existing .ini configuration file that has been opened into this Configuration Window. You may use File->Open... to locate and open an existing .ini file.
Complete the information in the nine tabbed panels, as described separately (per tab) below. Click on each tab to display the associated panel.
If you begin creating an installation package but then decide to finish it at a later time, you may File->Save a partially completed package, and then File->Open... it later to resume and complete your work.
When you have entered all of the information requested in all nine tabbed panels, select File->Save to save your configuration choices in an .ini file and create a new installation package. Your Save command activates a standard, familiar Windows Save dialog box.
In the dialog box: Enter an appropriate path and filename for the .ini file and .exe file, and click the Save button.
The Save command actually creates two new files: the .ini file, which is saved to whatever folder you designate in the Save dialog box, and an .exe file (the bundled installation package, including a copy of the .ini file), which is saved by default to C:\Program Files\Sun\Deployment Configuration Program\Packages. Both the .ini and .exe files carry whatever filename you designate in the Save dialog box.
If the program reports a Logon failure or “Could not locate...” a necessary resource while it is running. If you know that the resource exists in the location you have specified, then the administrator account you are using to run this Deployment Configuration Program is not authenticated to the file server where the resource resides. Make sure that you are logged in to the locations of all such resources and then run the Deployment Configuration Program again.