gecko-dev/cck/CCKDocs/cd_man_cck.htm

1900 строки
67 KiB
HTML

<html>
<!--This html file is XHTML complaint, as set forth in the
w3c recommendations except for the following:
Lists work as they do in older versions on HTML and not as
directed in XHTML.
The <a name=" "> tags have targets that use spaces. -->
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
<title> Guide to Customizing and Distributing Mozilla 1.4.1: Chapter&#32;11Manually Customizing the CD Autorun Screen</title>
<!--The following is a javascript which determines whether the client
is on a Windows machine, or is on another type of operating system. Once
the operating system is determined, either a windows or other operating
system cascading style sheet is used. -->
<script type="text/JavaScript">
<!-- Start hiding
window.onerror=null;
var client=navigator.userAgent.toLowerCase();
var WinStyle = "<STYLE NAME=WINDOWS>\n" +
"body,p {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; } \n" +
"th,tr,td,br,li,dl,dd,ul,ol,li {font-family: helvetica,arial,sans-serif; font-size:10pt; } \n" +
".bartext {font-family: helvetica,arial,sans-serif; font-weight: bold; color: #666666; margin-bottom: 0; margin-top: 0; font-size:14pt;} \n" +
".callout {font-family: helvetica,arial,sans-serif; font-size: 8pt;} \n" +
".calloutlarge {font-family: helvetica,arial,sans-serif; font-size: 9pt;} \n" +
".calloutlargebold {font-family: helvetica,arial,sans-serif; font-size: 9pt; font-weight: bold;} \n" +
".calloutsmall {font-family: helvetica,arial,sans-serif; font-size: 7pt; font-weight: normal;} \n" +
".caption {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 5; margin-top: 0; font-size: 11pt;} \n" +
".caution {font-family: helvetica,arial,sans-serif; font-size:10pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
"code {font-family: courier,couriernew,monospaced; font-size: 10pt; margin-bottom: 0; margin-bottom:0; margin-top: 0;} \n" +
".copy {align: center; font-family: helvetica,arial,sans-serif; font-size:8pt; margin-bottom: 0; margin-top: 0;} \n" +
".footnote {font-family: helvetica,arial,sans-serif; font-size:10pt; } \n" +
".gloss {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; } \n" +
".grouptitleix {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 10; margin-top: 20pt; font-size: 14pt;} \n" +
".h1 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 0; margin-top: 30pt; font-size: 18pt;} \n" +
".h2 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 10; margin-top: 30pt; font-size: 16pt;} \n" +
".h3 {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 10; margin-top: 20pt; font-size: 14pt;} \n" +
".h4 {font-family: helvetica,arial,sans-serif; font-style: italic; font-color: black;margin-bottom: 0; margin-top: 16pt; font-size: 11pt;} \n" +
".h5 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 0; margin-top: 0; font-size: 8pt;} \n" +
".navigation {font-family: helvetica,arial,sans-serif; font-weight: bold; color: #993300; margin-bottom: 0; margin-top: 0; font-size:10pt;} \n" +
".note {font-family: helvetica,arial,sans-serif; font-size:10pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
".list1 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; margin-left: 12pt; list-style-position: outside; } \n" +
".list2 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; text-indent: 12pt; margin-left: 18pt; } \n" +
".list3 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; text-indent: 18pt; margin-left: 24pt; } \n" +
".para1 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; margin-left: 12pt; } \n" +
".para2 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; margin-left: 18pt; } \n" +
".para3 {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; margin-left: 24pt; } \n" +
"pre {font-family: courier,couriernew,monospaced; font-size: 10pt; margin-bottom: 0; } \n" +
".refh1 {font-family: palatino,times,timesnewroman,serif; font-weight: normal; color: black;margin-bottom: 10; margin-top: 30pt; font-size: 18pt;} \n" +
".refh2 {font-family: palatino,times,timesnewroman,serif; font-weight: normal; color: black; margin-bottom: 10; margin-top: 30pt; font-size: 16pt;} \n" +
".refhead {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 4; margin-top: 15pt; font-size: 11pt;} \n" +
".tabletext {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; } \n" +
".tablehead {text-align: left;font-family: helvetica,arial,sans-serif; font-weight: bold; font-size:10pt; margin-bottom: 4; margin-top: 0; } \n" +
".text {font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 10; margin-top: 0; } \n" +
".tip {font-family: helvetica,arial,sans-serif; font-size:10pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
".title {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black;margin-bottom: 30pt; margin-top: 16pt; font-size: 16pt;} \n" +
".toc1 {font-family: helvetica,arial,sans-serif; font-size: 11pt; font-weight: bold; margin-bottom: 0; margin-top: 30; text-indent: 20;} \n" +
".tocc {font-family: helvetica,arial,sans-serif; font-size: 11pt; font-weight: bold; margin-bottom: 0; margin-top: 7; text-indent: 20;} \n" +
".tochead1 {font-family: helvetica,arial,sans-serif; font-size: 10pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 20;} \n" +
".tochead2 {font-family: helvetica,arial,sans-serif; font-size: 10pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 40;} \n" +
".tochead3 {font-family: helvetica,arial,sans-serif; font-size: 10pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 60;} \n" +
".tocnontoc {font-family: helvetica,arial,sans-serif; font-size: 10pt; font-weight: normal; text-indent: 0;} \n" +
".tocpart {font-family: helvetica,arial,sans-serif; font-size:13pt; font-weight: bold; margin-bottom: 0; margin-top: 20;} \n" +
".update {text-align: right; font-family: helvetica,arial,sans-serif; font-size:8pt; margin-bottom: 0; margin-top: 0;} \n" +
"</style>";
var OtherStyle = "<style name=NOTWINDOWS>\n" +
"body,p {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; } \n" +
"th,tr,td,br,li,dl,dd,ul,ol,li {font-family: helvetica,arial,sans-serif; font-size:12pt; } \n" +
".bartext {font-family: helvetica,arial,sans-serif; font-weight: bold; color: #666666; margin-bottom: 0; margin-top: 0; font-size:17pt;} \n" +
".callout {font-family: helvetica,arial,sans-serif; font-size: 10pt;} \n" +
".calloutlarge {font-family: helvetica,arial,sans-serif; font-size: 11pt;} \n" +
".calloutlargebold {font-family: helvetica,arial,sans-serif; font-size: 11pt; font-weight: bold;} \n" +
".calloutsmall {font-family: helvetica,arial,sans-serif; font-size: 8pt; font-weight: normal;} \n" +
".caption {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 5; margin-top: 0; font-size: 13pt;} \n" +
".caution {font-family: helvetica,arial,sans-serif; font-size:12pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
"code {font-family: courier,couriernew,monospaced; font-size: 12pt; margin-bottom: 0; margin-bottom:0; margin-top: 0;} \n" +
".copy {align: center; font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 0; margin-top: 0;} \n" +
".footnote {font-family: helvetica,arial,sans-serif; font-size:12pt; } \n" +
".gloss {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; } \n" +
".grouptitleix {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 10; margin-top: 20pt; font-size: 17pt;} \n" +
".h1 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 0; margin-top: 30pt; font-size: 22pt;} \n" +
".h2 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 10; margin-top: 30pt; font-size: 19pt;} \n" +
".h3 {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 10; margin-top: 20pt; font-size: 17pt;} \n" +
".h4 {font-family: helvetica,arial,sans-serif; font-style: italic; font-color: black;margin-bottom: 0; margin-top: 16pt; font-size: 14pt;} \n" +
".h5 {font-family: helvetica,arial,sans-serif; font-weight: normal; color: black; margin-bottom: 0; margin-top: 0; font-size: 10pt;} \n" +
".navigation {font-family: helvetica,arial,sans-serif; font-weight: bold; color: #993300; margin-bottom: 0; margin-top: 0; font-size:12pt;} \n" +
".note {font-family: helvetica,arial,sans-serif; font-size:12pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
".list1 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; margin-left: 12pt; list-style-position: outside; } \n" +
".list2 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; text-indent: 12pt; margin-left: 18pt; } \n" +
".list3 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; text-indent: 18pt; margin-left: 24pt; } \n" +
".para1 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; margin-left: 12pt; } \n" +
".para2 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; margin-left: 18pt; } \n" +
".para3 {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; margin-left: 24pt; } \n" +
"pre {font-family: courier,couriernew,monospaced; font-size: 12pt; margin-bottom: 0; } \n" +
".refh1 {font-family: palatino,times,timesnewroman,serif; font-weight: normal; color: black;margin-bottom: 10; margin-top: 30pt; font-size: 22pt;} \n" +
".refh2 {font-family: palatino,times,timesnewroman,serif; font-weight: normal; color: black; margin-bottom: 10; margin-top: 30pt; font-size: 19pt;} \n" +
".refhead {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black; margin-bottom: 4; margin-top: 15pt; font-size: 13pt;} \n" +
".tabletext {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; } \n" +
".tablehead {text-align: left;font-family: helvetica,arial,sans-serif; font-weight: bold; font-size:12pt; margin-bottom: 4; margin-top: 0; } \n" +
".text {font-family: helvetica,arial,sans-serif; font-size:12pt; margin-bottom: 10; margin-top: 0; } \n" +
".tip {font-family: helvetica,arial,sans-serif; font-size:12pt; font-weight: bold; margin-bottom: 0; margin-top: 0; } \n" +
".title {font-family: helvetica,arial,sans-serif; font-weight: bold; color: black;margin-bottom: 30pt; margin-top: 16pt; font-size: 19pt;} \n" +
".toc1 {font-family: helvetica,arial,sans-serif; font-size: 13pt; font-weight: bold; margin-bottom: 0; margin-top: 30; text-indent: 20;} \n" +
".tocc {font-family: helvetica,arial,sans-serif; font-size: 13pt; font-weight: bold; margin-bottom: 0; margin-top: 7; text-indent: 20;} \n" +
".tochead1 {font-family: helvetica,arial,sans-serif; font-size: 12pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 20;} \n" +
".tochead2 {font-family: helvetica,arial,sans-serif; font-size: 12pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 40;} \n" +
".tochead3 {font-family: helvetica,arial,sans-serif; font-size: 12pt; font-weight: normal; margin-bottom: 0; margin-top: 2; text-indent: 60;} \n" +
".tocnontoc {font-family: helvetica,arial,sans-serif; font-size: 12pt; font-weight: normal; text-indent: 0;} \n" +
".tocpart {font-family: helvetica,arial,sans-serif; font-size:15pt; font-weight: bold; margin-bottom: 0; margin-top: 20;} \n" +
".update {text-align: right; font-family: helvetica,arial,sans-serif; font-size:10pt; margin-bottom: 0; margin-top: 0;} \n" +
"</style>";
if ( client.indexOf("win") != -1 ){
document.write( WinStyle );
}else{
document.write( OtherStyle );
}
// End hiding -->
</script>
</head>
<body text="#000000" link="#666699" vlink="#666699" alink="#333366" bgcolor="#FFFFFF">
<!--maincontent defines everything between the body tags -->
<!--start maincontent-->
<!--navigationcontent defines the top row of links and the banner -->
<!--start navigationcontent-->
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td><table border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="bottom" width="67">
<img src="netscape48.gif" height="48" width="48" border="0" alt="Netscape logo" />
</td>
<td valign="middle">
<span class="bartext"> <br />Guide to Customizing and Distributing Mozilla
1.4.1
</span>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td>
<hr size="4" noshade="noshade" />
<span class="navigation">
<a style="text-decoration: none" href="verify_tool_cck.htm">
Previous
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
<span class="navigation">
<a style="text-decoration: none" href="guide.html">
Contents
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
<span class="navigation">
<a style="text-decoration: none" href="advanced_cck.htm">
Next
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
</td>
</tr>
</table>
<!--end navigationcontent-->
<!--bookcontent defines the actual content of the file, sans headers and footers -->
<!--start bookcontent-->
<blockquote>
<br />
<p class="title">
<a name="13832"> </a>
<a name=""> </a>
<font color="#666666">
Chapter&#32;11
&nbsp;
</font>
<a name="13833"> </a>
<a name="Manually Customizing the CD Autorun Screen"> </a>
Manually Customizing the CD Autorun Screen
</p><p class="text">
<a name="15015"> </a>
The CD autorun screen automatically appears when a user inserts a customized Mozilla CD into a CD-ROM drive. The standard CD autorun screen lets your users easily install Mozilla or read installation instructions before they begin installation. You can customize some aspects of this screen, such as the title bar text and background, using the CCK tool.
</p>
<p class="text">
<a name="15016"> </a>
If you're planning to distribute a Mozilla installer on a CD, you might want to make more customizations to the standard CD autorun screen than the CCK tool can implement. This chapter describes the manual customizations to the CD autorun screen that you can make, if you wish, to the installation files generated by the CCK tool.
</p>
<p class="text">
<a name="15019"> </a>
This chapter contains these sections:
</p>
<p class="text">
<a name="16143"> </a>
<a href="cd_man_cck.htm#16167" >Why Manually Customize the Standard CD Autorun Screen?</a><br /><a href="cd_man_cck.htm#14914" >Run The CCK Tool First</a><br /><a href="cd_man_cck.htm#14934" >About the CD Autorun Files</a><br /><a href="cd_man_cck.htm#14371" >Tools for Customizing the Standard Autorun Screen</a><br /><a href="cd_man_cck.htm#15297" >Creating a CD Staging Area on Your Hard Disk</a><br /><a href="cd_man_cck.htm#14393" >Understanding the rshell.ini File</a><br /><a href="cd_man_cck.htm#14684" >Editing the rshell.ini File</a><br /><a href="cd_man_cck.htm#14971" >Verifying Your CD Autorun Screen Manual Customizations</a>
</p>
<p class="h1">
<a name="16167"> </a>
<a name="Why Manually Customize the Standard CD Autorun Screen?"> </a>
Why Manually Customize the Standard CD Autorun Screen?
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="15073"> </a>
<a href="cd_cck.htm#13833" >Chapter&#32;8 "Preparing to Customize the CD Autorun Screen</a>" describes the following customizations that you can make to the standard CD autorun screen using the CCK tool:
</p>
<ul>
<li>
Customize the CD autorun screen's background bitmap image.
<a name="15074"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
Provide your own title bar text and text below the title bar.
<a name="15075"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
Customize the contents of the installation guide text file.
<a name="15076"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ul>
<p class="text">
<a name="14314"> </a>
You can manually customize the standard CD autorun screen if you want to:
</p>
<ul>
<li>
Create additional screens that inform users about your products, services, and promotions.
<a name="14315"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
Include additional files or software on the CD. You can add new screens and buttons to the CD autorun screen that give users easy access to the directories on the CD that contain these files, so that users don't have to browse through the directories on the CD to find them. You can also include a button in the CD autorun screen that opens a <code>readme.txt </code>file, so users have easy access to information about these additional files. (For information about adding up to two additional installers with the CCK tool, see <a href="installer_cck.htm#13833" >Chapter&#32;9 "Preparing to Create the Installer</a>."
<a name="14317"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
Installers for additional applications on the CD. You can add buttons and text to the standard CD autorun screen that inform users about these applications and make them convenient to install.
<a name="14319"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ul>
<p class="h1">
<a name="14914"> </a>
<a name="Run The CCK Tool First"> </a>
Run The CCK Tool First
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14916"> </a>
Before manually customizing the standard CD autorun screen, use the CCK tool to create a Mozilla installer that includes the CD autorun screen. Make sure you select the checkbox labeled "Include CD autorun screen" on the Gathering Information screen. Checking this box causes CCK to include the files associated with the CD autorun screen when it creates your customized Mozilla installer. After the CCK tool builds the installer, verify that the CD autorun customizations are correct.
</p>
<p class="h1">
<a name="14934"> </a>
<a name="About the CD Autorun Files"> </a>
About the CD Autorun Files
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14340"> </a>
The CD autorun screen is a standard Windows executable program that automatically launches when users insert the CD in a CD-ROM drive.
</p>
<p class="text">
<a name="14344"> </a>
When you create your customized Mozilla installer, the CCK tool places the CD Autorun files in this location:
</p>
<p>
<code>
<a name="14346"></a>
<em>installation_directory</em>\CCKTool\Configs\<em>my_config</em>\Output
</code>
</p><p class="text">
<a name="14348"> </a>
When you are finished editing the CD autorun screen files, you use the contents of the <code>Output</code> directory to create your CD layout.
</p>
<p class="text">
<a name="14350"> </a>
These files and directories are associated with the CD autorun screen:
</p>
<ul>
<li>
The <code>Nsetup32.exe</code> program (the Autorun program) and the <code>rshell.ini</code> file are both located in the directory <code>Output\Shell\Nsetup32\</code>. The <code>rshell.ini</code> file contains all of the custom settings and flags that control the appearance and function of the CD autorun screen.
<a name="14351"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
<code>setup.exe</code>, <code>launch.ini</code>, and <code>autorun.inf</code> are located in the <code>Output</code> directory, which is the root of the CD layout. They control the automatic launch of the Autorun program and the CD autorun screen. The <code>launch.ini</code> file points to the location of the <code>Nsetup32.exe</code> autorun program and its associated file, <code>rshell.ini</code>. If the Autorun screen doesn't automatically launch, users can double-click the setup.exe file.
<a name="15244"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ul>
<p class="text">
<a name="14362"> </a>
In addition to controlling the appearance of the CD autorun screen, the <code>rshell.ini</code> file also links any number of CD autorun screens together using buttons. The buttons can also point to any installers or files included on your CD that you want users to be able to access.
</p>
<p class="text">
<a name="14370"> </a>
For more information about preparing your CD layout, see <a href="distribute_cck.htm#13833" >Chapter&#32;14 "Distributing Your Installers</a>."
</p>
<p class="h1">
<a name="14371"> </a>
<a name="Tools for Customizing the Standard Autorun Screen"> </a>
Tools for Customizing the Standard Autorun Screen
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14373"> </a>
To customize the standard autorun screen or add new screens, you'll need:
</p>
<ul>
<li>
Aa standard text editor for editing the <code>rshell.ini</code> file.
<a name="15284"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
A graphics editing program, for creating any custom bitmap images that you want to include as background or button images in the Autorun screens.
<a name="14376"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ul>
<p class="text">
<a name="14377"> </a>
You can include one or more directories inside the shell directory to store the custom bitmap images used by the autorun screens. Depending on the CD layout you want to create, you can also include directories for additional items such as applications that you want users to be able to install by clicking buttons in the CD autorun screen.
</p>
<p class="h1">
<a name="15297"> </a>
<a name="Creating a CD Staging Area on Your Hard Disk"> </a>
Creating a CD Staging Area on Your Hard Disk
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="15298"> </a>
Before you start editing the <code>rshell.ini</code> file, you'll need to determine the directory structure on the CD so that you know how to specify the pathnames of files that you want to be accessible through the Autorun screens. You do this by creating a staging area on your hard disk that exactly represents the final CD layout you intend to use.
</p>
<p class="text">
<a name="14383"> </a>
To create a CD staging area:
</p>
<ol type="1">
<li value="1">
Create a directory called Staging on your hard disk.
<a name="14384"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="2">
Locate the <code>Output</code> directory you created using the CCK tool.
<a name="14386"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Copy the contents of the Output directory into the Staging directory.
<a name="14388"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="4">
Inside the <code>Staging</code> directory, create a directory for each additional component that you want to include on the CD.
<a name="14390"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="text">
<a name="14392"> </a>
Inside the <code>Staging\Shell</code> directory, you'll find a directory called <code>bmps</code> in which you'll store the custom background bitmap images for any new CD autorun screens you create.
</p>
<p class="h1">
<a name="14393"> </a>
<a name="Understanding the rshell.ini File"> </a>
Understanding the rshell.ini File
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14396"> </a>
<b>Note:</b> The <code>rshell.ini</code> file does not support the usage of double-byte character sets such as those used in the Chinese, Japanese, and Korean languages.
</p>
<p class="text">
<a name="15353"> </a>
To understand the structure of the <code>rshell.ini</code> file, use a standard text editor such as NotePad to open <code>Shell\Nsetup32\rshell.ini</code>, and examine the descriptions contained in the file.
</p>
<p class="text">
<a name="14399"> </a>
The <code>rshell.ini</code> file consists of two sections:
</p>
<ul>
<li>
The [General] section is where you specify the attributes of the control buttons (Browse CD, Back, and Exit) that appear at the bottom of the Autorun screens.
<a name="14400"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li>
The [Dialog] sections specify the attributes and behavior of each Autorun screen. Each [Dialog] section defines one Autorun screen, and you name the [Dialog] sections sequentially as [Dialog1], [Dialog2], [Dialog3], and so on, one for each Autorun screen.
<a name="14402"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ul>
<p class="h2">
<a name="15387"> </a>
<a name="General Settings in the rshell.ini File"> </a>
General Settings in the rshell.ini File
</p>
<p class="text">
<a name="15388"> </a>
This section describes the general settings in the <code>rshell.ini</code> file that apply to all dialogs.
</p>
<p class="h3">
<a name="15431"> </a>
<a name="Text for Browse, Back, and Exit Buttons"> </a>
Text for Browse, Back, and Exit Buttons
</p>
<p>
<code>
<a name="14409"></a>
browse_button_text=text
</code>
</p><p>
<code>
<a name="14411"></a>
back_button_text=text
</code>
</p><p>
<code>
<a name="14413"></a>
exit_button_text=text
</code>
</p><p class="text">
<a name="14415"> </a>
Specify the text displayed for the Browse, Back and Exit buttons. The Browse and Exit buttons appear on all dialogs. The Back button only appears if the <code>rshell.ini</code> file specifies more than one dialog.
</p>
<p class="text">
<a name="14417"> </a>
Use an <code>&amp;</code> (ampersand) in front of the character you want to assign as the keyboard shortcut for this button. For example, <code>browse_button_text=Browse &amp;CD</code> sets C as the keyboard shortcut for this button.
</p>
<p class="h4">
<a name="14419"> </a>
<a name="Default Values<br />&nbsp;"> </a>
Default Values<br />&nbsp;
</p>
<p>
<code>
<a name="14420"></a>
browse_button_text=Browse &amp;CD
</code>
</p><p>
<code>
<a name="14422"></a>
back_button_text=Back
</code>
</p><p>
<code>
<a name="14424"></a>
exit_ button_text=Exit
</code>
</p><p class="h3">
<a name="15426"> </a>
<a name="Positions of Browse, Back, and Exit Buttons"> </a>
Positions of Browse, Back, and Exit Buttons
</p>
<p>
<code>
<a name="14426"></a>
browse_button_pos= <em>x1,y1,x2,y2
</em>
</code>
</p><p>
<code>
<a name="14428"></a>
back_button_pos= <em>x1,y1,x2,y2
</em>
</code>
</p><p>
<code>
<a name="14430"></a>
exit_button_pos= <em>x1,y1,x2,y2
</em>
</code>
</p><p class="text">
<a name="14432"> </a>
Specifies the position of the Browse, Back, and Exit buttons, relative to the top left corner (0,0) of the dialog. If not specified, button position is based on dialog size.
</p>
<p class="h4">
<a name="14434"> </a>
<a name="Values<br />&nbsp;"> </a>
Values<br />&nbsp;
</p>
<p class="text">
<a name="14435"> </a>
<em>x1,y1</em>: The upper left coordinates of the button, in pixels, relative to the top left corner of the dialog.
</p>
<p class="text">
<a name="14437"> </a>
<em>x2,y2</em>: The lower right coordinates of the button, in pixels, relative to the top left corner of the dialog. These coordinates are ignored if button bitmap files are specified using the <code>browse_button_bitmaps</code>, <code>back_button_bitmaps</code>, or <code>exit_button_bitmaps</code> setting.
</p>
<p class="h3">
<a name="15442"> </a>
<a name="Bitmaps for the Browse, Back, and Exit Buttons"> </a>
Bitmaps for the Browse, Back, and Exit Buttons
</p>
<p>
<code>
<a name="14439"></a>
browse_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp
</code>
</p><p>
<code>
<a name="14441"></a>
back_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp
</code>
</p><p>
<code>
<a name="14443"></a>
exit_button_bitmaps=up.bmp,dn.bmp,sel.bmp,dis.bmp
</code>
</p><p class="text">
<a name="14445"> </a>
Specifies the button bitmaps used for the Browse, Back, and Exit buttons. Four bitmaps specify the four possible states of the button: up, down, selected, disabled. This setting is optional. If you don't specify bitmaps for a button, the dialog uses a standard Windows button with the text specified in <code>browse_button_text</code>, <code>back_button_text</code>, or <code>exit_button_text</code>.
</p>
<p class="h4">
<a name="14447"> </a>
<a name="Values<br />&nbsp;"> </a>
Values<br />&nbsp;
</p>
<p class="text">
<a name="14448"> </a>
<code>up.bmp</code>: Specifies the bitmap associated with the up (unpressed) button state.
</p>
<p class="text">
<a name="14450"> </a>
<code>dn.bmp</code>: Specifies the bitmap associated with the down (pressed) button state.
</p>
<p class="text">
<a name="14452"> </a>
<code>sel.bmp</code> (optional): Specifies the bitmap associated with the selected (mouse-over) button state.
</p>
<p class="text">
<a name="14454"> </a>
<code>dis.bmp</code> (optional): Specifies the bitmap associated with the disabled button state.
</p>
<p class="h2">
<a name="14456"> </a>
<a name="Dialog Settings"> </a>
Dialog Settings
</p>
<p class="text">
<a name="14458"> </a>
This section describes the global settings that apply within a dialog.
</p>
<p class="h3">
<a name="15736"> </a>
<a name="Caption Text"> </a>
Caption Text
</p>
<p>
<code>
<a name="14461"></a>
caption=caption text
</code>
</p><p class="text">
<a name="14463"> </a>
Specifies the text that appears in the dialog's title bar.
</p>
<p class="h3">
<a name="15737"> </a>
<a name="Dialog Position"> </a>
Dialog Position
</p>
<p>
<code>
<a name="14465"></a>
dialog_position=<em>x1,y1,x2,y2
</em>
</code>
</p><p class="text">
<a name="14467"> </a>
Specifies the position of the dialog on the monitor screen. If not specified, the dialog is displayed at the center of the monitor screen. If <code>bk_bitmap</code> is specified, <em>x2,y2</em> is ignored.
</p>
<p class="h4">
<a name="14469"> </a>
<a name="Values<br />&nbsp;"> </a>
Values<br />&nbsp;
</p>
<p class="text">
<a name="14471"> </a>
<em>x1,y1</em>: Specifies the coordinates, in pixels, relative to the top left corner (0,0) of the dialog.
</p>
<p class="text">
<a name="14473"> </a>
<em>x2,y2</em>: Specifies the coordinates, in pixels, of the lower-right corner of the dialog.
</p>
<p class="h3">
<a name="15738"> </a>
<a name="Background Bitmap"> </a>
Background Bitmap
</p>
<p>
<code>
<a name="14475"></a>
bk_bitmap=background.bmp
</code>
</p><p class="text">
<a name="14477"> </a>
Specifies the background bitmap file used for the dialog. If a background bitmap file is not specified, the dialog uses the system background color for its background color.
</p>
<p class="h3">
<a name="14478"> </a>
<a name="Button Gap"> </a>
Button Gap
</p>
<p>
<code>
<a name="14479"></a>
button_gap=<em>y
</em>
</code>
</p><p class="text">
<a name="14481"> </a>
Specifies the vertical gap (<em>y</em>), in pixels, between the buttons in the dialog.
</p>
<p class="h2">
<a name="14483"> </a>
<a name="Global Text Settings"> </a>
Global Text Settings
</p>
<p class="text">
<a name="14485"> </a>
This section describes the settings used for the title text in a dialog. You use these settings to include a line or paragraph of text that can appear anywhere within the dialog.
</p>
<p class="h3">
<a name="15749"> </a>
<a name="Dialog Title Text"> </a>
Dialog Title Text
</p>
<p>
<code>
<a name="14487"></a>
dialog_title_text=text
</code>
</p><p class="text">
<a name="14489"> </a>
Specifies the title text for the dialog.
</p>
<p class="h3">
<a name="14490"> </a>
<a name="Dialog Title Position"> </a>
Dialog Title Position
</p>
<p>
<code>
<a name="14491"></a>
dialog_title_pos=<em>x1,y1,x2,y2
</em>
</code>
</p><p class="text">
<a name="14493"> </a>
Specifies the position in pixels, relative to the top left corner of the dialog, of the title text.
</p>
<p class="h4">
<a name="14495"> </a>
<a name="Values<br />&nbsp;"> </a>
Values<br />&nbsp;
</p>
<p class="text">
<a name="14497"> </a>
<em>x1,y1</em>: Specifies the position of the top left corner of the text.
</p>
<p class="text">
<a name="14499"> </a>
<em>x2,y2</em>: Specifies the position of the bottom right corner of the text.
</p>
<p class="h3">
<a name="15760"> </a>
<a name="Dialog Title Text Color"> </a>
Dialog Title Text Color
</p>
<p>
<code>
<a name="14501"></a>
dialog_title_text_color=red,green,blue
</code>
</p><p>
<code>
<a name="14503"></a>
dialog_title_shadow_color=red,green,blue
</code>
</p><p>
<code>
<a name="14505"></a>
dialog_title_shadow_depth=red,green,blue
</code>
</p><p class="text">
<a name="14507"> </a>
Specifies the text color, shadow color, and shadow depth of the dialog title text. You specify a number between 0 (black) and 255 (white) for each of the red, green, and blue values to get the overall pixel color.
</p>
<p class="text">
<a name="14509"> </a>
Table 1 lists commonly-used colors from the standard Windows palette.<br />
<p class="caption">
<a name="15771"> </a>
<a name="Windows palette colors"> </a>
Table 11-1 &nbsp;&nbsp; Windows palette colors
</p>
<br/>
<table width="90%" border="1" cellspacing="0" cellpadding="4">
<tr bgcolor="#CCCCCC" align="left" valign="top">
<th valign="top" align="left">
<p class="tablehead">
<a name="15775"> </a>
Color
</p>
</th>
<th valign="top" align="left">
<p class="tablehead">
<a name="15777"> </a>
Red,Green,Blue values
</p>
</th>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15779"> </a>
Black
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15781"> </a>
0,0,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15783"> </a>
White
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15785"> </a>
255,255,255
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15787"> </a>
Red
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15789"> </a>
255,0,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15791"> </a>
Green
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15793"> </a>
0,255,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15795"> </a>
Blue
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15889"> </a>
0,0,255
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15799"> </a>
Yellow
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15801"> </a>
255,255,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15803"> </a>
Magenta
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15805"> </a>
255,0,255
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15807"> </a>
Cyan
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15809"> </a>
0,255,255
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15811"> </a>
Dark red
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15813"> </a>
128,0,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15815"> </a>
Dark green
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15817"> </a>
0,128,0
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15819"> </a>
Dark blue
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15821"> </a>
0,0,128
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15823"> </a>
Dark cyan
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15825"> </a>
0,128,128
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15827"> </a>
Dark gray
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15829"> </a>
128,128,128
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15831"> </a>
Dark magenta
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15833"> </a>
128,0,128
</p></td>
</tr>
<tr>
<td valign="top">
<p class="tabletext">
<a name="15835"> </a>
Gray
</p></td>
<td valign="top">
<p class="tabletext">
<a name="15837"> </a>
192,192,192
</p></td>
</tr>
</table>
</p>
<p class="h3">
<a name="14532"> </a>
<a name="Dialog Title Text Font"> </a>
Dialog Title Text Font
</p>
<p>
<code>
<a name="16062"></a>
dialog_title_text_font=font,size
</code>
</p><p class="text">
<a name="14534"> </a>
Specifies the font and font size used for the dialog's title text. It's best to use a standard font that you know will be available on end users' machines. If not specified, the system font and font size are used.
</p>
<p class="h3">
<a name="14535"> </a>
<a name="Dialog Title Text Style"> </a>
Dialog Title Text Style
</p>
<p>
<code>
<a name="14536"></a>
dialog_title_font_bold=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14538"></a>
dialog_title_font_underline=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14540"></a>
dialog_title_font_italic=TRUE/FALSE
</code>
</p><p class="text">
<a name="14542"> </a>
If set to <code>TRUE</code>, specifies the font style (bold, italic, underline) used for the dialog's title text. If not specified or if set to <code>FALSE</code>, the style is not applied.
</p>
<p class="h2">
<a name="14544"> </a>
<a name="Global Button Text Settings"> </a>
Global Button Text Settings
</p>
<p class="text">
<a name="14546"> </a>
This section describes the text settings used for all button text in a dialog.
</p>
<p class="h3">
<a name="14547"> </a>
<a name="Text Colors"> </a>
Text Colors
</p>
<p class="text">
<a name="14548"> </a>
<code>text_color_default=red,green,blue</code>
</p>
<p class="text">
<a name="14550"> </a>
<code>text_color_highlight=red,green,blue</code>
</p>
<p class="text">
<a name="14552"> </a>
Specifies the default text color and the mouse-over (highlight) text color of all button text in a dialog. You specify a number between 0 (black) and 255 (white) for each of the red, green, and blue values to get the overall pixel color. The text automatically changes to the mouse-over (highlight) text color when you position the mouse over a button in the dialog.
</p>
<p class="text">
<a name="14554"> </a>
<a href="cd_man_cck.htm#15771" >Table&nbsp;11-1</a> lists commonly used colors from the standard Windows palette.
</p>
<p class="h3">
<a name="14556"> </a>
<a name="Button Title and Body Text"> </a>
Button Title and Body Text
</p>
<p>
<code>
<a name="16210"></a>
button_title_text_font=font,size
</code>
</p><p>
<code>
<a name="14558"></a>
body_text_font=font,size
</code>
</p><p class="text">
<a name="14560"> </a>
Specifies the font and size used for the dialog's button title text and button body text. It's best to use a standard font that you know will be available on end users' machines. If not specified, the system font and font size are used.
</p>
<p class="h3">
<a name="16217"> </a>
<a name="Button Title Font"> </a>
Button Title Font
</p>
<p>
<code>
<a name="14562"></a>
button_title_font_bold=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14564"></a>
button_title_font_italic=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14566"></a>
button_title_font_underline=TRUE/FALSE
</code>
</p><p class="text">
<a name="14568"> </a>
If set to <code>TRUE</code>, specifies the font style (bold, italic, underline) used for the dialog's button title text. If not specified or if set to <code>FALSE</code>, the style is not applied.
</p>
<p class="h3">
<a name="14569"> </a>
<a name="Button Body Text Style"> </a>
Button Body Text Style
</p>
<p>
<code>
<a name="14570"></a>
body_text_font_bold=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14572"></a>
body_text_font_italic=TRUE/FALSE
</code>
</p><p>
<code>
<a name="14574"></a>
body_text_font_underline=TRUE/FALSE
</code>
</p><p class="text">
<a name="14576"> </a>
Specifies the font style (bold, italic, underline) used for the dialog's button body text. If not specified or set to <code>FALSE</code>, the style is not applied.
</p>
<p class="h2">
<a name="14578"> </a>
<a name="Column Settings Within a Dialog"> </a>
Column Settings Within a Dialog
</p>
<p class="text">
<a name="14580"> </a>
This section describes the settings used for columns within a dialog. Each dialog can have one or more columns. The settings for the first (left-most) column all begin with col1; the settings for the second column all begin with col2, etc. If you only want one column of buttons in a dialog, delete all of the col2 and greater settings, or you can leave them blank.
</p>
<p class="h3">
<a name="14582"> </a>
<a name="Position of First Button in Column One"> </a>
Position of First Button in Column One
</p>
<p>
<code>
<a name="14583"></a>
col1_button_pos=<em>x,y
</em>
</code>
</p><p class="text">
<a name="14585"> </a>
Specifies the position of the first button in column 1 of a dialog. You specify the <em>x,y</em> coordinates of the upper-left corner of the button, relative to the upper-left corner of the dialog (0,0). If you want, you can specify an offset position for an individual button using the <code>button1_offset</code> setting described later in this chapter.
</p>
<p class="h3">
<a name="14587"> </a>
<a name="Position of a Button's Descriptive Text"> </a>
Position of a Button's Descriptive Text
</p>
<p>
<code>
<a name="16240"></a>
col1_text_offset=offset
</code>
</p><p>
<code>
<a name="14589"></a>
col1_text_posx=<em>x
</em>
</code>
</p><p class="text">
<a name="14591"> </a>
You can use either of these settings to specify the position of the button's descriptive text. Use <code>col1_text_offset</code> if you want to specify the text's position by defining an offset between the button and the button text. Use <code>col1_text_posx</code> instead if you want to specify the absolute <em>x</em> position of the button's descriptive text.
</p>
<p class="text">
<a name="14593"> </a>
If unspecified, the default is <code>col1_text_offset=10</code>. If both settings are specified, <code>col1_text_offset</code> is ignored and the absolute <em>x</em> position as specified in <code>col1_text_posx</code> is used.
</p>
<p class="h3">
<a name="14594"> </a>
<a name="Column Text Width"> </a>
Column Text Width
</p>
<p>
<code>
<a name="14595"></a>
col1_text_width=<em>x
</em>
</code>
</p><p class="text">
<a name="14597"> </a>
Specifies the distance <em>x</em>, relative to the left edge of the dialog box, at which the button descriptive text wordwraps to the next line. If this setting is not specified, the text wordwraps when it is 10 pixels to the left of the right edge of the dialog.
</p>
<p class="h2">
<a name="14599"> </a>
<a name="Button Settings Within a Dialog"> </a>
Button Settings Within a Dialog
</p>
<p class="text">
<a name="14601"> </a>
This section describes the settings used for buttons within a dialog. Each dialog can have one or more buttons. The settings for the first button all begin with button1, the settings for the second button all begin with button2, and so on. If you only want one button in a dialog, delete all of the button2 and greater settings, or leave them blank.
</p>
<p class="h3">
<a name="14602"> </a>
<a name="Button Bitmaps"> </a>
Button Bitmaps
</p>
<p class="text">
<a name="14603"> </a>
<code>button1_bitmaps= up.bmp,dn.bmp,sel.bmp,dis.bmp</code>
</p>
<p class="text">
<a name="14605"> </a>
Specifies the button bitmaps used for button1. Four bitmaps specify the four possible states of the button: up, down, selected, disabled. This setting is optional. If you don't specify bitmaps for a button, the dialog uses a standard Windows button with the text specified in <code>button1_text_title</code>.
</p>
<p class="h4">
<a name="14607"> </a>
<a name="Values<br />&nbsp;"> </a>
Values<br />&nbsp;
</p>
<p class="text">
<a name="14608"> </a>
<code>up.bmp</code>: Specifies the bitmap associated with the up (unpressed) button state.
</p>
<p class="text">
<a name="14610"> </a>
<code>dn.bmp</code>: Specifies the bitmap associated with the down (pressed) button state.
</p>
<p class="text">
<a name="14612"> </a>
<code>sel.bmp</code> (optional): Specifies the bitmap associated with the selected (mouse-over) button state.
</p>
<p class="text">
<a name="14614"> </a>
<code>dis.bmp</code> (optional): Specifies the bitmap associated with the disabled button state.
</p>
<p class="h3">
<a name="14615"> </a>
<a name="Button Action"> </a>
Button Action
</p>
<p>
<code>
<a name="14616"></a>
button1_cmdline=action,target
</code>
</p><p class="text">
<a name="14618"> </a>
Specifies the action you want to assign to the button. Clicking a button can cause one of seven possible actions, depending on the value you specify for the action argument. The possible button actions and arguments are:
</p>
<ul>
<li>
Launch a program (<code>action=exe</code>)
<a name="14619"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14621"></a>
button1_cmdline=exe,path to executable file
</code>
</p></dl></dl> <dl>
<dt> <a name="14623"> </a>
Example: <code>button1_cmdline=exe,..\..\Mozilla\setup.exe</code>
<br />&nbsp;</dt> </dl>
<li>
Go to a different dialog screen (<code>action=window</code>)
<a name="14625"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14627"></a>
button1_cmdline=window,dialog#
</code>
</p></dl></dl> <dl>
<dt> <a name="14629"> </a>
Example: <code>button1_cmdline=window,dialog2</code>
<br />&nbsp;</dt> </dl>
<li>
Open a file (<code>action=open</code>)
<a name="14631"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14633"></a>
button1_cmdline=open, path to file
</code>
</p></dl></dl> <dl>
<dt> <a name="14635"> </a>
The file opens with whatever program the operating system has associated with the file's type. If a file type association doesn't exist, Windows asks the user to choose a program.
<br />&nbsp;</dt> <dt> <a name="14637"> </a>
Example: <code>button1_cmdline=open,..\..\install.txt</code>
<br />&nbsp;</dt> </dl>
<li>
Print a file (<code>action=print</code>)
<a name="14639"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14641"></a>
button1_cmdline=print, path to file
</code>
</p></dl></dl> <dl>
<dt> <a name="14643"> </a>
The file is printed with whatever program the operating system has associated with the file's type. If a file type association doesn't exist, Windows asks the user to choose a program.
<br />&nbsp;</dt> <dt> <a name="14645"> </a>
<b>Note:</b> You cannot print HTML files through Windows.
<br />&nbsp;</dt> <dt> <a name="14649"> </a>
Example: <code>button1_cmdline=print,..\..\install.txt</code>
<br />&nbsp;</dt> </dl>
<li>
Explore a directory on the CD (<code>action=explore</code>)
<a name="14651"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14653"></a>
button1_cmdline=explore,directorypath
</code>
</p></dl></dl> <dl>
<dt> <a name="14655"> </a>
Opens the specified directory on the CD. The directory path must be specified as an absolute path from the root of the CD.
<br />&nbsp;</dt> <dt> <a name="14657"> </a>
Example: <code>button1_cmdline=explore,extras\clipart</code> opens the <code>extras\clipart</code> directory, which is at the root level of the CD.
<br />&nbsp;</dt> </dl>
<li>
Open a file in the Mozilla Browser (<code>action=mozilla</code>)
<a name="14659"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14661"></a>
button1_cmdline=mozilla, path to file
</code>
</p></dl></dl> <dl>
<dt> <a name="14663"> </a>
Opens the specified file using the currently-installed version of the Mozilla Browser. The file type can be <code>.html</code>, <code>.gif</code>, <code>.jpeg</code>, or any other file type that the browser can open, such as <code>.pdf</code> (if the correct plug-in is already installed).
<br />&nbsp;</dt> <dt> <a name="14665"> </a>
Example: <code>button1_cmdline=mozilla,myfile.html</code>
<br />&nbsp;</dt> </dl>
<li>
Create a shortcut on the desktop (<code>action=desktop</code>)
<a name="14667"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14669"></a>
button1_cmdline=desktop, file or directory name, shortcut name,
path to icon file
</code>
</p></dl></dl> <dl>
<dt> <a name="14671"> </a>
When button1 is clicked, a shortcut is created on the desktop, using the specified shortcut name and icon file, that opens the specified file or directory on the CD. File or directory paths must be specified as absolute paths from the root of the CD.
<br />&nbsp;</dt> <dt> <a name="14673"> </a>
Example: <code>button1_cmdline=desktop,readme.txt,Read Me,\shell\icons\readme.ico</code>
<br />&nbsp;</dt> <dt> <a name="16341"> </a>
Button Text
<br />&nbsp;</dt><dl><dl><p>
<code>
<a name="14674"></a>
button1_text_title=text
</code>
</p><p>
<code>
<a name="14676"></a>
button1_text_body=text
</code>
</p></dl></dl> <dt> <a name="14678"> </a>
Specifies the button title text and body text for button1.
<br />&nbsp;</dt> </dl>
</ul>
<p class="h3">
<a name="14679"> </a>
<a name="Button Offset"> </a>
Button Offset
</p>
<p>
<code>
<a name="14680"></a>
button1_offset=<em>x,y
</em>
</code>
</p><p class="text">
<a name="14682"> </a>
Specifies the button's horizontal (<em>x</em>) and vertical (<em>y</em>) offset, in pixels, from the location specified in the <code>col1_button_pos</code> setting. If there is more than one button in column 1, and you only specify an offset for button1, the other buttons in the same column will use the same vertical (<em>y</em>) offset. You can change the offsets for the other buttons by specifying individual button offsets for each of them.
</p>
<p class="h1">
<a name="14684"> </a>
<a name="Editing the rshell.ini File"> </a>
Editing the rshell.ini File
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14686"> </a>
To edit the rshell.ini file:
</p>
<ol type="1">
<li value="1">
Locate the <code>Staging\Shell\nsetup32\rshell.ini</code> file and open it using a standard text editor. Familiarize yourself with the settings in the <code>rshell.ini</code> file.
<a name="14687"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="2">
Decide how many dialog screens you want to use. If you need more dialog screens than are defined in the <code>rshell.ini</code> file, copy an entire <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> section (where <em>x</em> is a unique number associated with each dialog) and paste it as needed into the file. Each dialog screen must have a unique number. If you need fewer than are provided by default, remove entire <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> sections as necessary.
<a name="14689"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Design the layout, background images, buttons, and text for each dialog screen. Make the necessary customizations in the settings in the rshell.ini file.
<a name="16398"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="16399"> </a>
<b>Note:</b> Rather than entering the text for a screen in the <code>rshell.ini</code> file, you may prefer to create your text as part of the background image using an image editing program such as Adobe Photoshop. Using an image editing program gives you more control over the appearance of the text, including fonts and colors.
<br />&nbsp;</dt> </dl>
<li value="4">
Assign an action to each button in each dialog screen.
<a name="14697"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="5">
Save your changes to the <code>rshell.ini</code> file in place; do not move the file.
<a name="14699"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="h2">
<a name="14700"> </a>
<a name="Adding a New Screen"> </a>
Adding a New Screen
</p>
<p class="text">
<a name="14703"> </a>
The supplied <code>rshell.ini</code> file includes a second dialog, Dialog2, that is not visible by default. To enable it, locate the button3 settings that are commented out with semicolons (located within the section in the <code>rshell.ini</code> file called "Buttons 2 - 6 for Dialog 1"). Remove the semicolons in front of all the button3 settings, save your changes, and then launch the Autorun screen by double-clicking the file <code>Shell\nsetup32\Nsetup32.exe</code> file. Click the third button in the first screen (labeled Bonus Applications and Plug-ins) and you'll be able to see the second dialog.
</p>
<p class="text">
<a name="14704"> </a>
To add a new Autorun screen:
</p>
<ol type="1">
<li value="1">
Locate the file <code>Staging\Shell\nsetup32\rshell.ini</code> file and open it using a text editor.
<a name="14705"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="2">
Copy an entire <code>[Dialogx]</code> section and paste it into the <code>rshell.ini</code> file at the location where you want the new screen to appear.
<a name="14707"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Increment the value of <em>x</em> in the <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> identifier, so that the <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> section has a unique number. Each <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> section must have a unique number associated with it, such as<code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font>, <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font>, <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font>.
<a name="14709"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="4">
Make the necessary customizations to each <code>[Dialog</code><em>x</em><font face="fontsansserif" SIZE="+2" COLOR="red">]</font> section.
<a name="16455"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="5">
Save your changes to the <code>rshell.ini</code> file in place; do not move the file.
<a name="16456"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="h2">
<a name="16457"> </a>
<a name="Adding A Background Image to a Dialog Screen"> </a>
Adding A Background Image to a Dialog Screen
</p>
<p class="text">
<a name="14716"> </a>
If you don't specify a background image for a new screen, the new screen uses the system background color. To add a background image to a new screen, follow these steps:
</p>
<ol type="1">
<li value="1">
Using a graphic editing program, create a background bitmap that's 640 x 480 pixels, and save it as a <code>.BMP</code> format file in the <code>shell\bmps\</code> directory.
<a name="14717"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14719"> </a>
Keep the following in mind:
<br />&nbsp;</dt> </dl>
<ul>
<li>
Keep your bitmap file sizes as small as possible by reducing the number of colors the images use or by removing (flattening) the layers if you created the images in Adobe Photoshop. If your images are too large, you may not be able to see them in the Autorun screen. If you cannot see a background image when you test the Autorun screen, open the image in a paint program and try reducing the number of colors to reduce the image's file size.
<a name="14721"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li>
<li>
To prevent palette-swapping when switching between Autorun screens, be sure to use a 256-color palette in each background image you create.
<a name="14723"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li>
<li>
Be sure to leave room at the bottom of the background bitmap (about 40 pixels in height, preferably black) for placement of the control buttons (Browse CD, Back, and Exit) specified in the rshell.ini file.
<a name="14727"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li> <dl>
<dt> <a name="14728"> </a>
For example, here is an illustration of the background bitmap image used to create the standard Autorun screen. Note that a black area 40 pixels high was created at the bottom of the image, to allow placement of the control buttons.<br /><br><img src="gifs/install.gif">
<br>
<br />&nbsp;</dt> </dl>
</ul>
<li value="2">
Open the rshell.ini file using a text editor.
<a name="14732"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Locate the dialog section that you want to customize.
<a name="14733"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="4">
To the right of the <code>bk_bitmap= setting</code>, enter the path to the bitmap file, relative to the location of the shell directory. For example:
<a name="14735"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="17058"></a>
bk_bitmap=..\bmp\myinstall.bmp
</code>
</p></dl></dl>
<li value="5">
Save your changes to the <code>rshell.ini</code> file in place; do not move the file.
<a name="14737"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="h2">
<a name="14738"> </a>
<a name="Customizing a Screen's Title Bar Text"> </a>
Customizing a Screen's Title Bar Text
</p>
<p class="text">
<a name="16948"> </a>
The title bar appears at the top of every autorun dialog screen. You may want to include your company's name in the title bar or provide other identifying information. For example, this screen shows customized text in a CD autorun screen's title bar:<br /><br><img src="gifs/myispshell.gif">
<br><br />
</p>
<p class="text">
<a name="16952"> </a>
To customize a screen's title bar:
</p>
<ol type="1">
<li value="1">
Open the <code>rshell.ini file</code> using a text editor.
<a name="16517"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="2">
Locate the <code>[Dialogx]</code> section that you want to customize.
<a name="14748"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
To the right of the <code>caption= setting,</code> enter the text that you want to appear in the screen's title bar.
<a name="14750"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14751"> </a>
For example, the text "MyISP" results in the title "Mozilla by MyISP"
<br />&nbsp;</dt><dl><dl><p>
<code>
<a name="14752"></a>
caption=MyIsp
</code>
</p></dl></dl> </dl>
<li value="4">
Save your changes to the <code>rshell.ini</code> file in place; do not move the file.
<a name="14754"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="h2">
<a name="14755"> </a>
<a name="Adding a New Button to a Screen"> </a>
Adding a New Button to a Screen
</p>
<p class="text">
<a name="14757"> </a>
You can add a button to an autorun screen that performs any of these functions:
</p>
<ul>
<li>
Launch an executable (<code>.exe</code>) program.
<a name="14758"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14759"> </a>
For example, if you want to include an installer for another application on the CD, you can add a button that users can click to launch the installer.
<br />&nbsp;</dt> </dl>
<li>
Go to another screen
<a name="14761"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14762"> </a>
For example, if you're creating multiple CD autorun screens, you can add a button that users can click to go to a particular screen. (This is in addition to the standard Browse, Back, and Exit buttons that appear on each autorun screen.)
<br />&nbsp;</dt> </dl>
<li>
Open a file
<a name="14764"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14765"> </a>
For example, you can add a button that opens a <code>readme.txt</code> file so that users can read installation instructions for another application you're providing on the CD.
<br />&nbsp;</dt> </dl>
<li>
Print a text file
<a name="14767"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14768"> </a>
For example, you can add a button that prints the installation instructions.
<br />&nbsp;</dt> </dl>
<li>
Explore a directory
<a name="14770"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14771"> </a>
For example, if you're including a directory of utilities on the CD, you can add a button that opens that directory so that user can view its contents.
<br />&nbsp;</dt> </dl>
<li>
Open a file in the Mozilla Browser
<a name="14773"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14774"> </a>
For example, if you've provided an HTML or GIF format file on the CD that you want users to view in Navigator, you can add a button that opens the file using an already-installed version of Navigator.
<br />&nbsp;</dt> </dl>
<li>
Create a shortcut on the user's desktop
<a name="14776"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14777"> </a>
For example, if there's a directory on the CD that you want users to have easy access to, you can create a desktop shortcut for that directory.
<br />&nbsp;</dt> </dl>
</ul>
<p class="text">
<a name="14778"> </a>
To add a new button to an Autorun dialog screen:
</p>
<ol type="1">
<li value="1">
Open the <code>rshell.ini</code> file using a text editor.
<a name="14779"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="2">
Locate the dialog section where you want to add a new button.
<a name="14781"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Within the dialog section, locate the section where the buttons for the dialog are defined. Each button group begins with
<a name="14783"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="17071"> </a>
<code>button1_bitmaps=</code>
<br />&nbsp;</dt> </dl>
<li value="4">
Decide how many buttons you want to appear in the dialog.
<a name="14785"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="5">
If you need more buttons than are defined by default in the <code>rshell.ini</code> file, copy and paste new button groups and increment the button number for each new group you add.
<a name="14787"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="6">
To remove buttons, delete the button groups that are above the number you need, or simply leave their settings blank.
<a name="14789"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="7">
Assign an action to each button using the <code>buttonx_cmdline=</code> setting. You can define any one of seven different button actions. See the description of the <code>buttonx_cmdline=</code> setting earlier in this chapter, or by referring to the comments in the rshell.ini file.
<a name="14791"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl>
<dt> <a name="14793"> </a>
For example, to have button1 go to the dialog2 screen, you would enter:
<br />&nbsp;</dt><dl><dl><p>
<code>
<a name="14795"></a>
button1_cmdline=window,dialog2
</code>
</p></dl></dl> <dt> <a name="14796"> </a>
For example, to have button1 launch a program named Setup.exe, you would enter:
<br />&nbsp;</dt><dl><dl><p>
<code>
<a name="14798"></a>
button1_cmdline=exe,..\..\Mozilla\Setup.exe
</code>
</p></dl></dl> </dl>
<li value="8">
When you have finished defining buttons and button actions, save your changes to the <code>rshell.ini</code> file.
<a name="14799"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="h1">
<a name="14971"> </a>
<a name="Verifying Your CD Autorun Screen Manual Customizations"> </a>
Verifying Your CD Autorun Screen Manual Customizations
<hr size="2" noshade="noshade" />
</p>
<p class="text">
<a name="14972"> </a>
After you finish editing the <code>rshell.ini</code> file, you should view your custom Autorun screens so you can verify your customizations. Follow these steps:
</p>
<ol type="1">
<li value="1">
Locate this directory:
<a name="14974"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<dl><dl><p>
<code>
<a name="14975"></a>
<em>intallation_directory</em>\CCKTool\Configs\<em>my_config</em>\Output\Shell\
</code>
</p></dl></dl>
<li value="2">
To test the CD autorun screens, launch the first screen by double-clicking the file <code>\Shell\Nsetup32\Nsetup32.exe</code>.
<a name="14976"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
<li value="3">
Verify the appearance of your CD autorun screen and test the action of each button.
<a name="14977"> </a>
<img src="pixel.gif" align="top" height="22" alt="" />
</li><br>
</ol>
<p class="text">
<a name="14231"> </a>
</p>
</blockquote>
<!--end bookcontent-->
<!--footercontent defines the bottom navigation and the copyright. It also includes
the revision date-->
<!--start footercontent-->
<blockquote>
<br />
<br />
<span class="navigation">
<a style="text-decoration: none" href="verify_tool_cck.htm">
Previous
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
<span class="navigation">
<a style="text-decoration: none" href="guide.html">
Contents
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
<span class="navigation">
<a style="text-decoration: none" href="advanced_cck.htm">
Next
</a>
</span>
&nbsp;&nbsp;&nbsp;&nbsp;
<hr noshade="noshade" size="1" />
<p class="copy">Copyright &#169; 2003 Netscape Communications Corp. All rights reserved.</p>
<br />
<p class="update">Last Updated <b>October 05, 2001</b></p>
</blockquote>
<!--end footercontent-->
<!--end maincontent-->
</body>
</html>