Option "a" simply uses "dummy" files with filenames matching those of the real MPEG files over on the Emulator. ImageMaker identifies the file type either by the .mmd extension or from where the file is selected in its browser. Therefore, it can create the necessary master script, even if the REAL mmd files aren't really on the Mac or PC.
1. On a PC or Mac create a DVPREP directory. In DVPREP, create a plain text file containing a few hundred characters, and save it under the name "dummy.txt". A readme file from anywhere could also be copied and named "dummy.txt".
2. Obtain a list of the MPEG file names you wish to process.
3. For each MPEG filename, make a copy of dummy.txt, then rename it to match the MPEG filename. For example, the first MPEG on your list has a filename of "booboo.mmd". Duplicate "dummy.txt", then rename the duplicate "booboo.mmd". Repeat until all the MPEGs on your list have a corresponding text file in DVPREP.
4. Run ImageMaker according to the preceding Macintosh or PC section instructions. Make SURE you choose the disc image file to be placed in the DVPREP directory. At some point, ImageMaker (actually Master) will Error and Quit on the text files it assumed were actual mmd files. This is OK. We are only after the master script and disc image parts ImageMaker manufactures.
5. Open the master script file (file ends in .msc) in a text editor that can do search/replace. In OS-9 hard drives are referred to a /h0, /h1, /h2, etc. On the Mac, they have a name, followed by a colon, followed by folder names separated by colons (like Macintosh HD:Homer:DVPREP). On the PC the drive is C:\, D:\...followed by directory names separated by slashes (like D:\HOMER\DVPREP). On both platforms, all the characters preceding the name DVPREP are to be replaced with "/h2/" for use on the emulator. Follow the appropriate Macintosh or PC procedure below:
Macintosh:
Find the first text line containing a drive path and filename. ALL the characters BEFORE the word DVPREP must be replaced with /h2/. For example, a path reading Macintosh HD:Homer:DVPREP would be changed to read /h2/DVPREP. In similar fashion, change all remaining lines in the master script. Save the master script.
IBM Compatibles:
Find the first text line containing a drive path and filename. ALL the characters BEFORE the word DVPREP must be replaced with /h2/. For example, a path reading D:/Homer/DVPREP would be changed to read /h2/DVPREP. In similar fashion, change all remaining lines in the master script. Save the master script.
6. Copy all the files, EXCEPT the .MPEG text files, to a high density MS-DOS floppy.
7. Copy the files from the MS-DOS floppy to the DVPREP directory where the REAL MPEG files are. The OS-9 command: copy /pcd0h/* -w=/h2/DVPREP should work.
8. Assure than script2disc 2.2 has been installed on /h2. Run master, using the master script created. The command master rtf_worm.msc or something similar should work. Master will produce a disc image file. This can take several hours or more, so be patient.
9. Record the disc image according the Emulator instructions. Usually, this can be done with a command similar to:
cdr521 -t=rtf_worm.toc rtf_worm.cd.
For those truly brave souls wishing to try option "b", disc image processing can be done by writing your own master script, or by altering, or adding to, the information in the master script template.Remember, the following information presumes that you have already created .rtf files of your MPEG. If you have not, please read the information about doing this here.
1.) Change the volume name shown in the template to what you'd like the disc image file name to be. Be sure the hard drive and directory you specify the disc image to be on has enough free space - add the file sizes of all the MPEG .rtf's you wish to place on th CD.
2.) You must assign each .rtf to be included in the disc image a "token" name. The token name is just a temporary name used by master in the process of building the disc image. As shown in the template, it is easiest to use the .rtf filename with periods altered to the underscore character. Each .rtf must be specified on a line that follows the format:
green file DARE_RTF from "/h2/DV/DARE.RTF"
where "green file" indicates the source file is already in.rtf format. DARE_RTF is the token name, and "/h2/DV/DARE.RTF" is the .rtf filename as it appears on your hard drive.
3.) Lastly, the disc image directory structure is specified, along with the directory contents. Each token name specified in step 2 is then assigned an actual filename to be used for placement in the "CDI" directory on the WORM. The format is:
"DARE.RTF" protection 0x555 from DARE_RTF
where "DARE.RTF" is the filename to be used, protection 0x555 is the access privilage for the file, and DARE_RTF is the token name used while master is building the disc image.
4.) Make a directory called DVWORM. Save the master script in ASCII format with the name dvworm.msc in the DVWORM directory.
5.) A "dummy" file is needed as a placeholder for several lines in this example master script for CD-i images. Make a copy of some utility, like "/h2/CMDS/attr" and name it "/h2/DVWORM//dummy". For example:
copy /h2/CMDS/attr /h2/DVWORM/dummy
6.) Then chd to DVWORM and type:
master dvworm.msc
Creation of the disc image might take several hours depending on the number and length of your real time files.
master script template
! this comment line marks the beginning of the templateoptions: -s define album "DV Assets" publisher "My company" preparer "Me" volume "DV" in "/h2/DVWORM/dv_worm.cd" application file APPL from "/h2/DVWORM/dummy" message from "/h2/DVWORM/dummy" copyright file Copyright from "/h2/DVWORM/dummy" abstract file Abstract from "/h2/DVWORM/dummy" biblio file Biblio from "/h2/DVWORM/dummy" ! add as many lines as you have RTF's, according to the ! examples below green file DARE_RTF from "/h2/DV/DARE.RTF" green file AEROSPACE_RTF from "/h2/DV/AEROSPACE.RTF" ! the brackets below are VERY important. do NOT delete { "abstract" protection 0x555 from Abstract "bibliographic" protection 0x555 from Biblio "copyright" protection 0x555 from Copyright "CDI" { ! for every line with green file above, there MUST be a ! entry below. The indented bracket must be AFTER all entries "DUMMY" protection 0x555 from APPL "DARE.RTF" protection 0x555 from DARE_RTF "AEROSPACE.RTF" protection 0x555 from AEROSPACE_RTF } } ! this comment line marks the end of the template