[Simh] Problem booting RSX11M on pdp11 (halt at loc 0)

Discussion:

Phil J Fisher

2018-03-22 10:15:05 UTC

Hi

can anyone suggest what I have done wrong or what I am missing?

I am running SIMH 3.9 (from the SimH site) on a Centos6 system run under
VMware (also VirtualBox gives same results). I have been using Bob
Evans RSX11M information from his site.
When I load the simulator using mostly his sim.ini file (I removed his
telnet stuff that was built in) and type the usual 'BOOT RL0' (or 'boo
rl0') I get a Halt at PC 0.
Examining the code at location 0 I get (as expected from output) a HLT
instruction (000000 octal).

The disk images do not appear to be corrupted but I am not aware of any
MD5 or similar checksums to be certain.

Anyone any ideas what I am missing or doing wrong?

My only thought was that I was running pdp11 SimH under a virtualization
system (or in crude terms a simulator within a emulator/simulator) and
wondered if that was the issue. But some searching showed a number of
people who have successfully run SimH simulators under VMware at least.
So at the moment I am inclined to believe that is not the issue.

My initial PC is a Windows 10 Home, running VMware Workstation 14 (or
VirtualBox 5.2.8) and hence to a Centos 6.9 system with 2GB RAM, 1 vCPU.

--
Phil J Fisher

Jordi Guillaumes Pons

2018-03-22 10:20:43 UTC

Permalink

My only thought was that I was running pdp11 SimH under a virtualization system (or in crude terms a simulator within a emulator/simulator) and wondered if that was the issue. But some searching showed a number of people who have successfully run SimH simulators under VMware at least. So at the moment I am inclined to believe that is not the issue.

Iâve run simh under virtualization without any problem.

I suggest you to try the current 4.0 beta, which is quite stable and adds a lot of enhancements over 3.9. You can get the sources from github ((https://github.com/simh/simh <https://github.com/simh/simh>) and build it yourself. I donât know if there are precompiled binaries around, but to build it is quite easy and the prerrequisites are just a few.

In any case, could you share your pdp11.ini file and maybe the image you are using?

Jordi Guillaumes i Pons
***@jordi.guillaumes.name
HECnet: BITXOW::JGUILLAUMES

Paul Koning

2018-03-22 13:24:30 UTC

Permalink

Post by Phil J Fisher
Hi
can anyone suggest what I have done wrong or what I am missing?
I am running SIMH 3.9 (from the SimH site) on a Centos6 system run under VMware (also VirtualBox gives same results). I have been using Bob Evans RSX11M information from his site.
When I load the simulator using mostly his sim.ini file (I removed his telnet stuff that was built in) and type the usual 'BOOT RL0' (or 'boo rl0') I get a Halt at PC 0.
Examining the code at location 0 I get (as expected from output) a HLT instruction (000000 octal).
The disk images do not appear to be corrupted but I am not aware of any MD5 or similar checksums to be certain.

A simple check would be to look at the first block of the image you have attached to the drive you're booting. Try "hexdump -0 -n 512". You might see something like this:

$ hexdump -o -n 512 ~/Documents/e11/v101du.dsk
0000000 000240 000572 000006 000000 000012 000000 000020 172150
0000010 052504 012707 054464 000000 001570 021041 000041 000000
0000020 000000 000000 000000 000606 000471 010705 062705 000344
0000030 012700 000064 005025 077002 016767 177740 000436 016767
0000040 177734 000454 016767 177730 000450 016767 177730 000420
...

A reasonably new PDP11 disk has a boot block starting with 000240 (NOP). If it's old it might just start with something executable, like this RSTS V4 (1972 vintage) system disk:

$ hexdump -o -n 512 ~/Documents/e11/v4.dsk
0000000 012700 000024 016701 000162 010104 012021 020027 000200
0000010 001374 010407 162701 000020 012702 000005 000005 010704
...

If it starts with 0 but the word after contains what looks like PDP11 code, it could be a disk for a PRO, though that would be a bit odd and certainly would not be the case for an RL02 image.

paul

Phil Fisher

2018-03-22 20:21:09 UTC

Permalink

I have checked up some information and found the following. (if anyone wants to see the INI file or the disk image I can send that directly as a 7zip file).

Looking at the dump of the disk file it looks like a valid boot block although (as below from offset 0):

0000000 000240 000406 000000 002467 000000 000000 000000 000000

0000010 012704 001000 ...

suggesting a code start of:

NOP
BR 1$
.word 0
.word 02467
.word 0
.word 0
.word 0
.word 0
1$: MOV #1000,R4
...

all values in octal.

So to me this looks at least sensible. Alas I cannot recall what the old RK05 boot block looked like for comparison as I was at one time VERY familiar with that.

So my thoughts are that BOOT is broken somehow or I have majorly screwed up the INI file.

Phil
--
Phil J Fisher ***@peejayeff.co.uk
_____________________________________________________
Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________

Mike Stramba

2018-03-22 21:04:56 UTC

Permalink

Phil,

I assume this is the site ? :

http://home.earthlink.net/~n1be/pdp11/PDP11.html

I'm downloading it now will try it on my Win7 laptop.

Have tried / been successful running it on a "native" O.S (not under
VmWare or VirtualBox ?)

I.e is the point to try to get it running under VmWare / Vbox .. or
just it running period ? ;)

Mike

Post by Phil Fisher
I have checked up some information and found the following. (if anyone wants
to see the INI file or the disk image I can send that directly as a 7zip
file).
Looking at the dump of the disk file it looks like a valid boot block
0000000 000240 000406 000000 002467 000000 000000 000000 000000
0000010 012704 001000 ...
NOP
BR 1$
.word 0
.word 02467
.word 0
.word 0
.word 0
.word 0
1$: MOV #1000,R4
...
all values in octal.
So to me this looks at least sensible. Alas I cannot recall what the old
RK05 boot block looked like for comparison as I was at one time VERY
familiar with that.
So my thoughts are that BOOT is broken somehow or I have majorly screwed up the INI file.
Phil
--
_____________________________________________________
Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh

Phil Fisher

2018-03-25 18:52:57 UTC

Permalink

Further to recent communications on this topic (for which many thanks to those persons) and some thinking I have a potential/possible reason that I would like comments on.

My thinking goes that if in the virtualisation setup I have the "disk" is not responding quickly enough for the RL driver in SimH then maybe it will return a buffer of zeros.

Now even if I am on the right track for this, it leaves some questions (in no particular order):

a) others have reported being able to use SimH 4.0 under virtualisation with no issues although not with RSX11M. So why would I be different?
b) I would have thought that the driver for RL especially as it is emulating hardware would not "timeout" so quickly.
c) If it did timeout, why have I not seen an error message? Maybe I need to look somewhere else ... hmm.

And the obvious statement that I am completely wrong and it is something I have configured incorrectly either in the virtualisation environment (except it gives same error under both Virtual Box and VMware Workstation) or in SimH.

Phil

----- Original Message -----
From: Mike Stramba <***@gmail.com>
Reply-To: <***@gmail.com>
To: Phil Fisher <***@peejayeff.co.uk>
Cc: <***@trailing-edge.com>
Sent: 22/03/2018 21:04:56
Subject: Re: [Simh] Problem booting RSX11M on pdp11 (halt at loc 0)
________________________________________________________________________________

Phil,

I assume this is the site ? :

http://home.earthlink.net/~n1be/pdp11/PDP11.html

I'm downloading it now will try it on my Win7 laptop.

Have tried / been successful running it on a "native" O.S (not under
VmWare or VirtualBox ?)

I.e is the point to try to get it running under VmWare / Vbox .. or
just it running period ? ;)

Mike

Mark Pizzolato

2018-03-25 19:25:09 UTC

Permalink

Post by Phil Fisher
Further to recent communications on this topic (for which many thanks to
those persons) and some thinking I have a potential/possible reason that I
would like comments on.
My thinking goes that if in the virtualisation setup I have the "disk" is not
responding quickly enough for the RL driver in SimH then maybe it will return
a buffer of zeros.

That theory is not correct. "Time" for the RL simh device is measured in
instructions simulated AND disk transfers occur immediately after that
number of instructions (BEFORE executing another instruction). This makes
the simulation insensitive to the host system's CPU speed and I/O rates.

Post by Phil Fisher
Now even if I am on the right track for this, it leaves some questions (in no
a) others have reported being able to use SimH 4.0 under virtualisation with
no issues although not with RSX11M. So why would I be different?
b) I would have thought that the driver for RL especially as it is emulating
hardware would not "timeout" so quickly.
c) If it did timeout, why have I not seen an error message? Maybe I need to
look somewhere else ... hmm.

There is absolutely no problem running simh in a virtual environment.
The simh PDP11 can even run within a simh VAX simulator running inside
a Virtual PC.

Odds are very good that your pdp11 boot disk image is corrupted
OR there is something else odd about your configuration file

Post by Phil Fisher
And the obvious statement that I am completely wrong and it is something I
have configured incorrectly either in the virtualisation environment (except it
gives same error under both Virtual Box and VMware Workstation) or in
SimH.

The version you're running was released approximately 9 years ago. The
latest code can be working on your Linux system in a couple of minutes:

$ wget https://github.com/simh/simh/archive/master.zip
$ unzip master.zip
$ cd simh-master
$ make pdp11
$ cp BIN/pdp11 {someplace}

Odds are that you will experience the same results with the latest code, but
it may be easier to understand what is happening.

For your Windows system you can get the latest prebuilt windows binaries
from https://github.com/simh/Win32-Development-Binaries

If you still have problems you can create an issue at
https://github.com/simh/simh/issues and work through exactly what is wrong.

- Mark

Phil Fisher

2018-03-29 21:31:36 UTC

Permalink

Dear SimH people

I think I have found a pointer to the issue. The issue apparently being that my VirtualBox simulator under which I run Centos 6 Linux seems to have some challenge providing disk information to the SimH simulator running on Centos 6.

I think I have demonstrated this by first enabling some debugging on the compiled pdp11 simulator (DEBUG=1) and enabling DEBUG=TRACE;OPS;DATA on the RL disk device.

When I ran the simulator and merely enabled 11/70, 1MB RAM and a RL0 disk attached, I found the following results (the last few lines only shown):

PDP-11 simulator V4.0-0 Current git commit id: 9111a1a6
======================================================================
Disabling XQ
CPU 11/70, FPP, RH70, autoconfiguration enabled, idle enabled
1024KB
...
sim> attach RL0 ./RSX-11M_V3.2_RSX11MBL26_3.2.rl01
sim> BOOT RL0
DBG(8281)> RL RWR: >>RL wr: RLDA 000013
DBG(8281)> RL RWR: >>RL0 write: RLBA=013
DBG(8283)> RL RWR: >>RL wr: RLCS 000200 new 000004
DBG(8283)> RL RWR: >>RL GSTA: rlds=000035 drv=0
...
DBG(8320)> RL RRD: >>RL0 read: RLCS=014
DBG(8322)> RL RRD: >>RL rd: RLCS 000014
DBG(8322)> RL RRD: >>RL0 read: RLCS=014
DBG(8324)> RL RRD: >>RL rd: RLCS 000014
DBG(8324)> RL RRD: >>RL0 read: RLCS=014
DBG(8325)> RL OPS: >>RL svc: func=RD drv=0 rlda=000000
DBG(8325)> RL OPS: >>RL svc: cyl 0, sect 0, wc 512, maxwc 5120
DBG(8325)> RL OPS: RL0 sim_disk_rdsect lbn: 00000000 len: 00000400
DBG(8325)> RL OPS: 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
DBG(8325)> RL OPS: 0010 thru 03FF same as above
DBG(8326)> RL RRD: >>RL rd: RLCS 000215
DBG(8326)> RL RRD: >>RL0 read: RLCS=0215
DBG(8328)> RL RRD: >>RL rd: RLCS 000215
DBG(8328)> RL RRD: >>RL0 read: RLCS=0215
DBG(8328)> RL RWR: >>RL wr: RLCS 000215 new 000000
DBG(8328)> RL RWR: >>RL0 write: RLCS=00

HALT instruction, PC: 000002 (HALT)
sim>

at which point clearly the BOOT RL0 command will fail (and HALT).
So the buffer returned from the disk is all zeroes and is loaded into memory which results as above.

I had a think and considered that perhaps the I/O in the simulator(s) was getting confused somehow. So I attached the SAME DISK IMAGE but fetched it from the local PC store by making use of the Shared Folder feature of VirtualBox. This led the disk image to be located on the NTFS Win 10 filestore.

And lo, behold! It boots and I get the RSX11M prompt.

sim> SET RL ENABLE
sim> SET RL0 ENABLE, RL01, WRITEENABLED
sim> set RL DEBUG=OPS;TRACE;DATA
sim> ATTACH RL0 /mnt/phil/phil_dir/Simulators/rsx3_2/rsx11mbl26_3_2.rl01
RL0: '/mnt/phil/phil_dir/Simulators/rsx3_2/rsx11mbl26_3_2.rl01' Contains an ODS1 File system
RL0: Volume Name: RSXM26 Format: DECFILE11A Sectors In Volume: 10240
sim> boot RL0

RSX-11M V3.2 BL26 28K

MOU DL:RSXM26
@DL:[1,2]STARTUP

Notice that SimH detects it as a native File11 file system whereas before the format was apparently SimH based on simulator output.

Now, given the above, has anyone any suggestions on how I look further on this on the grounds that I would like the setup to be as normal as possible and using "native" files in the VBox/Centos6 system?

Phil
--
Phil J Fisher ***@peejayeff.co.uk
_____________________________________________________
Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________

Mike Stramba

2018-03-29 22:40:40 UTC

Permalink

Hi Phil,

Maybe try another Linux "flavor" ?

And /or check on the VirtualBox forums.

pdp11/rsx11 works for me on Ubuntu 14 (native Ubuntu).

Hmm, I do have VirtualBox installed on that Ubuntu box ..... Ubuntu
running on Vbox on Ubuntu, running rsx11 ? ;)

Mike

Post by Phil Fisher
Dear SimH people
I think I have found a pointer to the issue. The issue apparently being that
my VirtualBox simulator under which I run Centos 6 Linux seems to have some
challenge providing disk information to the SimH simulator running on Centos
6.
I think I have demonstrated this by first enabling some debugging on the
compiled pdp11 simulator (DEBUG=1) and enabling DEBUG=TRACE;OPS;DATA on the
RL disk device.
When I ran the simulator and merely enabled 11/70, 1MB RAM and a RL0 disk
PDP-11 simulator V4.0-0 Current git commit id: 9111a1a6
======================================================================
Disabling XQ
CPU 11/70, FPP, RH70, autoconfiguration enabled, idle enabled
1024KB
...
sim> attach RL0 ./RSX-11M_V3.2_RSX11MBL26_3.2.rl01
sim> BOOT RL0
DBG(8281)> RL RWR: >>RL wr: RLDA 000013
DBG(8281)> RL RWR: >>RL0 write: RLBA=013
DBG(8283)> RL RWR: >>RL wr: RLCS 000200 new 000004
DBG(8283)> RL RWR: >>RL GSTA: rlds=000035 drv=0
...
DBG(8320)> RL RRD: >>RL0 read: RLCS=014
DBG(8322)> RL RRD: >>RL rd: RLCS 000014
DBG(8322)> RL RRD: >>RL0 read: RLCS=014
DBG(8324)> RL RRD: >>RL rd: RLCS 000014
DBG(8324)> RL RRD: >>RL0 read: RLCS=014
DBG(8325)> RL OPS: >>RL svc: func=RD drv=0 rlda=000000
DBG(8325)> RL OPS: >>RL svc: cyl 0, sect 0, wc 512, maxwc 5120
DBG(8325)> RL OPS: RL0 sim_disk_rdsect lbn: 00000000 len: 00000400
DBG(8325)> RL OPS: 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
DBG(8325)> RL OPS: 0010 thru 03FF same as above
DBG(8326)> RL RRD: >>RL rd: RLCS 000215
DBG(8326)> RL RRD: >>RL0 read: RLCS=0215
DBG(8328)> RL RRD: >>RL rd: RLCS 000215
DBG(8328)> RL RRD: >>RL0 read: RLCS=0215
DBG(8328)> RL RWR: >>RL wr: RLCS 000215 new 000000
DBG(8328)> RL RWR: >>RL0 write: RLCS=00
HALT instruction, PC: 000002 (HALT)
sim>
at which point clearly the BOOT RL0 command will fail (and HALT).
So the buffer returned from the disk is all zeroes and is loaded into memory
which results as above.
I had a think and considered that perhaps the I/O in the simulator(s) was
getting confused somehow. So I attached the SAME DISK IMAGE but fetched it
from the local PC store by making use of the Shared Folder feature of
VirtualBox. This led the disk image to be located on the NTFS Win 10
filestore.
And lo, behold! It boots and I get the RSX11M prompt.
sim> SET RL ENABLE
sim> SET RL0 ENABLE, RL01, WRITEENABLED
sim> set RL DEBUG=OPS;TRACE;DATA
sim> ATTACH RL0 /mnt/phil/phil_dir/Simulators/rsx3_2/rsx11mbl26_3_2.rl01
RL0: '/mnt/phil/phil_dir/Simulators/rsx3_2/rsx11mbl26_3_2.rl01' Contains an
ODS1 File system
RL0: Volume Name: RSXM26 Format: DECFILE11A Sectors In Volume: 10240
sim> boot RL0
RSX-11M V3.2 BL26 28K

MOU DL:RSXM26
@DL:[1,2]STARTUP

Notice that SimH detects it as a native File11 file system whereas before
the format was apparently SimH based on simulator output.
Now, given the above, has anyone any suggestions on how I look further on
this on the grounds that I would like the setup to be as normal as possible
and using "native" files in the VBox/Centos6 system?
Phil
--
_____________________________________________________
Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh

Phil Fisher

2018-03-30 11:34:54 UTC

Permalink

Hi Mike

the point on another Linux is valid -- as I suspect VBox itself is not to blame since I had similar results with VMware Workstation (although I have not attempted to find a way to access "real" store on there I think it would work if I could do so).

Based on other responses and comments from the mailing list that others have run other SimH simulators under virtualisation (but maybe more commercial ones) with no issues I suspect it may be something on my hardware setup on the HP laptop (relating to virtualisation) or the Win 10 itself.

I am not yet good with SimH debugging (it took me a while to get to provide the help it did and I am still not convinced I did it correctly) so any suggestions welcome on that front. I did notice what seems to be a "bug" in that output is CR (015) terminated which I feel is odd - certainly messes up my looking back at my Putty history.

Phil

----- Original Message -----
From: Mike Stramba <***@gmail.com>
Reply-To: <***@gmail.com>
To: Phil Fisher <***@peejayeff.co.uk>
Cc: Bob Supnik (simh) <***@trailing-edge.com>
Sent: 29/03/2018 23:40:40
Subject: Re: [Simh] Problem booting RSX11M on pdp11 (halt at loc 0)
________________________________________________________________________________

Hi Phil,

Maybe try another Linux "flavor" ?

And /or check on the VirtualBox forums.

pdp11/rsx11 works for me on Ubuntu 14 (native Ubuntu).

Hmm, I do have VirtualBox installed on that Ubuntu box ..... Ubuntu
running on Vbox on Ubuntu, running rsx11 ? ;)

Mike

MOU DL:RSXM26
@DL:[1,2]STARTUP

Notice that SimH detects it as a native File11 file system whereas before
the format was apparently SimH based on simulator output.
Now, given the above, has anyone any suggestions on how I look further on
this on the grounds that I would like the setup to be as normal as possible
and using "native" files in the VBox/Centos6 system?
Phil
--
_____________________________________________________
Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________
_______________________________________________
Simh mailing list
http://mailman.trailing-edge.com/mailman/listinfo/simh

Mark Pizzolato

2018-03-30 14:35:48 UTC

Permalink

Post by Phil Fisher
the point on another Linux is valid -- as I suspect VBox itself is not to blame
since I had similar results with VMware Workstation (although I have not
attempted to find a way to access "real" store on there I think it would work if
I could do so).
Based on other responses and comments from the mailing list that others
have run other SimH simulators under virtualisation (but maybe more
commercial ones) with no issues I suspect it may be something on my
hardware setup on the HP laptop (relating to virtualisation) or the Win 10
itself.
I am not yet good with SimH debugging (it took me a while to get to provide
the help it did and I am still not convinced I did it correctly) so any
suggestions welcome on that front.

You found your way there reasonably well. Building with DEBUG=1 is only
necessary if you're planning on running the simulator under a debugger and
plan to set breakpoints, etc directly in the simulator code. The simh
provided debug output is always there without regard to having built
things with DEBUG=1.

Meanwhile, you've isolated things well to what seems to be where the
Disk image file is located. To help yourself you should use host system
tools to assure that the files are indeed EXACTLY the same.

I pulled down a CentOS 7 ISO image and installed that in a newly
created VirtualBox VM on my Windows 10 Laptop. I pulled the latest
code from github.com/simh/simh master branch and built it and tested.
This is what happened to me:

[***@localhost simh]$ make pdp11
*** Installing git hooks in local repository ***
lib paths are: /lib64/ /usr/lib64/dyninst/ /usr/lib64/iscsi/ /usr/lib64/mysql/
include paths are: /usr/include
using libm: /lib64/libm.so
using librt: /lib64/librt.so
using libpthread: /lib64/libpthread.so /usr/include/pthread.h
using regex: /usr/include/regex.h
using libdl: /lib64/libdl.so /usr/include/dlfcn.h
using mman: /usr/include/sys/mman.h
*** Info ***
*** Info *** The simulator you are building could provide more
*** Info *** functionality if video support were available on your system.
*** Info *** Install the development components of libSDL packaged by your
*** Info *** operating system distribution and rebuild your simulator to
*** Info *** enable this extra functionality.
*** Info ***
using libpcap: /usr/include/pcap.h
*** Info ***
*** Info *** pdp11 Simulator are being built with
*** Info *** minimal libpcap networking support
*** Info ***
*** Info ***
*** Info *** Simulators on your Linux platform can also be built with
*** Info *** extended LAN Ethernet networking support by using VDE Ethernet.
*** Info ***
*** Info *** To build simulator(s) with extended networking support you
*** Info *** should read 0readme_ethernet.txt and follow the instructions
*** Info *** regarding the needed libvdeplug components for your Linux
*** Info *** platform
*** Info ***
***
*** pdp11 Simulator being built with:
*** - compiler optimizations and no debugging support. GCC Version: 4.8.5.
*** - dynamic networking support using Linux provided libpcap components.
*** - Local LAN packet transports: PCAP TAP NAT(SLiRP)
***
*** git commit id is b0ff29781b2e6f526f6f36602590fcd91adc0c95.
*** git commit time is 2018-03-29T21:12:44-0700.
***
gcc -std=gnu99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPEN sim_BuildROMs.c -o BIN/BuildROMs
BIN/BuildROMs
rm -f BIN/BuildROMs
gcc -std=gnu99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPEN PDP11/pdp11_fp.c PDP11/pdp11_cpu.c PDP11/pdp11_dz.c PDP11/pdp11_cis.c PDP11/pdp11_lp.c PDP11/pdp11_rk.c PDP11/pdp11_rl.c PDP11/pdp11_rp.c PDP11/pdp11_rx.c PDP11/pdp11_stddev.c PDP11/pdp11_sys.c PDP11/pdp11_tc.c PDP11/pdp11_tm.c PDP11/pdp11_ts.c PDP11/pdp11_io.c PDP11/pdp11_rq.c PDP11/pdp11_tq.c PDP11/pdp11_pclk.c PDP11/pdp11_ry.c PDP11/pdp11_pt.c PDP11/pdp11_hk.c PDP11/pdp11_xq.c PDP11/pdp11_xu.c PDP11/pdp11_vh.c PDP11/pdp11_rh.c PDP11/pdp11_tu.c PDP11/pdp11_cpumod.c PDP11/pdp11_cr.c PDP11/pdp11_rf.c PDP11/pdp11_dl.c PDP11/pdp11_ta.c PDP11/pdp11_rc.c PDP11/pdp11_kg.c PDP11/pdp11_ke.c PDP11/pdp11_dc.c PDP11/pdp11_dmc.c PDP11/pdp11_kmc.c PDP11/pdp11_dup.c PDP11/pdp11_rs.c PDP11/pdp11_vt.c PDP11/pdp11_td.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c sim_imd.c sim_card.c -DVM_PDP11 -I PDP11 -DHAVE_PCAP_NETWORK -I/usr/include/ -DBPF_CONST_STRING -DUSE_SHARED -DHAVE_TAP_NETWORK -Islirp -Islirp_glue -Islirp_glue/qemu -DHAVE_SLIRP_NETWORK -DUSE_SIMH_SLIRP_DEBUG slirp/*.c slirp_glue/*.c -o BIN/pdp11 -lm -lrt -lpthread -ldl
[***@localhost simh]$ cd BIN
[***@localhost BIN]$ wget http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
--2018-03-30 10:00:26-- http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
Resolving www.mirrorservice.org (www.mirrorservice.org)... 212.219.56.184, 2001:630:341:12::184
Connecting to www.mirrorservice.org (www.mirrorservice.org)|212.219.56.184|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1607457 (1.5M) [application/x-gzip]
Saving to: ‘RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz’

100%[======================================>] 1,607,457 575KB/s in 2.7s

2018-03-30 10:00:30 (575 KB/s) - ‘RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz’ saved [1607457/1607457]

[***@localhost BIN]$ gzip -d RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
[***@localhost BIN]$ ./pdp11

PDP-11 simulator V4.0-0 Current git commit id: b0ff2978
sim> att rl0 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
RL0: 'RSX-11M_V3.2_RSX11MBL26_3.2.DSK' Contains an ODS1 File system
RL0: Volume Name: RSXM26 Format: DECFILE11A Sectors In Volume: 10240
sim> b rl0

RSX-11M V3.2 BL26 28K

Post by Phil Fisher
MOU DL:RSXM26
@DL:[1,2]STARTUP

Simulation stopped, PC: 001330 (CLRB (R1)+)
sim> q
Goodbye
[***@localhost BIN]$ ls -l RSX-11M_V3.2_RSX11MBL26_3.2.DSK
-rw-rw-r--. 1 mark mark 5243087 Mar 30 10:01 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
[***@localhost BIN]$ md5sum RSX-11M_V3.2_RSX11MBL26_3.2.DSK
7ae69baabd1c15fb2006545c457feb5d RSX-11M_V3.2_RSX11MBL26_3.2.DSK
[***@localhost BIN]$ ./pdp11

PDP-11 simulator V4.0-0 Current git commit id: b0ff2978
sim> show ver
PDP-11 simulator V4.0-0 Current
Simulator Framework Capabilities:
32b data
32b addresses
Threaded Ethernet Packet transports:PCAP:TAP:NAT:UDP
Idle/Throttling support is available
Virtual Hard Disk (VHD) support
RAW disk and CD/DVD ROM support
Asynchronous I/O support (Lock free asynchronous event queue)
Asynchronous Clock support
FrontPanel API Version 12
Host Platform:
Compiler: GCC 4.8.5 20150623 (Red Hat 4.8.5-16)
Simulator Compiled as C arch: x64 (Release Build) on Mar 30 2018 at 00:51:38
Memory Access: Little Endian
Memory Pointer Size: 64 bits
Large File (>2GB) support
SDL Video support: No Video Support
RegEx support for EXPECT commands
OS clock resolution: 1ms
Time taken by msleep(1): 1ms
OS: Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
git commit id: b0ff2978
git commit time: 2018-03-29T21:12:44-0700
sim> q
Goodbye

This the exactly the expected result and essentially identical to what happens on other Linux, OS X, and Windows systems.

What is the size and md5sum of the file you are attaching to the RL0 device?

Notice in my test the directory I'm working in the one for my user account on the local CentOS file system and is not a shared drive. The same results are observed if I use a file on a shared drive.

If the md5sum of the disk image file is the same as mine, then I'll go and find a CentOS 6 image and dig further.

If the md5sum of the disk image file differs, then first pull down and unzip a new disk image:
$ wget http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
$ gzip -d RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
$ md5sum RSX-11M_V3.2_RSX11MBL26_3.2.DSK
If this file doesn't have the same value as I do, then clearly the problem has nothing to do with simh.
Once you've got matching input files, try with the minimal 2 SCP commands I used:
sim> attach RL0 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
sim> B RL0
As you noticed, the output produced by the attach command will predict whether the boot will succeed.

= Mark

Phil Fisher

2018-03-30 18:54:43 UTC

Permalink

Hi all

It seems it is Centos6 (specifically Centos 6.9, kernel 2.6.32-696) since I also tried on my Centos 7 -- not as recent as yours Mark (I don't like RHEL7/Centos7 so tend not to use it unless I need something specific).

Just like you I re-used my simh-master.zip (recent), built SimH (4.0.0-current) and ran pdp11 (no DEBUG).

I copied the RL01 image I had already that I knew worked from my Win 10 storage onto Centos7 "local storage". I then did a cmp on the two for confirmation they were identical. Then created 11/70, 1MB RAM, IDLE enabled. Attached the new disk from local Centos7 storage and noted it was immediately correctly recognised (thanks for the tip Mark), booted and et voila!

So there is something screwy with my Centos6 or the kernel. I will re-update Centos6 later and re-try, just in case.

Phil

----- Original Message -----
From: Mark Pizzolato <***@infocomm.com>
To: Phil Fisher <***@peejayeff.co.uk>, <***@gmail.com>
Cc: Bob Supnik (simh) <***@trailing-edge.com>
Sent: 30/03/2018 15:35:48
Subject: RE: [Simh] Problem booting RSX11M on pdp11 (halt at loc 0)
________________________________________________________________________________

You found your way there reasonably well. Building with DEBUG=1 is only
necessary if you're planning on running the simulator under a debugger and
plan to set breakpoints, etc directly in the simulator code. The simh
provided debug output is always there without regard to having built
things with DEBUG=1.

Meanwhile, you've isolated things well to what seems to be where the
Disk image file is located. To help yourself you should use host system
tools to assure that the files are indeed EXACTLY the same.

I pulled down a CentOS 7 ISO image and installed that in a newly
created VirtualBox VM on my Windows 10 Laptop. I pulled the latest
code from github.com/simh/simh master branch and built it and tested.
This is what happened to me:

[***@localhost simh]$ make pdp11
*** Installing git hooks in local repository ***
lib paths are: /lib64/ /usr/lib64/dyninst/ /usr/lib64/iscsi/ /usr/lib64/mysql/
include paths are: /usr/include
using libm: /lib64/libm.so
using librt: /lib64/librt.so
using libpthread: /lib64/libpthread.so /usr/include/pthread.h
using regex: /usr/include/regex.h
using libdl: /lib64/libdl.so /usr/include/dlfcn.h
using mman: /usr/include/sys/mman.h
*** Info ***
*** Info *** The simulator you are building could provide more
*** Info *** functionality if video support were available on your system.
*** Info *** Install the development components of libSDL packaged by your
*** Info *** operating system distribution and rebuild your simulator to
*** Info *** enable this extra functionality.
*** Info ***
using libpcap: /usr/include/pcap.h
*** Info ***
*** Info *** pdp11 Simulator are being built with
*** Info *** minimal libpcap networking support
*** Info ***
*** Info ***
*** Info *** Simulators on your Linux platform can also be built with
*** Info *** extended LAN Ethernet networking support by using VDE Ethernet.
*** Info ***
*** Info *** To build simulator(s) with extended networking support you
*** Info *** should read 0readme_ethernet.txt and follow the instructions
*** Info *** regarding the needed libvdeplug components for your Linux
*** Info *** platform
*** Info ***
***
*** pdp11 Simulator being built with:
*** - compiler optimizations and no debugging support. GCC Version: 4.8.5.
*** - dynamic networking support using Linux provided libpcap components.
*** - Local LAN packet transports: PCAP TAP NAT(SLiRP)
***
*** git commit id is b0ff29781b2e6f526f6f36602590fcd91adc0c95.
*** git commit time is 2018-03-29T21:12:44-0700.
***
gcc -std=gnu99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPEN sim_BuildROMs.c -o BIN/BuildROMs
BIN/BuildROMs
rm -f BIN/BuildROMs
gcc -std=gnu99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPEN PDP11/pdp11_fp.c PDP11/pdp11_cpu.c PDP11/pdp11_dz.c PDP11/pdp11_cis.c PDP11/pdp11_lp.c PDP11/pdp11_rk.c PDP11/pdp11_rl.c PDP11/pdp11_rp.c PDP11/pdp11_rx.c PDP11/pdp11_stddev.c PDP11/pdp11_sys.c PDP11/pdp11_tc.c PDP11/pdp11_tm.c PDP11/pdp11_ts.c PDP11/pdp11_io.c PDP11/pdp11_rq.c PDP11/pdp11_tq.c PDP11/pdp11_pclk.c PDP11/pdp11_ry.c PDP11/pdp11_pt.c PDP11/pdp11_hk.c PDP11/pdp11_xq.c PDP11/pdp11_xu.c PDP11/pdp11_vh.c PDP11/pdp11_rh.c PDP11/pdp11_tu.c PDP11/pdp11_cpumod.c PDP11/pdp11_cr.c P
DP11/pdp11_rf.c PDP11/pdp11_dl.c PDP11/pdp11_ta.c PDP11/pdp11_rc.c PDP11/pdp11_kg.c PDP11/pdp11_ke.c PDP11/pdp11_dc.c PDP11/pdp11_dmc.c PDP11/pdp11_kmc.c PDP11/pdp11_dup.c PDP11/pdp11_rs.c PDP11/pdp11_vt.c PDP11/pdp11_td.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c sim_imd.c sim_card.c -DVM_PDP11 -I PDP11 -DHAVE_PCAP_NETWORK -I/usr/include/ -DBPF_CONST_STRING -DUSE_SHARED -DHAVE_TAP_NETWORK -Islirp -Islirp_glue -Islirp_glue/qemu -DHAVE_SLIRP_NETWORK -DUSE_SIMH_SLIRP_DEBUG slirp/*.c slirp_glue/*.c -o BIN/pdp11 -lm -lrt -lpthread -ldl
[***@localhost simh]$ cd BIN
[***@localhost BIN]$ wget http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
--2018-03-30 10:00:26-- http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
Resolving www.mirrorservice.org (www.mirrorservice.org)... 212.219.56.184, 2001:630:341:12::184
Connecting to www.mirrorservice.org (www.mirrorservice.org)|212.219.56.184|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1607457 (1.5M) [application/x-gzip]
Saving to: ‘RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz’

100%[======================================>] 1,607,457 575KB/s in 2.7s

2018-03-30 10:00:30 (575 KB/s) - ‘RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz’ saved [1607457/1607457]

[***@localhost BIN]$ gzip -d RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
[***@localhost BIN]$ ./pdp11

PDP-11 simulator V4.0-0 Current git commit id: b0ff2978
sim> att rl0 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
RL0: 'RSX-11M_V3.2_RSX11MBL26_3.2.DSK' Contains an ODS1 File system
RL0: Volume Name: RSXM26 Format: DECFILE11A Sectors In Volume: 10240
sim> b rl0

RSX-11M V3.2 BL26 28K

Post by Phil Fisher
MOU DL:RSXM26
@DL:[1,2]STARTUP

Mark Pizzolato

2018-03-30 19:13:49 UTC

Permalink

Post by Phil Fisher
It seems it is Centos6 (specifically Centos 6.9, kernel 2.6.32-696) since I also
tried on my Centos 7 -- not as recent as yours Mark (I don't like
RHEL7/Centos7 so tend not to use it unless I need something specific).
Just like you I re-used my simh-master.zip (recent), built SimH (4.0.0-current)
and ran pdp11 (no DEBUG).
I copied the RL01 image I had already that I knew worked from my Win 10
storage onto Centos7 "local storage". I then did a cmp on the two for
confirmation they were identical. Then created 11/70, 1MB RAM, IDLE
enabled. Attached the new disk from local Centos7 storage and noted it was
immediately correctly recognised (thanks for the tip Mark), booted and et
voila!
So there is something screwy with my Centos6 or the kernel. I will re-update
Centos6 later and re-try, just in case.

Before involving simh, please compare the md5sum of the disk image file that
works vs the one that doesn't.

- Mark

Phil Fisher

2018-03-31 13:36:31 UTC

Permalink

It seems that the copying of the file has somehow gone wrong. The MD5 checksums differ; but copying the file fails but a dd of the file seems to work ok. I am beginning to suspect my Centos 6.9 is corrupt somewhere but ... odd if so as so much works ok.

Another possible answer is my laptop networking is screwed as the file download sizes are/were fine. Thanks to all for the help.

Phil

----- Original Message -----
From: Mark Pizzolato <***@infocomm.com>
To: Phil Fisher <***@peejayeff.co.uk>, <***@gmail.com>
Cc: Bob Supnik (simh) <***@trailing-edge.com>
Sent: 30/03/2018 20:13:49
Subject: RE: [Simh] Problem booting RSX11M on pdp11 (halt at loc 0)
________________________________________________________________________________

Before involving simh, please compare the md5sum of the disk image file that
works vs the one that doesn't.

- Mark

khandy21yo

2018-03-30 16:23:20 UTC

Permalink

Since you're using a shared device, could virtualbox be doing a dos2unix thing to yo which side of the share did you write you're image to? Does it look the same from both sides?

from my Galaxy TabÂ® A

You found your way there reasonably well.Â Building with DEBUG=1 is only
necessary if you're planning on running the simulator under a debugger and
plan to set breakpoints, etc directly in the simulator code.Â The simh
provided debug output is always there without regard to having built
things with DEBUG=1.

Meanwhile, you've isolated things well to what seems to be where the
Disk image file is located.Â To help yourself you should use host system
tools to assure that the files are indeed EXACTLY the same.

I pulled down a CentOS 7 ISO image and installed that in a newly
created VirtualBox VM on my Windows 10 Laptop.Â I pulled the latest
code from github.com/simh/simh master branch and built it and tested.
This is what happened to me:

[***@localhost simh]$ make pdp11
*** Installing git hooks in local repository ***
lib paths are: /lib64/ /usr/lib64/dyninst/ /usr/lib64/iscsi/ /usr/lib64/mysql/
include paths are: /usr/include
using libm: /lib64/libm.so
using librt: /lib64/librt.so
using libpthread: /lib64/libpthread.so /usr/include/pthread.h
using regex: /usr/include/regex.h
using libdl: /lib64/libdl.so /usr/include/dlfcn.h
using mman: /usr/include/sys/mman.h
*** Info ***
*** Info *** The simulator you are building could provide more
*** Info *** functionality if video support were available on your system.
*** Info *** Install the development components of libSDL packaged by your
*** Info *** operating system distribution and rebuild your simulator to
*** Info *** enable this extra functionality.
*** Info ***
using libpcap: /usr/include/pcap.h
*** Info ***
*** Info *** pdp11 Simulator are being built with
*** Info *** minimal libpcap networking support
*** Info ***
*** Info ***
*** Info *** Simulators on your Linux platform can also be built with
*** Info *** extended LAN Ethernet networking support by using VDE Ethernet.
*** Info ***
*** Info *** To build simulator(s) with extended networking support you
*** Info *** should read 0readme_ethernet.txt and follow the instructions
*** Info *** regarding the needed libvdeplug components for your Linux
*** Info *** platform
*** Info ***
***
*** pdp11 Simulator being built with:
*** - compiler optimizations and no debugging support. GCC Version: 4.8.5.
*** - dynamic networking support using Linux provided libpcap components.
*** - Local LAN packet transports: PCAP TAP NAT(SLiRP)
***
*** git commit id is b0ff29781b2e6f526f6f36602590fcd91adc0c95.
*** git commit time is 2018-03-29T21:12:44-0700.
***
gcc -std=gnu99 -U__STRICT_ANSI__Â -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700Â -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IOÂ -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPENÂ sim_BuildROMs.c -o BIN/BuildROMs
BIN/BuildROMs
rm -f BIN/BuildROMs
gcc -std=gnu99 -U__STRICT_ANSI__Â -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=b0ff29781b2e6f526f6f36602590fcd91adc0c95 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700 -DSIM_GIT_COMMIT_TIME=2018-03-29T21:12:44-0700Â -DSIM_COMPILER="GCC Version: 4.8.5" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IOÂ -DHAVE_REGEX_H -DHAVE_DLOPEN=so -DHAVE_UTIME -DHAVE_GLOB -DHAVE_SHM_OPENÂ PDP11/pdp11_fp.c PDP11/pdp11_cpu.c PDP11/pdp11_dz.c PDP11/pdp11_cis.c PDP11/pdp11_lp.c PDP11/pdp11_rk.c PDP11/pdp11_rl.c PDP11/pdp11_rp.c PDP11/pdp11_rx.c PDP11/pdp11_stddev.c PDP11/pdp11_sys.c PDP11/pdp11_tc.c PDP11/pdp11_tm.c PDP11/pdp11_ts.c PDP11/pdp11_io.c PDP11/pdp11_rq.c PDP11/pdp11_tq.c PDP11/pdp11_pclk.c PDP11/pdp11_ry.c PDP11/pdp11_pt.c PDP11/pdp11_hk.c PDP11/pdp11_xq.c PDP11/pdp11_xu.c PDP11/pdp11_vh.c PDP11/pdp11_rh.c PDP11/pdp11_tu.c PDP11/pdp11_cpumod.c PDP11/pdp11_cr.c PDP11/pdp11_rf.c PDP11/pdp11_dl.c PDP11/pdp11_ta.c PDP11/pdp11_rc.c PDP11/pdp11_kg.c PDP11/pdp11_ke.c PDP11/pdp11_dc.c PDP11/pdp11_dmc.c PDP11/pdp11_kmc.c PDP11/pdp11_dup.c PDP11/pdp11_rs.c PDP11/pdp11_vt.c PDP11/pdp11_td.c PDP11/pdp11_io_lib.cÂ Â scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c sim_imd.c sim_card.c -DVM_PDP11 -I PDP11 -DHAVE_PCAP_NETWORK -I/usr/include/ -DBPF_CONST_STRING -DUSE_SHARED -DHAVE_TAP_NETWORK -Islirp -Islirp_glue -Islirp_glue/qemu -DHAVE_SLIRP_NETWORK -DUSE_SIMH_SLIRP_DEBUG slirp/*.c slirp_glue/*.cÂ -o BIN/pdp11 -lm -lrt -lpthread -ldlÂ
[***@localhost simh]$ cd BIN
[***@localhost BIN]$ wget http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
--2018-03-30 10:00:26--Â http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
Resolving www.mirrorservice.org (www.mirrorservice.org)... 212.219.56.184, 2001:630:341:12::184
Connecting to www.mirrorservice.org (www.mirrorservice.org)|212.219.56.184|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1607457 (1.5M) [application/x-gzip]
Saving to: âRSX-11M_V3.2_RSX11MBL26_3.2.DSK.gzâ

100%[======================================>] 1,607,457Â Â Â 575KB/sÂ Â in 2.7sÂ Â

2018-03-30 10:00:30 (575 KB/s) - âRSX-11M_V3.2_RSX11MBL26_3.2.DSK.gzâ saved [1607457/1607457]

[***@localhost BIN]$ gzip -d RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
[***@localhost BIN]$ ./pdp11

PDP-11 simulator V4.0-0 CurrentÂ Â Â Â Â Â Â git commit id: b0ff2978
sim> att rl0 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
RL0: 'RSX-11M_V3.2_RSX11MBL26_3.2.DSK' Contains an ODS1 File system
RL0: Volume Name:Â Â Â Â Â Â RSXM26 Format: DECFILE11AÂ Â Sectors In Volume: 10240
sim> b rl0

Â RSX-11M V3.2 BL26Â Â 28K

Post by Phil Fisher
MOU DL:RSXM26
@DL:[1,2]STARTUP

Simulation stopped, PC: 001330 (CLRB (R1)+)
sim> q
Goodbye
[***@localhost BIN]$ ls -l RSX-11M_V3.2_RSX11MBL26_3.2.DSK
-rw-rw-r--. 1 mark mark 5243087 Mar 30 10:01 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
[***@localhost BIN]$ md5sum RSX-11M_V3.2_RSX11MBL26_3.2.DSK
7ae69baabd1c15fb2006545c457feb5dÂ RSX-11M_V3.2_RSX11MBL26_3.2.DSK
[***@localhost BIN]$ ./pdp11

PDP-11 simulator V4.0-0 CurrentÂ Â Â Â Â Â Â git commit id: b0ff2978
sim> show ver
PDP-11 simulator V4.0-0 Current
Â Â Â Simulator Framework Capabilities:
Â Â Â Â Â Â Â 32b data
Â Â Â Â Â Â Â 32b addresses
Â Â Â Â Â Â Â Threaded Ethernet Packet transports:PCAP:TAP:NAT:UDP
Â Â Â Â Â Â Â Idle/Throttling support is available
Â Â Â Â Â Â Â Virtual Hard Disk (VHD) support
Â Â Â Â Â Â Â RAW disk and CD/DVD ROM support
Â Â Â Â Â Â Â Asynchronous I/O support (Lock free asynchronous event queue)
Â Â Â Â Â Â Â Asynchronous Clock support
Â Â Â Â Â Â Â FrontPanel API Version 12
Â Â Â Host Platform:
Â Â Â Â Â Â Â Compiler: GCC 4.8.5 20150623 (Red Hat 4.8.5-16)
Â Â Â Â Â Â Â Simulator Compiled as C arch: x64 (Release Build) on Mar 30 2018 at 00:51:38
Â Â Â Â Â Â Â Memory Access: Little Endian
Â Â Â Â Â Â Â Memory Pointer Size: 64 bits
Â Â Â Â Â Â Â Large File (>2GB) support
Â Â Â Â Â Â Â SDL Video support: No Video Support
Â Â Â Â Â Â Â RegEx support for EXPECT commands
Â Â Â Â Â Â Â OS clock resolution: 1ms
Â Â Â Â Â Â Â Time taken by msleep(1): 1ms
Â Â Â Â Â Â Â OS: Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Â Â Â Â Â Â Â git commit id: b0ff2978
Â Â Â Â Â Â Â git commit time: 2018-03-29T21:12:44-0700
sim> q
Goodbye

This the exactly the expected result and essentially identical to what happens on other Linux, OS X, and Windows systems.

What is the size and md5sum of the file you are attaching to the RL0 device?

Notice in my test the directory I'm working in the one for my user account on the local CentOS file system and is not a shared drive.Â The same results are observed if I use a file on a shared drive.

If the md5sum of the disk image file is the same as mine, then I'll go and find a CentOS 6 image and dig further.

If the md5sum of the disk image file differs, then first pull down and unzip a new disk image:
Â Â $ wget http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/discimages/rl01/rsx11m_3.2/RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
Â Â $ gzip -d RSX-11M_V3.2_RSX11MBL26_3.2.DSK.gz
Â Â $ md5sum RSX-11M_V3.2_RSX11MBL26_3.2.DSK
If this file doesn't have the same value as I do, then clearly the problem has nothing to do with simh.
Once you've got matching input files, try with the minimal 2 SCP commands I used:
Â Â Â sim> attach RL0 RSX-11M_V3.2_RSX11MBL26_3.2.DSK
Â Â Â sim> B RL0
As you noticed, the output produced by the attach command will predict whether the boot will succeed.

= Mark