El 24/12/2012, a les 13:32, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> va escriure:
I have had no problem doing TOPS-10 MONGENs following that.
http://pastebin.com/LDUWrSEA is what happens
This is a succesful MONGEN on KLH10:
Actually, there is a mistake in that MONGEN. The answer to " Load DECnet DTE service (YES,NO) :" must be NO.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
El 23/12/2012, a les 23:38, Cory Smelosky <b4 at gewt.net> va escriure:
I have had no problem doing TOPS-10 MONGENs following that.
http://pastebin.com/LDUWrSEA is what happens
This is a succesful MONGEN on KLH10:
.r setsrc
*cp [10,7,mon]
*^Z
.r mongen
Write MONGEN.MIC (YES,NO) :
% DSK:MONGEN.MIC will not be written
% File DSK:MONGEN.MIC already exists
MONGEN for 704 monitors
MONGEN will generate any known TOPS-10 configuration. For information
about which configurations are supported, please refer to the SPD.
/HELP (PROMPT,SHORT,LONG) ]:
Which GEN (SYS,F) : sys
Output(DSK:SYSCNF.MAC):
DECsystem10 (KL,KS) : kl
CPUs (1,1-6) : 1
System name : BITXT1
CPU0 serial number (1-10000) : 1022
Exclude monitor overhead from user run time (YES,NO) :
EBOX/MBOX runtime accounting (YES,NO) :
Exclude PI time from user runtime (YES,NO) :
Account verification (YES,NO) : no
MOS memory (YES,NO) :
Autoconfigured device options:
Include SCA (NO,YES,PROMPT):
Include Ethernet service (NO,YES,PROMPT): yes
Include SA10 device support (NO,YES,PROMPT):
Include RP01/2/3 disks (NO,YES,PROMPT):
Include Swapping drums (NO,YES,PROMPT):
Include RS04/5 Massbus disks (NO,YES,PROMPT):
Prompt for RP0x/RM0x Massbus disks (NO,YES): yes
Device code (CR,0-774) :
Massbus device (0,0-7) :
Drive, slave, or unit: all
Data:
Do you want to specify more data (NO,YES):
Include DX20/RP20 disks (NO,YES,PROMPT):
Include TM02/TM03 magtapes (NO,YES,PROMPT): yes
Include DX10/TX01/TX02 tapes (NO,YES,PROMPT):
Include DX20/TX02 tapes (NO,YES,PROMPT):
Include TM78/TU78/TU79 magtapes (NO,YES,PROMPT):
Include TM10B magtapes (NO,YES,PROMPT):
Include TC10C magtapes (NO,YES,PROMPT):
Include BA10/LP100 printers (NO,YES,PROMPT):
Include CFE/LP20 printers (NO,YES,PROMPT):
Include XY10 plotters (NO,YES,PROMPT):
Include CR10 card readers (NO,YES,PROMPT):
Include CFE/CD20 card readers (NO,YES,PROMPT):
Include CP10/CP10D card punches (NO,YES,PROMPT):
Include PC04 paper tape punches (NO,YES,PROMPT):
Include PC04 paper tape readers (NO,YES,PROMPT):
Types of DTE service to load:
Load ANF-10 DTE service (YES,NO) : no
Load IBMCOMM DTE service (YES,NO) : no
Load DECnet DTE service (YES,NO) : yes
Local terminal configuration:
Configure old terminal scanners (NO,YES) :
How many RSX-20F TTYs on CPU0 (0,0-128) :
OPR octal line number (CTY,0-3) : cty
Data set lines
Number of Jobs (1-511) : 511
Maximum pages of core for each job (0,0-16384) :
Total amount of system core in K (512-4096) : 4096
Number of real-time devices (0,0-77) :
Allow jobs to be locked in core (YES,NO) :
Guaranteed number of pages for unlocked jobs (0,0-16384) :
Number of pages reserved for locking jobs in Exec Virtual Memory (10,0-?) :
Number of high priority interrupt queues (0,0-15): 5
Meter (NO,YES) :
KASER (NO,YES) :
MPXSER (YES,NO) :
PSISER (YES,NO) :
IPCF (YES,NO) :
ENQ/DEQ (YES,NO) :
Disk sets (ALL) :
Configure non-autoconfigured hardware (NO,YES) :
Number of PTYs (20,1-505) :
Network software (YES,NO) : yes
Node name : BITX>T1
Number of remote TTYs (485,0-485) :
ANF-10 software (YES,NO) : no
DECnet software (YES,NO) :
Node name (BITX) : BITXT1
Area number of central site (1,1-63) : 7
Node number of central site (1,1-1023) : 80
Router type (ROUTING,NONROUTING) : NONR
Transmit password (DECNET20) :
Remote terminals (YES,NO) :
LAT software (YES,NO) :
Node name (BITX) : BITXT1
Number of circuits (20,1-100) :
Service groups :
Decimal "symbol,value"
Octal "symbol,value"
SIXBIT "symbol,value"
Type "device-mnemonic,PI-channel" for special devices
Type "device-mnemonic,PI-channel,no.-of-devices"
Type "device-mnemonic,PI-channel,highest-ac-to-save"
Type "ersatz-device,P,Pn,search-list-type"
Type "command-name,dispatch,flags,unique-bits,PRVTAB-name"
Terminal class :
Additional terminals for classes:
Class to extend :
System default terminal type (TTY) : VT102
File DSK:SYSCNF.MAC Closed
Which GEN (SYS,F) : f
Output(DSK:F.MAC):
Feature set (KL10,KS10) : KL10
Standard settings (YES,NO) :
File DSK:F.MAC Closed
Which GEN (SYS,F) : ^Z
EXIT
.dir *.mic
MONGEN MIC 7 <057> 24-Dec-12 DSKB: [10,7,MON]
LINKM MIC 1 <057> 31-May-12 DSKC:
COMPIL MIC 1 <057> 31-May-12
Total of 2 blocks in 2 files on DSKC: [10,7,MON]
Grand total of 9 blocks in 3 files
.type compil.mic
00100 .COMPILE/COMPILE F,S
00200 .COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
00300 .COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
00400
00500 .R LINK
00600 *NEWSYS/SAVE/NOINITIAL/HASH:13K = /LOCALS -
00700 *COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
00800 */PATCH:200/COUNTERS/GO
00900
. at compil
.COMPILE/COMPILE F,S
MACRO: F
MACRO: S
EXIT
.COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
MACRO: DEVPRM
MACRO: DTEPRM
MACRO: NETPRM
MACRO: D36PAR
EXIT
.COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
MACRO: COMMON
MACRO: COMDEV
MACRO: COMMOD
EXIT
.
.R LINK
*NEWSYS/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 155054 330000
.HIGH. 340000 650677 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766606 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
.^Z
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
You have to install a small kit. It can be found in the freeware CDs IIRC. For your convenience I have copied it to BITXOO::DUA1:[KITS]
By the way, a 4.7 system works nicely as area router. Small footprint and overhead ;)
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
El 24/12/2012, a les 8:47, Cory Smelosky <b4 at gewt.net> va escriure:
Also, how did you license decnet? It asks me to license it when I run STARTNET.COM
You can use 7.3 to generate a bootable standalone backup on a RL02 disk. Then you can boot that RL02 in the 780 and proceed with the install. You can't boot a tape in the SIMH 780.
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
El 24/12/2012, a les 3:23, Johnny Billquist <bqt at softjar.se> va escriure:
On 2012-12-24 03:05, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
I might have the wrong tape.
Is there some specific reason for V4.6?
Get a news VMS version -- I can make V6.something or V7.something available
for you -- and then, restore the .B save set to your boot device. Then, you
boot from the system disk to continue the install. Back then, VMS was dis-
tributed on tape. I've no idea how you access that from SimH. During the
boot, VMS will prompt you to enter where the distribution media is mounted
and then, it will just do the rest -- just answer to the questions as they
arise.
If I can find the time, I'll get to my storage unit and pull the V4 (orange
wall) tomes with the installation notes for 11/780 just in case.
As I remember the procedure, it's kindof tricky to see how you'd do it in simh.
On a real 11/780, you'd boot the standalone backup first. Not sure, but I think that would have been a bunch of RX01 floppies.
One the standalone backup is running, you can restore the distribution tape .B saveset to the destination disk, and after that, things starts getting easier.
However, as simh don't have the FE, nor RX01, how do you get the standalone backup running?
I wonder if you could use the standalone backup from a newer VMS to install a really old version. Recent CD distributions boot the standalone backup, and I suspect you would able to boot simh into that.
Not sure what Cory's real problem is though, as he claims he now restores the .B saveset and still don't get a bootable system. Did the backup restore the saveset without complaints?
What is the name of the saveset you are restoring, Cory?
Have you atleast read through the installation manual for a recent VMS? I think the basic procedure is unchanged.
Johnny
On 24 Dec 2012, at 02:33, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
BITXOO runs 4.7 ;)
I can post a RL02 with a bootable 4.7 BACKUP if that could be of help to bootstrap the 4.7 install.
No need now, I figured it with a little help from the mailing list and then some random button mashing.
Thanks though. We could maybe put some documentation on doing this whole install up somewhere. Maybe a wiki article over on gunkies? ;)
Also, how did you license decnet? It asks me to license it when I run STARTNET.COM
(fun fact: I found a typo when running NETCONFIG on 5.2)
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
El 24/12/2012, a les 1:58, Cory Smelosky <b4 at gewt.net> va escriure:
On 23 Dec 2012, at 19:57, "Steve Davidson" <jeep at scshome.net> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: Sunday, December 23, 2012 19:52
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] New node in area 19
On 23 Dec 2012, at 19:51, "Steve Davidson" <jeep at scshome.net> wrote:
Johnny,
Please add node 19.140 name DWARF to DECnet. It is a SimH
instance on
a Raspberry Pi. It will be running VMS (VAX-11/780).
Which version of VMS?
-Steve
V7.3 at the moment. It will be running multiple versions as time
permits. It is a dual boot. It can boot standalone or as a cluster
member (satellite). When I find my VAX-11/780 documentation I will
choose the drives that were available at the time to be as close as
possible to a "real" system.
I think I may do something similar, due to having difficulty booting anything other than V7.3 on the 780 simulator. ;)
-Steve
BITXOO runs 4.7 ;)
I can post a RL02 with a bootable 4.7 BACKUP if that could be of help to bootstrap the 4.7 install.
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
El 24/12/2012, a les 1:58, Cory Smelosky <b4 at gewt.net> va escriure:
On 23 Dec 2012, at 19:57, "Steve Davidson" <jeep at scshome.net> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: Sunday, December 23, 2012 19:52
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] New node in area 19
On 23 Dec 2012, at 19:51, "Steve Davidson" <jeep at scshome.net> wrote:
Johnny,
Please add node 19.140 name DWARF to DECnet. It is a SimH
instance on
a Raspberry Pi. It will be running VMS (VAX-11/780).
Which version of VMS?
-Steve
V7.3 at the moment. It will be running multiple versions as time
permits. It is a dual boot. It can boot standalone or as a cluster
member (satellite). When I find my VAX-11/780 documentation I will
choose the drives that were available at the time to be as close as
possible to a "real" system.
I think I may do something similar, due to having difficulty booting anything other than V7.3 on the 780 simulator. ;)
-Steve
On 23 Dec 2012, at 21:42, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-12-24 03:37, Cory Smelosky wrote:
On 23 Dec 2012, at 21:33, "Steve Davidson" <jeep at scshome.net> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: Sunday, December 23, 2012 21:25
To: hecnet at Update.UU.SE
Cc: Brian Schenkenberger, VAXman-
Subject: Re: [HECnet] Older VAXVMS Install kits?
On 23 Dec 2012, at 21:23, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-12-24 03:05, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
I might have the wrong tape.
Is there some specific reason for V4.6?
Get a news VMS version -- I can make V6.something or V7.something
available for you -- and then, restore the .B save set to
your boot
device. Then, you boot from the system disk to continue
the install.
Back then, VMS was dis- tributed on tape. I've no idea how you
access that from SimH. During the boot, VMS will prompt
you to enter
where the distribution media is mounted and then, it will
just do the
rest -- just answer to the questions as they arise.
If I can find the time, I'll get to my storage unit and
pull the V4
(orange
wall) tomes with the installation notes for 11/780 just in case.
As I remember the procedure, it's kindof tricky to see how
you'd do it in simh.
On a real 11/780, you'd boot the standalone backup first.
Not sure, but I think that would have been a bunch of RX01 floppies.
One the standalone backup is running, you can restore the
distribution tape .B saveset to the destination disk, and
after that, things starts getting easier.
However, as simh don't have the FE, nor RX01, how do you
get the standalone backup running?
I wonder if you could use the standalone backup from a
newer VMS to install a really old version. Recent CD
distributions boot the standalone backup, and I suspect you
would able to boot simh into that.
I'm booting VMS 7.3 and running backup from there to image it
to another disk. Does it NEED to be standalone backup?
Not sure what Cory's real problem is though, as he claims
he now restores the .B saveset and still don't get a bootable
system. Did the backup restore the saveset without complaints?
What is the name of the saveset you are restoring, Cory?
Have you atleast read through the installation manual for a
recent VMS? I think the basic procedure is unchanged.
It copies the backup set without issue. Am I perhaps
attaching it to the wrong tape device? (tq)
Johnny
It can be standalone or not. Try:
$backup/image/verify <version-saveset>.b/save <device>:
THAT worked.
What line did you use before? And why didn't you read the manuals?
Anyway. Good that you got somewhere.
I even managed to get VMS 4.0 to work. Turns out I needed to copy REQUIRED. instead of <VER>.A.
Johnny
On 24 Dec 2012, at 00:16, Cory Smelosky <b4 at gewt.net> wrote:
Hey Johnny,
When you get the chance, add MAE (9.11) to the novelist!
Let's plan for the future so I won't need to bug you:
MOYA (9.12)
MOIRA (9.13)
as well.
Thanks!
On 23 Dec 2012, at 21:42, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-12-24 03:37, Cory Smelosky wrote:
On 23 Dec 2012, at 21:33, "Steve Davidson" <jeep at scshome.net> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: Sunday, December 23, 2012 21:25
To: hecnet at Update.UU.SE
Cc: Brian Schenkenberger, VAXman-
Subject: Re: [HECnet] Older VAXVMS Install kits?
On 23 Dec 2012, at 21:23, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-12-24 03:05, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
I might have the wrong tape.
Is there some specific reason for V4.6?
Get a news VMS version -- I can make V6.something or V7.something
available for you -- and then, restore the .B save set to
your boot
device. Then, you boot from the system disk to continue
the install.
Back then, VMS was dis- tributed on tape. I've no idea how you
access that from SimH. During the boot, VMS will prompt
you to enter
where the distribution media is mounted and then, it will
just do the
rest -- just answer to the questions as they arise.
If I can find the time, I'll get to my storage unit and
pull the V4
(orange
wall) tomes with the installation notes for 11/780 just in case.
As I remember the procedure, it's kindof tricky to see how
you'd do it in simh.
On a real 11/780, you'd boot the standalone backup first.
Not sure, but I think that would have been a bunch of RX01 floppies.
One the standalone backup is running, you can restore the
distribution tape .B saveset to the destination disk, and
after that, things starts getting easier.
However, as simh don't have the FE, nor RX01, how do you
get the standalone backup running?
I wonder if you could use the standalone backup from a
newer VMS to install a really old version. Recent CD
distributions boot the standalone backup, and I suspect you
would able to boot simh into that.
I'm booting VMS 7.3 and running backup from there to image it
to another disk. Does it NEED to be standalone backup?
Not sure what Cory's real problem is though, as he claims
he now restores the .B saveset and still don't get a bootable
system. Did the backup restore the saveset without complaints?
What is the name of the saveset you are restoring, Cory?
Have you atleast read through the installation manual for a
recent VMS? I think the basic procedure is unchanged.
It copies the backup set without issue. Am I perhaps
attaching it to the wrong tape device? (tq)
Johnny
It can be standalone or not. Try:
$backup/image/verify <version-saveset>.b/save <device>:
THAT worked.
What line did you use before? And why didn't you read the manuals?
backup vms052.b/save_set dual: As per the VMS 5.0 documentation, with 50 changed to 52.
However, doing backup/image/verify vms052.b/save dua1: worked.
I will go back to trying VMS 4.6 in a bit.
Anyway. Good that you got somewhere.
Johnny
