Philips' VCD 2.0 Toolkits were designed to allow easy GUI and drag-and-drop creation of VCD titles, and as such are not equipped to allow adding custom files and applications to a VCD disc. Such files can be added, but require the use of a second tool, VCDMaster, in order to accomplish it. VCDMaster comes with the Toolkits, but there are no instuctions in how to use it. Documentation may be purchased, but at extra cost. The procedure below explains how to add files to a Toolkit disc, but is unsupported (unless support for VCDMaster is purchased). Most of the procedure applies to both Mac and PC Toolkits, with the following exceptions:
Mac:

1. VCDMaster is contained in the Drivers folder within the VCD2TK folder.
2. There are 3 ways to put a Mac application on a VCD disc. In order of difficulty:
   1. Binhex or MacBinary encode the application before putting it on the disc. Then the encoded files are referenced in the master script, as described in Step 3. This method requires the end-user to decode the application first, using StuffIt Expander, etc. This is by far the easiest and the recommended procedure.
   2. Create a Mac HFS/CD-ROM XA hybrid, with the Mac applications on the HFS volume. A VCD disc is basically an implemenation of the CD-ROM XA standard. Technically, a disc made this way is not a true VCD disc. This method is not easy to implement, however, as recording packages are not equipped to make a VCD hybrid disc, and may require a special extension in order to read the HFS volume.
   3. Use the Apple Extensions to the CD-ROM standard to put the Mac application on the XA volume. This is possible, but requires custom programming and is completely unsupported by us.
   Note:Creating a Mac HFS/CD-ROM XA multivolume(i.e. multisession) disc has been found not to work. Only the first session is accessible. Even if it did work, in order to read the HFS session the end-user would need the Multisession Mounter, or similar, extension installed on their Mac, and thus this method would not be practical for wide distribution.
3. Text and other files containing only a data fork may be placed in the XA volume by modifying the master script produced during the VCD 2.0 Toolkit build process. This procedure is described below.

1. The VCDMaster front-end application itself is not included with VCD 2.0 Toolkit for PC, only the dll. The front-end may be downloaded in the PC file section in the FTP area of this website.
2. Data, text, and application files may be placed in the XA volume by modifying the master script produced during the VCD 2.0 Toolkit build process. This procedure is described below.

1. Create your VCD title using the Toolkit in the normal manner.
2. Start the build process. When the status window indicates that it has finished writing the master script, stop the build process.
3. There should now be a master script in the destination folder. The name of this script file should be the same as the VCD volume name, with a .msc extension attached. This script file is a normal text file that may be edited in any text editor.
4. Using a text editor, follow the example below to add additional lines to the master script, representing the desired files to be added. Basically the procedure can be broken down as:
   1. Associate a file on a hard drive with an internal identifier in the files definition section.
   2. Later, in the directory structure section, cross-reference that identifier with a file to be created on the cd.
5. Start VCDMaster, and Open the newly edited master script under the File menu. This will create the .cd disc image.