ToolBook
Knowledge Base
Distributing an application without installing the run-time files
|
|
Article: P2687
|
|
The information in this article applies to:
Product: ToolBook
Component: AutoPackager
Product version(s): ToolBook (pre TB 9)
DETAILS
Note that this information does not pertain to ToolBook 9+, as the AutoPackage has substantially changed as of version 9.
As indicated in the Assistant and Instructor 6.5 release notes, the "Icon only (All files remain on CD)" option for AutoPackager has been modified.
The change does have implications for launching other ToolBook books with the "Run Application" and "Open Document" objects from the catalog or with the openScript "run" command, see below for more info on this.
The AutoPackager and its associated setup program have been changed to require that no initialization file or registry changes are made when the ToolBook run-time files are left on the CD, rather than installed to the hard drive.
The changes made are as follows:
- The AutoPackager now marks the shortcut entries in the ASU file that point to books.
- The setup program detects these marked shortcuts and, if the end-user chose to leave the runtime on the CD, the command line attribute of the created shortcut is modified to point directly to tb60_16r.exe or tb60_32r.exe (as appropriate for the operating system) on the CD, passing the book as a parameter.
- The setup program now makes no registry or INI file changes if the end-user chooses to leave the run-time files on the CD.
When the run-time files are left on the CD, there is no TBK file association made with tbload.exe.
Note
The run command (used by the Run application object) will fail when passed a book name if the run-time files are not installed on the hard drive.
| OPENSCRIPT NOTICE The OpenScript programming examples found in many articles may need modification in order to work in ToolBook 9.0 or higher, particularly if the article was written for an older version of ToolBook. To learn more, click here. |
 |
 |
 |
|||
 |
 |
 |