Hi,
that's quite easy:
1)
Either in the SIMH console or in the VAX.INI file used to configure your
simulation, use the following commands:
{from VAX.INI}
; This virtual machine has 256M memory (cpu extend to enable mem 64M)
; note: set cpu extend is not needed, as it is implicitely included
Hi,
I just finished another Blinkenlight project:
An extended SimH runs on a BeagleBone (credit card sized
Linux platform)
and controls real console panels of historical computers, or
simulations
of those panels.
So the project is named BlinkenBone.
First implementation is
Hi,
this means: You want to use the same phyiscal disk image file on the host
system, and tell two (or more ?) SIMH instances to connect to an run on this
same image ?
This reminds me - it should be identical to booting two 11/750s (or whatever
...), both connected to a dual-interface RA81
Hi,
thanks for your new ideas as well :-)
The behaviour you described reminded me to the time when working with real
hardware, especially the one when connecting two VAX's lines together ... and
about the VT teminal connections, I remember that we used to hard-wire DTR
jumpers for some
Hi,
is a required volume is missing during the initial startup - why not simply
create one ? Can be any size, with the same name and controller as it was
before. Then, your system should boot up as usual (as long as no real required
files were on that missing disk).
With SIMH, it's just
