Discussion:
[Simh] Trying to install openvms 7.3 over a Beta install of openvms k7.2
James W. Laferriere
2018-08-06 21:37:02 UTC
Permalink
Hello All , Some many years ago I was involved with the Beta testing of
OpenVMS 7.2 called K7.2 . VMSInstal does not recognize the K in the version
number and stops the upgrade with version NOT acceptable message .

What I geuess I'd like to do is LIE to the VMSInstal procedure by
removing the K from the reported version report .

Anyone ever had a chance to do this ?

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 .


Tia , JimL
--
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road | Give me Linux |
| ***@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP |
+------------------------------------------------------------------+
Jeremy Begg
2018-08-06 22:56:55 UTC
Permalink
Hi James,
Post by James W. Laferriere
Hello All , Some many years ago I was involved with the Beta testing of
OpenVMS 7.2 called K7.2 . VMSInstal does not recognize the K in the version
number and stops the upgrade with version NOT acceptable message .
What I geuess I'd like to do is LIE to the VMSInstal procedure by
removing the K from the reported version report .
Anyone ever had a chance to do this ?
No, but it shouldn't be too difficult with a modest amount of editing ...
Post by James W. Laferriere
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:[000000]

(assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[000000] 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:[000000] 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
James W. Laferriere
2018-08-07 22:47:04 UTC
Permalink
Hello Jeremy ,

On Tue, 7 Aug 2018, Jeremy Begg wrote:
...snip...
Post by Jeremy Begg
Post by James W. Laferriere
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
(assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[000000] is
where you put them).
It's possible to tell VMSINSTAL to pause the installation so that you can
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:[000000] (*)
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:[000000] /size/date

Directory VAXX1$DUA0:[000000]

000000.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;1 1 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 | System Techniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road | Give me Linux |
| ***@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP |
+------------------------------------------------------------------+
Jeremy Begg
2018-08-07 22:52:08 UTC
Permalink
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
Post by James W. Laferriere
Hello Jeremy ,
...snip...
Post by Jeremy Begg
Post by James W. Laferriere
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
(assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[000000] is
where you put them).
It's possible to tell VMSINSTAL to pause the installation so that you can
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:[000000] (*) 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:[000000] /size/date
Directory VAXX1$DUA0:[000000]
000000.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;1 1 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 | System Techniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road | Give me Linux |
+------------------------------------------------------------------+
Zane Healy
2018-08-08 00:15:00 UTC
Permalink
If this is under SIMH, simply create a image of the CD, and mount that under SIMH.

Zane
Post by Jeremy Begg
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
Post by James W. Laferriere
Hello Jeremy ,
...snip...
Post by Jeremy Begg
Post by James W. Laferriere
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
(assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[000000] is
where you put them).
It's possible to tell VMSINSTAL to pause the installation so that you can
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:[000000] (*) 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:[000000] /size/date
Directory VAXX1$DUA0:[000000]
000000.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;1 1 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 | System Techniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road | Give me Linux |
+------------------------------------------------------------------+
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh
Johnny Billquist
2018-08-08 10:58:37 UTC
Permalink
Also, unless I'm totally misremembering, the savesets can be anywhere.
They do not have to be in the root directory.

Johnny
Post by Zane Healy
If this is under SIMH, simply create a image of the CD, and mount that under SIMH.
Zane
Post by Jeremy Begg
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
Post by James W. Laferriere
Hello Jeremy ,
...snip...
Post by Jeremy Begg
Post by James W. Laferriere
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
(assuming your kit savesets are VMS073.A, VMS073.B, etc and DUA0:[000000] is
where you put them).
It's possible to tell VMSINSTAL to pause the installation so that you can
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:[000000] (*) 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:[000000] /size/date
Directory VAXX1$DUA0:[000000]
000000.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;1 1 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 | System Techniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road | Give me Linux |
+------------------------------------------------------------------+
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: ***@softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Loading...