1.0 LAST MINUTE NOTES There are a few files on the distribution with filetype .LEO which contain updated (later) command files. They have not been fully tested, however. Of special interest is a build file for RTEM, the RT11 emulator that runs on VMS. Some last minute changes have been noted in CHANGE.TXT in this account. 2.0 GETTING ORIENTED To build Decus C, first read NEW.DOC, KIT.DOC, all README.* files and the command files needed to build Decus C on your operating system. The command files may require editing before use on some operating systems, especially RT11. You should also read CC.DOC and WIZARD.DOC to learn about Decus C and its run-time library. 3.0 GETTING ON THE AIR WITH DECUS C If you currently have a Decus C distribution, be sure you make a backup of your current system, then initialize (zero) the accounts used for the new system -- some files that were on the previous distribution have been deleted from this one. There are a few incompatibilities which will require editing and recompiling your C programs; the edited software will then be simpler to transport to other C compilers and operating systems. These are discussed in NEW.DOC, CC.DOC, and the run-time library documentation. 4.0 INSTALLATION TIME ESTIMATES Assuming all goes well, installation on RSTS/E will require about one-half hour to create accounts and read the distribution tape and about two hours to build all programs (using command file [5,1]RBUILD.CMD). This assumes an unloaded 11/70 system. Installation on VMS will require about two and one-half hours to read the distribution tape (because the tape is written in FLX format and must read the entire tape for each account). Building all programs using command file [.COMMAND]VBUILD.COM will require about two and one-half hours on a reasonably-loaded VAX-11/780. Installation time on other systems should be comparable and, in general, proportional to the disk access time. NOTE FLX on RSX-11M has a "/UI" switch, which allows reading files from multiple directories on DOS tapes into the corresponding disk directories, IN ONE PASS. This may work on VAX. I didn't have time to test this, but if so, here's a nifty way to get the files off the tape on to a VAX system in one pass. 1. Create synonym directories UIC style for the VAX directories (e.g. "[5,1]" for [?.COMMAND]) by using MCR PIP's '/EN' switch: $ MC PIP 005001.DIR=COMMAND.DIR/EN where "" is a device or pseudodevice spec, and "" is the path from that device to the parent-to-be of the kit tree. This will allow the files to be written from DOS tape to disk without an output directory spec. 2. Read all files in one pass: $ SET DEF $ MC FLX /RS/UI=MSA0:[*,*]*.*/DO This should put all files into the correct directories. 3. Delete the synonym directories: $MC PIP 005001.DIR/RM This only removes the synonym from the parent directory It's worth a try (RBD). 5.0 SUPPORT FOR THE KIT One last note regarding support for the Decus C system. Martin Minow and I (Bob Denny) have been working on this system for over three years. This has led to my getting an average of three or four calls a week for tapes, and support questions. It's a bit much. I will try valiantly at the Fall Decus Symposium to organize a Decus-C working group within the Structured Languages SIG, and set as it's "prime directive" organization of a support team and a mail-driven support mechanism. Telephone interrupts are inappropriate for such activity. So please be patient until this mechanism gets going.