I've been trying out the VAXstations - 3100M38, 3100M76 and 4000M60, and I'm
not getting much success.
For the M38 and the M60, if I try for a network boot to my (SimH) cluster, I
get ?4B CTRLERR, e.g.
VAXstation 3100 M38 (KA42-B) simulator V4.0-0 Current git commit id:
52a31597
D:/VMS_LSL/LAMPS_SimH/LAMPS1/VAXstation3100M38.ini-4> attach nvr
VAXstation3100M38.nvr
NVR: buffering file in memory
D:/VMS_LSL/LAMPS_SimH/LAMPS1/VAXstation3100M38.ini-7> attach rz0
lamps1_disk0.img
RZ0: 'lamps1_disk0.img' Contains ODS2 File system
RZ0: Volume Name: LAMPS1DISK0 Format: DECFILE11B Sectors In Volume:
832526
D:/VMS_LSL/LAMPS_SimH/LAMPS1/VAXstation3100M38.ini-12> attach rz4 vms552h4.iso
RZ4: 'vms552h4.iso' Contains ODS2 File system
RZ4: Volume Name: VMS2H4055 Format: DECFILE11B Sectors In Volume:
400176
D:/VMS_LSL/LAMPS_SimH/LAMPS1/VAXstation3100M38.ini-17> attach xs eth0 WinPcap
version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0
branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{2EAEE481-D0E8-41B3-A0DA-A0E1AD1CB786} -
Wired Ethernet
sim> boot cpu
Loading boot code from internal ka42b.bin KA42-B V1.5
F_..E?..D...C?..B?..A...9...8?..7...6...5?..4_..3_..2_..1?..
?? E 0040 0000.0014
? D 0050 0000.0081
?? C 0080 0000.0004
?? B 0010 0020.0020
?? 8 0060 0000.0002
?? 5 0001 0000.000A
?? 1 00C0 0000.1004
>>> boot esa0
-ESA0
?4B CTRLERR
?06 HLT INST
PC = 00000C66
>>>
And I see no requests on the boot server.
If I do the same with the M76, it gets further, in that I get
[ESA0:] ?>>>
83 BOOT SYS
-ESA0
?54 RETRY
?54 RETRY
?54 RETRY
?54 RETRY
?54 RETRY
?54 RETRY
?54 RETRY
And on the boot server I see lots of
%%%%%%%%%%% OPCOM 9-MAY-2019 20:05:10.19 %%%%%%%%%%%
Message from user SYSTEM on HARDY1
LANACP MOP V4 Downline Load Service
Volunteered to load request on XQA0 from LAMPS1 Requested file:
DISK$HARDYSYS0:<SYS11.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
$
%%%%%%%%%%% OPCOM 9-MAY-2019 20:05:10.38 %%%%%%%%%%%
Message from user SYSTEM on HARDY1
LANACP MOP V4 Downline Load Service
Load failed for LAMPS1 on XQA0
System image, DISK$HARDYSYS0:<SYS11.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
Failure status: Protocol error (load already in progress)
Has anyone recently managed to get any of these three VAXstations doing a
network boot?
I then tried booting from CDROM and installing VMS (5.5-2H4 - I want to
replicate a particular historical system). Installing VMS and Motif went OK,
and I can boot from DKA0 and login to VMS, but the system looks like a MicroVAX
rather than a VAXstation. Do I need something in my ini file to enable the
graphics? I'd assumed that because these executables say VAXstation, that it
would be enabled by default.
My ini file for the M38 looks like:
set cpu 32m
set cpu idle=vms
set cpu conhalt
attach nvr VAXstation3100M38.nvr
set nar mac=08-00-2B-AA-BB-31
set rz0 rz25
attach rz0 lamps1_disk0.img
set rz1 disable
set rz2 disable
set rz3 disable
set rz4 cdrom
attach rz4 vms552h4.iso
set rz5 disable
set rz7 disable
attach xs eth0
Any comments welcomed!
--
Paul Hardy
Email: p...@paulhardy.net, web: www.paulhardy.net
-----Original Message-----
From: Simh <simh-boun...@trailing-edge.com> On Behalf Of Matt Burke
Sent: 01 May 2019 23:16
To: simh@trailing-edge.com
Subject: Re: [Simh] More VAX Simulators
On 01/05/2019 13:36, m...@wickensonline.co.uk wrote:
> Matt
>
> I've built the VAXstation 4000/60 and 4000/VLC images. Is it possible to
> post an example simh.ini file for either or both of these please, it would
> save me some considerable guesswork!
>
> I have just reconfigured a FreeAXP emulator running on Windows which
> contains SLAVE, formerly an AlphaServer 1000A. It serves up a cluster
> member disk for a 4000/VLC so that will be a great test of your new
> systems.
>
> I previously had lots of trouble with FreeAXP and SIMH residing on the
> same windows box, turns out that FreeAXP really doesn't like WinPCap - it
> crashes on startup and it is very difficult to kill the image.
>
> Regards, Mark.
>
Hi Mark,
The first thing to note (if you haven't spotted it already) is that the
simulators have been merged into the Simh master branch and a number of
fixes have been applied. CD-ROM and tape drive support is now included along
with fixes to the memory sizing for the M60 and VLC.
The VAXstation 4000/60 and 4000/VLC are very similar so this simh.ini will
work for both:
; Set system memory size
; M60 can be one of 8m, 16m, 24m, 32m, 40m, 48m, 56m, 72m, 80m, 104m ;
VLC can be one of 8m, 16m, 24m ; set cpu 24m ; ; Attach the NVRAM device ;
attach nvr vaxstation4000.nvr ; ; Set the MAC address in the network address
ROM ; This will need to match whatever your boot server is expecting ; set
nar mac=08:00:2b:40:00:60 ; ; Setup local SCSI disks if required (here are a
few examples) ; Also try 'help rz'
;
; set rz0 rz26
; attach rz0 disk0.img
; set rz1 disable
; set rz2 disable
; set rz3 disable
; set rz4 rrd40
; attach rz4 vms73.iso
; set rz5 tz30
; attach rz5 backup.tap
; rz6 is always disabled because this is the initiator SCSI ID ; set rz7
disable ; ; Enable LANCE Ethernet (device ESA0 under VMS) ; set xs enable ;
; Attach Ethernet device to a host interface ; attach xs eth0 ; ; Start the
simulator ; boot cpu
The first time the ROM self-test runs after the memory size is changed or
after attaching a new NVRAM file it will perform a thorough memory test.
This can take quite a long time especially with 104MB. You will see multiple
selftest failures but don't worry about it, they're expected for now. After
the self-test completes I would recommend enabling the fast boot option:
>>> SET FBOOT 1
This will significantly speed up subsequent restarts of the simulator.
Eventually I'll patch the ROM to skip the memory tests.
Assuming your boot server is all setup you can now boot from the Ethernet:
>>> BOOT ESA0
I haven't tested Ethernet booting on these simulators for quite some time so
I hope it works!
Let me know how it goes.
Matt
_______________________________________________
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
