Subject: CDROM Production

Here's a quick checklist that I use for producing CDs. Please note that we produce CDs for export to students who may have a wide variety of systems -- so we can't include audio (very few military computers have sound boards), and we must assume a 386, 4 meg RAM, 16 color platform. The checklist helps me remember what I consider to be certain critical steps -- its certainly not all inclusive. Additionally, although it works for me, I haven't sent it to DSP for a validity check. Good luck. Any questions, comments or suggestions? Please call or write - Major Joe Kennedy, USACGSC, kennedyj@leav-emh.army.mil, 913-684 3409.

PREPARING FOR CD PRODUCTION--

Guiding Principles:

  1. Never require students to download any files other than setup or runtime files onto their hard drives - and make sure that's automatic.
  2. Always remove scripts to prevent inadvertent student tampering which could cause unexpected errors.
  3. Limit student options as much as possible to ensure consistent performance of the software -- ensure that you remove as many menubar options as possible.
  4. Never call tech support with partial info - don't waste their time. If you have a philosophical question, E-mail it to tech support and state that it is not an urgent request.
Follow these directions to the letter. Don't worry about how or why something works - just consider it magic until you have a better understanding. There are almost certainly better ways to do this, but this solution works.

  1. Check links for all clips, hyperlinks and other media resources. (see page 4-4, mmtb User Manual and Openscript Reference) Do this by going into each book and selecting "tools, hyperlinks, check book hyperlinks". Check media links using the media resource icon. Correct any problems. Remember - always make links path independent.
  2. Ensure that each book has the following scripts at book level:
    1. a.
      to handle enterApplication
        if "cbt30r.sbk" is not in sysBooks
          push sysToolBookDirectory&"cbt30r.sbk"onto sysbooks
        end
        forward
      end
      
      -- this script, from David Kester, ensures that CBT widgets which require the c tb30r.sbk will work. Another solution is to include the sysbook in the ini file - but ini files can be changed by the user producing unexpected problems.
    2. b.
      to handle enterbook
        linkDll "tb30dos.dll"
        STRING getCDDriveList ()
      end linkDll
      firstCD = textline 1 of getCDDriveList ()
      CDMediaPath of this book = firstCD
      ASYM_Hyperpath of this book = ASYM_Hyperpath of this book&",directory name\,dir
      ectory name\,directory name\"
      forward
      end
      
      -- this script, from Bridie Saccocio and Craig McDonald, sets sysCDMediaPath to the first CD-ROM drive, and lets hyperpaths be relative, no matter what drive was specified in the hyperlink properties. Substitute your actual directory names where you read "directory name". Don't have a clue how it all works, but it does. See also page 6-31, mmtb Users Manual. Note - you need to include this script because all media resources must remain on the CD.
  3. Optimize each book. See page 9-9, mmtb user's manual. Set options to TEMPORARY, MINIMAL. If you change anything in the book after optimizing, you must re-optimize again ("save as" - new name, choose optimize, then resave it again with the original name). This should be your very last step working with the files before producing the CD.
  4. File Structure. Ensure that your file structure matches exactly the file structure you'll put on the CD. (note - remember to remove all the duplicate files created when you "save as" to optimize books)A sure fire way to make sure everything always works is to dump everything into one, and only one, directory. It looks really sloppy, but it works every time.
  5. CTB30r.sbk. Make sure a copy of this file is in a subdirectory before running setup manager. If you don't, you'll get a "sharing" violation because setup manager is also using the same file (can't make a copy of a file in use).
  6. *.key file. Do a file search for *.key. Make sure the value is greater than 0 - if not, full text search won't work at all. To increase the file size, open the file using the notepad and add a space. Size should be >0 - double check file size with file manager.
  7. Setup Manager. Read pages 9-15 to 9-17 -- twice. Set default directory to $install$, common directory to $windows$\asym\runtime. Under "files" tab, make sure that you include a "setup" component - without out it setup won't work. Make sure that all the files listed in the "filelist.wri" are include (off of the cbt disk) -one typo on the .wri -- tbkmmwid.fon isn't on the cd and apparently isn't needed.
  8. Make a test set of disks. Find a system that has never used toolbook (or eliminate all references to toolbook in the windows and system ini files, erase the asym subdirectory, etc, etc). Make sure the system fits the standard configuration.
  9. CD ROM Cutting. Always, always, always do a psudo write test first. This will check to make sure all systems are working correctly. Make sure you set fixation options to "final". Leave all optimization settings on "high". Always exit windows before starting the process. Make sure you're not on the net (disconnet the cable). Once you've tested the first CD and you're satisfied that it works as intended, change the destination to "image file" - this will make it quicker to make multiple copies, and then make copies using the image file as the source. Save the file either on the syQuest, or hide it somewhere on the file server - remember to dump it or the network folks will complain.
Again - hope this helps somewhat. Really designed for my eventual replacement here. Regards, Joe Kennedy.
Revised 6/2/95
brianp@u.washington.edu (Brian Parkhurst)
University of Washington
Box 357260
Seattle, WA 98195-7260
206/543-9175