MIGLESIAS@UCIVMS.BITNET (Mike Iglesias) (03/11/86)
I'm going to be installing VMS 4.2 on our VAXcluster in about a month, and I've been trying to get my salesman to get ahold of the patches for MTHRTL. He can't seem to find out anything about them. We have self-maintenance, so we can't call the software people without 'an open P.O.' or call TSC. Does anybody know if there is some official DEC part number for the MTHRTL patch kit so I can tell my salesman about it? I've also heard rumors that installing PASCAL will fix it. We currently have PASCAL v3.1, so if I re-install it, will that fix MTHRTL? Also, anybody have any gotchas I should be on the lookout for while installing 4.2? Thanks, Mike Iglesias University of California, Irvine MIGLESIAS@UCIVMSA (BITNET)
kks0@GTE-LABS.CSNET (Kiran Shah) (03/11/86)
If your SWAPFILE.SYS file is of non-standard length(i.e. not the one arrrived at by AUTOGEN) then you should put the actual size in MODPARAMS.DAT instead of 0 as suggested in the System Management and Daily Operations guide on page 11-8. The VMSINSTAL.COM deletes SWAPFILE.SYS file before it creates it again. Kiran Shah GTE Labs. Waltham, Ma
linscomb@NGP.UTEXAS.EDU (Thomas J. Linscomb) (03/14/86)
> Also, anybody have any gotchas I should be on the lookout for while > installing 4.2? Thanks, Mike Iglesias > University of California, Irvine MIGLESIAS@UCIVMSA (BITNET) One problem that I ran into and also noticed made it into the PageSwapper was the system hanging during the upgrade from v4.1 to v4.2. This occured after the message about deinstalling images (end of Phase 1?). After deinstalling images the upgrade procedure goes through and deletes a large number of files (performing a lot of file operations). If it goes far enough it says something to the effect "Now working on [SYS0.SYSEXE]" and "Now working on [SYS0.SYSMGR]" depending on what system directory it is working on. On one of our systems, deleting the files would consistantly cause a hang. The work around I used was to restore the F11BXQP.EXE from the "REQUIRED." saveset of the VMS 4.2 kit into sys$system and reboot (after having to reboot out of the hung upgrade). This problem is similar to all the other hang conditions that have been associated with the early F11BXQP's but it is especially unnerving when it occurs in a "blind" section of the upgrade. The fix only took about 6 passes at the upgrade and about the same number of hours to understand and finally get going. ---------- --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