linscomb@NGP.UTEXAS.EDU (Thomas J. Linscomb) (08/15/86)
Because the AGL redistributes software to other sites at UT, I usually use a MOUNT/COPY sequence to put the BACKUP savesets of products on disk. A funny thing showed up while I was reading the Mandatory Update for MicroVMS version 4.4 off of a TK-50 tape. After reading VMSMUP044.A;1, VMSMUP044.B;1 and VMSMUP044.C;1, COPY read an additional version of these files. To determine if the Updates were different, I broke down each saveset into seperate files. The first savesets were written by "NAMOGLU" on 14-Apr-1986. The second savesets were written by "ELLISON" on 16-Apr-1986. I found that both copies of saveset "B" and saveset "C" contain the same patches. The difference between the two Updates occurs in saveset "A". The second "A" saveset includes an additional patch to STABACKIT.COM. During STABACKIT.COM, this additional patch makes STABACKIT check if WRITEBOOT.EXE exists before it executes it. WRITEBOOT is not executed if it does not exist. This ECO is dated April 16, suprise, suprise! I have checked other copies of the Mandatory update, one off of another TK-50 and the other that we received with our VMS distribution. Both of these included only the first set of Mandatory Updates. (The Mandatory Updates for MicroVMS and VMS have been the same for v4.2 and v4.4.) If I had installed the Update from the tape, then only the first Update would have been found by VMSINSTAL. The additional patch would not have been performed. I have not checked whether the patch fixes the problem in STABACKIT, but I have had to hack STABACKIT on a system that didn't include this patch. ----- --Thomas Linscomb aka linscomb@ngp.UTEXAS.EDU aka cctlinscomb@agl.UTEXAS.EDU --Advanced Graphics Lab/Computation Center/The University of Texas --Austin, TX 78712 phone: 512/471-3241 --uucp: ...seismo!ut-sally!ut-ngp!linscomb linscomb@ut-ngp.UUCP --bitnet: cctj001@utadnx