Re: [Simh] Trying to install openvms 7.3 over a Beta install of openvms k7.2
If this is under SIMH, simply create a image of the CD, and mount that under SIMH. Zane > On Aug 7, 2018, at 3:52 PM, Jeremy Begg wrote: > > Hi Jim, > > With only 64218 free blocks on the system disk you might run into problems > upgrading VMS regardless of where the savesets live. > > You could put them in the TLD of another disk. > You can delete the savesets after the upgrade is complete. > > Jeremy > > Sent from my iPad > >> On 8 Aug 2018, at 8:17 am, James W. Laferriere >> wrote: >> >> Hello Jeremy , >> >> On Tue, 7 Aug 2018, Jeremy Begg wrote: >> ...snip... I Very vaugely remember a document that came with the Field Test kit that gave me a hint that it was possible to "Upgrade" from the K7.2 to the production version of 7.2 after the field testing was completed . And of course that document is either extrememly buried or gone . >>> >>> If I recall correctly, to do a VMS upgrade on VAX you put the VMS kit >>> savesets somewhere easily found (e.g. top level directory of the VMS system >>> disk) then run >>> >>> $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] >>> >>> (assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[00] is >>> where you put them). >>> >>> It's possible to tell VMSINSTAL to pause the installation so that you can >>> make changes to the kit: >>> >>> $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] OPTIONS RSP=A >>> >>> This will tell VMSINSTAL to unpack the .A saveset and then it wait at a >>> prompt. Login from another terminal and edit the KITINSTAL.COM procedure >>> which you will find in a newly-created subdirectory of SYS$UPDATE. >>> >>> Somewhere in KITINSTAL.COM it will define the VMS version it is willing to >>> ugprade from. >>> >>> Regards, >>> Jeremy Begg >> >> Working on getting the savesets copied over , But dua0:[00] (*) >> contains critical files I'd really rather not pollute with the savesets . >> Would creating a subdirectory there work too ? I do have another disk >> (well disk file in simh) available I could use if that could work ? >> >> Tia , JimL >> >> (*) >> $ dir VAXX1$DUA0:[00] /size/date >> >> Directory VAXX1$DUA0:[00] >> >> 00.DIR;1 1 29-SEP-1998 10:27:56.56 >> BACKUP.SYS;1 0 29-SEP-1998 10:27:56.56 >> BADBLK.SYS;1 0 29-SEP-1998 10:27:56.56 >> BADLOG.SYS;1 0 29-SEP-1998 10:27:56.56 >> BITMAP.SYS;1 229 29-SEP-1998 10:27:56.56 >> CONTIN.SYS;1 0 29-SEP-1998 10:27:56.56 >> CORIMG.SYS;1 0 29-SEP-1998 10:27:56.56 >> INDEXF.SYS;1 63981 29-SEP-1998 10:27:56.56 >> SECURITY.SYS;1 1 29-SEP-1998 10:27:56.56 >> SYS0.DIR;1 1 29-SEP-1998 10:28:01.01 >> SYSEXE.DIR;1 1 29-SEP-1998 10:28:27.45 >> TCPIP$FTP.DIR;11 22-JUL-2018 16:02:26.81 >> VMS$COMMON.DIR;1 3 29-SEP-1998 10:28:00.49 >> VOLSET.SYS;1 0 29-SEP-1998 10:27:56.56 >> >> Total of 14 files, 64218 blocks. >> >> -- >> +--+ >> | James W. Laferriere | SystemTechniques | Give me VMS | >> | Network&System Engineer | 3237 Holden Road | Give me Linux | >> | bab...@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | >> +--+ > > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Trying to install openvms 7.3 over a Beta install of openvms k7.2
Hi Jim, With only 64218 free blocks on the system disk you might run into problems upgrading VMS regardless of where the savesets live. You could put them in the TLD of another disk. You can delete the savesets after the upgrade is complete. Jeremy Sent from my iPad > On 8 Aug 2018, at 8:17 am, James W. Laferriere > wrote: > >Hello Jeremy , > > On Tue, 7 Aug 2018, Jeremy Begg wrote: > ...snip... >>>I Very vaugely remember a document that came with the Field Test kit >>> that gave me a hint that it was possible to "Upgrade" from the K7.2 to the >>> production version of 7.2 after the field testing was completed . >>>And of course that document is either extrememly buried or gone . >> >> If I recall correctly, to do a VMS upgrade on VAX you put the VMS kit >> savesets somewhere easily found (e.g. top level directory of the VMS system >> disk) then run >> >> $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] >> >> (assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[00] is >> where you put them). >> >> It's possible to tell VMSINSTAL to pause the installation so that you can >> make changes to the kit: >> >> $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] OPTIONS RSP=A >> >> This will tell VMSINSTAL to unpack the .A saveset and then it wait at a >> prompt. Login from another terminal and edit the KITINSTAL.COM procedure >> which you will find in a newly-created subdirectory of SYS$UPDATE. >> >> Somewhere in KITINSTAL.COM it will define the VMS version it is willing to >> ugprade from. >> >> Regards, >>Jeremy Begg > >Working on getting the savesets copied over , But dua0:[00] (*) > contains critical files I'd really rather not pollute with the savesets . >Would creating a subdirectory there work too ? I do have another disk > (well disk file in simh) available I could use if that could work ? > >Tia , JimL > > (*) > $ dir VAXX1$DUA0:[00] /size/date > > Directory VAXX1$DUA0:[00] > > 00.DIR;1 1 29-SEP-1998 10:27:56.56 > BACKUP.SYS;1 0 29-SEP-1998 10:27:56.56 > BADBLK.SYS;1 0 29-SEP-1998 10:27:56.56 > BADLOG.SYS;1 0 29-SEP-1998 10:27:56.56 > BITMAP.SYS;1 229 29-SEP-1998 10:27:56.56 > CONTIN.SYS;1 0 29-SEP-1998 10:27:56.56 > CORIMG.SYS;1 0 29-SEP-1998 10:27:56.56 > INDEXF.SYS;1 63981 29-SEP-1998 10:27:56.56 > SECURITY.SYS;1 1 29-SEP-1998 10:27:56.56 > SYS0.DIR;1 1 29-SEP-1998 10:28:01.01 > SYSEXE.DIR;1 1 29-SEP-1998 10:28:27.45 > TCPIP$FTP.DIR;11 22-JUL-2018 16:02:26.81 > VMS$COMMON.DIR;1 3 29-SEP-1998 10:28:00.49 > VOLSET.SYS;1 0 29-SEP-1998 10:27:56.56 > > Total of 14 files, 64218 blocks. > > -- > +--+ > | James W. Laferriere | SystemTechniques | Give me VMS | > | Network&System Engineer | 3237 Holden Road | Give me Linux | > | bab...@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | > +--+ ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Trying to install openvms 7.3 over a Beta install of openvms k7.2
Hello Jeremy , On Tue, 7 Aug 2018, Jeremy Begg wrote: ...snip... I Very vaugely remember a document that came with the Field Test kit that gave me a hint that it was possible to "Upgrade" from the K7.2 to the production version of 7.2 after the field testing was completed . And of course that document is either extrememly buried or gone . If I recall correctly, to do a VMS upgrade on VAX you put the VMS kit savesets somewhere easily found (e.g. top level directory of the VMS system disk) then run $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] (assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[00] is where you put them). It's possible to tell VMSINSTAL to pause the installation so that you can make changes to the kit: $ @SYS$UPDATE:VMSINSTAL VMS073 DUA0:[00] OPTIONS RSP=A This will tell VMSINSTAL to unpack the .A saveset and then it wait at a prompt. Login from another terminal and edit the KITINSTAL.COM procedure which you will find in a newly-created subdirectory of SYS$UPDATE. Somewhere in KITINSTAL.COM it will define the VMS version it is willing to ugprade from. Regards, Jeremy Begg Working on getting the savesets copied over , But dua0:[00] (*) contains critical files I'd really rather not pollute with the savesets . Would creating a subdirectory there work too ? I do have another disk (well disk file in simh) available I could use if that could work ? Tia , JimL (*) $ dir VAXX1$DUA0:[00] /size/date Directory VAXX1$DUA0:[00] 00.DIR;1 1 29-SEP-1998 10:27:56.56 BACKUP.SYS;1 0 29-SEP-1998 10:27:56.56 BADBLK.SYS;1 0 29-SEP-1998 10:27:56.56 BADLOG.SYS;1 0 29-SEP-1998 10:27:56.56 BITMAP.SYS;1 229 29-SEP-1998 10:27:56.56 CONTIN.SYS;1 0 29-SEP-1998 10:27:56.56 CORIMG.SYS;1 0 29-SEP-1998 10:27:56.56 INDEXF.SYS;1 63981 29-SEP-1998 10:27:56.56 SECURITY.SYS;1 1 29-SEP-1998 10:27:56.56 SYS0.DIR;1 1 29-SEP-1998 10:28:01.01 SYSEXE.DIR;1 1 29-SEP-1998 10:28:27.45 TCPIP$FTP.DIR;11 22-JUL-2018 16:02:26.81 VMS$COMMON.DIR;1 3 29-SEP-1998 10:28:00.49 VOLSET.SYS;1 0 29-SEP-1998 10:27:56.56 Total of 14 files, 64218 blocks. -- +--+ | James W. Laferriere | SystemTechniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | bab...@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +--+ ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] PDP-11 MARK
It would have been nice of you, Dave Porter, to include a link to the source of inspiration for your question: https://retrocomputing.stackexchange.com/q/7056/4025 Leo On Wed, Aug 1, 2018 at 5:26 PM, dave porter wrote: > Not really a simh question, but this might be an appropriate > bunch of people. What actually used MARK on PDP-11? > > I think I recall that some Fortran system (F4P?) used it, > but that's a vague feeling at most. > > Certainly as a Macro-11 kernel-mode weenie, I never > felt the need. > > > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
