What are the features of the writing tools?
The Wtools feature contains several child features: one for the writing tools of each available language. (The selection of languages that you can implement depends on the license that you have purchased.) All writing tools include utilities for checking spelling and for hyphenating words; those marked with an asterisk ( * ) also include a utility for checking grammar.
Afrika installs the Afrikaans writing tools
Portugue installs the Brazilian Portuguese writing tools
Catalan installs the Catalan writing tools
Czech installs the Czech writing tools
Danish installs the Danish writing tools
Dutch installs the Dutch writing tools*
English installs the English writing tools*
Finnish installs the Finnish writing tools
French installs the French writing tools
Galician installs the Galician writing tools
German installs the German writing tools
Greek installs the Greek writing tools*
Iceland installs the Icelandic writing tools*
Italian installs the Italian writing tools
Norway installs the Norwegian writing tools
Polish installs the Polish writing tools
Russian installs the Russian writing tools*
Slovak installs the Slovak writing tools*
Sotho installs the Sotho writing tools*
Spanish installs the Spanish writing tools
Swedish installs the Swedish writing tools
Tswana installs the Tswana writing tools
Turkish installs the Turkish writing tools
Xhosa installs the Xhosa writing tools*
Zulu installs the Zulu writing tools*
Remember that specifying Wtools in a command line does not include its child features, so you must individually specify each desired feature. In addition, please note that you cannot set the writing tools to run from the network.
Appendix B: Frequently asked questions
This appendix answers some of the most frequently asked questions about the CorelDRAW Graphics Suite X5:
Can I deploy the software in a Windows 7 environment? Can I deploy the software by using the msiexec.exe file?
Can I deploy the software by using a Group Policy Object? Can I deploy the software with a single registration? Can I create multiple server images?
Can I customize the setup fileset on the server image?
Can I customize the installation settings on the server image? Can I create run-from-network installations?
Can I make the extra content on the DVD available to workstation users?
Can I make the Bitstream Font Navigator software available to workstations users?
Can I deploy the software in a Windows environment?
Yes! The CorelDRAW Graphics Suite X5 is compatible with the Windows 7 operating system.
To create a server image on a Windows 7 network that contains a mix of workgroups and domains, you must have appropriate permissions.
Can I deploy the software by using the msiexec.exe file?
Yes.CorelDRAWGraphicsSuiteX5supportsusingthemsiexec.exe file to deploy the software.
As explained in the section What is Setup.exe? On page 13, all deployment procedures in this guide require the use of the Setup.exe file for the software. However, the Setup.exe file does not support some deployment scenarios, such as the following:
Using the Setup.msi file, rather than a start up script, to install the software by using a Group Policy Object. (For general information on Group Policy Objects, see What access rights are required for installing the software? On page 12.) using the Setup.msi file to create packages for use with Novell ZENworks Desktop Management. (For general information on Novell ZENworks Desktop Management, see How do I deploy the software with Novell ZENworks Desktop Management? On page 44.) If you require support for deployment scenarios such as these, you must use the msiexec.exe file that is provided by the Windows operating system to interact directly with the MSI files that make up the setup for the CorelDRAW Graphics Suite X5.
How do I use the msiexec.exe file in deployment scenarios?
You can use the msiexec.exe file in the same way as the Setup.exe file: to create command lines that perform a setup-related functions. (For detailed information on installing withSetup.exe command lines, see Chapter 4.)
For CorelDRAW Graphics Suite X5, a command line that is based on the msiexec.exe file requires the following items:
A switch that indicates the action to be performed: creating a server image (/a), or installing the software (/I)
The location and name of the MSI file to which you want to apply the effects of the command line. In most deployment scenarios, you use the Setup.msi file (see What is Setup.msi? On page 14), which is located on the installation disc or on the image server.
Any public properties that are required to carry out the task. See What are the available public properties? On page 55.
Any switches that are required to carry out the task, as specified by the CHAINER_CMD=" " public property. For example, you can use CHAINER_CMD to specify what to display when executing the command line: no user interface whatsoever (/qn' or /quiet), a progress bar (/qb' or /passive), a progress bar and some additional information (/qr), or the full user interface (/qf' ). For a list of supported switches, see What are the available command-line switches? On page 54.
For example, the following command line uses the file
\ \ server \ CGS15\ Setup.msi on the server image to install all features of CorelDRAW Graphics Suite X5 while displaying the full user interface:
msiexec.exe /I "\\ server\CGS15\ Setup.msi" ADDLOCAL="ALL" CHAINER_CMD="/qf' "
As explained in How do I apply MST files? on page 32, you can use the TRANSFORMS public property to apply an MST file to the setup. By default, all MST files are applied to the Setup.msifile. If you want to apply an MST file to a different MSI file, you must use the following syntax (where is the filename of the MSI file, not including its extension; and where is the filename of the MST file, including its extension):
If the MST file is not in the same folder as the MSI file, must specify the full path and filename of the MST file.
Let's consider an example. In the following command line, the msiexec.exe file uses the file \\ server\ CGS15 \ Setup.msi on the server image to install all features of CorelDRAW Graphics Suite X5 without displaying any user interface whatsoever. In addition, the MST filemy_draw.mst is applied to the MSI file Draw.msi (in the same folder), and the MST filemy_pp.mst is applied to the MSI file PP.msi (in the same folder).
msiexec.exe /I " \\server\CGS15\ Setup.msi" ADDLOCAL="ALL" CHAINER_CMD="/qn" TRANSFORM_Draw="my_draw.mst" TRANSFORMS_PP="my_pp.mst"
Can I deploy the software by using a Group Policy Object?
Yes, if you have the following:
A network domain that is based on Active Directory® directory service
Domain controllers for Windows Server 2003 (or later) workstations that run Windows 7, Windows Vista, or Windows XP Professional.
Please note that you must use the msiexec.ex'e file (see page 63) if you want to apply a Group Policy Object to the Setup.ms'i file.
For basic information on the access rights that are required for installing the software, see page 12.
For help with using Group Policy Objects, please refer to your Group Policy Software Development Kit.
For specific help with using Group Policy Objects to deploy Corel software, contact Corel Support Services (www.corel.com/support). Please note that charges will apply.
Can I deploy the software with a single registration?
Yes. If you do not want the workstations to display a registration request, be sure to enter all the required registration information when you create the server image.
You can use a command line to suppress the user interface during the installation of the software on the workstations. This technique automatically applies the registration information that you provided for the server image. For more information on this technique, see How much of the setup interface do I want users to see? On page 29.
If your command line for deploying to the workstations uses the /q switch (seepage29),the end-user license agreement (EULA) appears the first time that a CorelDRAW Graphics Suite X5 is started on a workstation. To prevent the EULA from appearing again on that workstation, a user with administrator-level rights must unlock the software by accepting the terms of the EULA.
Can I create multiple server images?
Yes. For details, see How do I create multiple server images? On page 21.
Can I customize the setup fileset on the server image?
Yes. Create a copy of the server image, add or remove the desired MSI files, and then edit theSetup.xml file to reflect your changes. The procedure that follows explains these steps in more detail.
Please note that some MSI files cannot be removed from the setup fileset. For detailed information on all the MSI files used by the setup required or optional please see What is Setup.msi? On page 14.
What information is contained in the Setup.xml file?
The Setup.xml file (see What is Setup.xml? On page 15) contains three main types of nodes:
Each node specifies an MSI file. A node has the following structure, where GUIDis the associated GUID, MSI is the path and filename of the MSI file, and name is a descriptive name for the MSI file:
If you want to apply an MST file to the specified MSI file, you can use the following syntax (whereMST is the path and filename of the MST file):
For a list of the available MSI files, see What is Setup.msi? on page 14. Each node specifies a feature that is associated with an MSI file. A node has the following format, where name is the name of the MSI file and feature is the name of the associated feature: For a list of the available features, see What are the available features? on page 58.
Finally, each node specifies a public property. A node has the following structure, where property is the name of the public property and value is its value:
For a list of available public properties, see What are the available public properties? on page 55.
To create a server image with a customized fileset 1 Copy the server image to a new location.
2 Add any desired language-module MSI files to the server image. 3 Edit the Setup.xml file to reflect the additions you've made to the fileset.
Add a node for each new language-module MSI file. Add the following node for each new language module MSI file, where $$is the language:
4 Remove any unwanted MSI files from the server image. Some MSI files cannot be removed from the setup fileset. For more information, see What is Setup.msi? on page 14.
5 Edit the Setup.xml file to reflect the removals you've made from the fileset. Remove the corresponding node for each removed MSI file.
Remove the corresponding node and sub node for each removed MSI file. Adjust any corresponding nodes by changing their value.
For example, let's say that you re creating a single-language setup from a multi-language setup. To record the fileset changes in the Setup.xml file, you must remove the correspondingnode and node for each removed language module. Next, you must set each node for Include.$$ to a value of 0, where $$is a removed language module. Finally, you must set the node for ShowApplicationLanguageSelector to a value of 0. Similarly, to record that you've removed extra content from the fileset, you must remove the corresponding node and node, and you must set the nodes forInclude.Extras.Page and ShowExtraTabs to a value of 0.
Can I customize the installation settings on the server image? Yes. The Persist.xml file, stored at the root of the server image, can be used to modify the settings that are used to install the software on the workstations.
Each entry in the Persist.xml file corresponds to a public property for the software (see What are the available public properties? on page 55). The syntax of each entry is as follows:
By modifying the value of an existing entry in the Persist.xml file or by adding a new entry you can customize the installation settings that are deployed from that server image. This deployment method provides an excellent alternative to creating a different server image or customizing a command line.
For example, the following Persist.xml entry specifies that automatic software updates are enabled:
By changing the value of this entry from "1" to "0" (and saving this change to the Persist.xmlfile), you can disable automatic updates for the workstation installations.
Similarly, the following Persist.xml entry specifies the serial number for the installation:
By changing the "" value, you can specify a different serial number for the workstation installations.
Can I create run-from-network installations? Yes! The typical pull-installation scenario (see page 39) lets users decide whether to run CorelDRAW Graphics Suite X5 applications from the network. However, you can use one of the following methods to enforce which applications or application features run from the network:
Use the command-line public property ADDSOURCE. For information on this public property, see How do I specify how features are installed? on page 33. Use a Microsoft transformation (MST) file. For information on MST files, see What are MST files? on page16.
If you plan on supporting run-from-network installations, please note the following: The run-from-network scenario is not recommended for networks with slow connections.
Some software features, such as the writing tools, cannot be set to run from the network. See What are the available features? on page 58 for details. Run-from-network installations cannot be configured to detect and download product updates. To update such installations, you must deploy the update from a patched server image, as explained in
How do I apply patches? on page 48. In addition, please note that some features require access to
Microsoft Internet Explorer. To ensure the proper function of these features, you must verify the intranet-related security settings for Microsoft Internet Explorer on each workstation. Open Microsoft Internet Explorer, and click Tools > Internet Options. On the Security page, click the Local intranet icon, and then click Sites. In the Local intranet dialog box that appears, verify the configuration of the following check boxes: Automatically detect intranet network disabled (if present) Include all local (intranet) sites not listed in other zones enabled
Include all sites that bypass the proxy server enabled Include all network paths (UNCs)enabled
Can I make the extra content on the DVD available to workstation users?
Yes, by using one of the following methods: First, copy the Extras\ Content folder from the DVD to a shared location on the server. Next, specify the CLIPARTSOURCEDIR public property when using a command line to deploy the software to the workstations, as described in the section How do I specify where extra content is located on the server? on page 33.
First, copy the entire Extras folder from the DVD to a shared located on the server. Next, have workstations users install the extra content by running the Setup.exe file from the sharedExtras folder. Can I make the Bitstream Font Navigator software available to workstations users?
Yes. However, please note that to use Bitstream Font Navigator, workstation users require administrator-level privileges (Windows 7 or Windows Vista) or Power User permissions (Windows XP).